Add default sync schedule documentation to connector FAQ

baton/faq.mdx

@@ -6,7 +6,7 @@
 
 ## Which IP addresses does C1 use for connectors?
 
 See [C1 egress IP addresses](/product/admin/egress-ips) for the full list of IPs to add to your allowlist for outbound connector and function traffic.
 
 ## What are connectors?
 
@@ -24,14 +24,44 @@
 
 ### Syncing
 
 Syncing keeps data consistent between C1 and your integrated systems. Once set up, a connector regularly retrieves access data (such as accounts, groups, roles, and orgs) from the integrated system and updates the records in the corresponding application in C1. Syncing ensures C1 has an accurate and up-to-date view of user identities and their assigned permissions. All connectors can sync.
 
 Specifically, C1 syncs:
 
 - **Accounts**, or the user accounts within the integrated system.
 - **Resources**, or the specific pieces of access (such as group membership or role assignment) in the integrated system and which accounts they’re assigned to.
 
-Syncing is a read-only operation. Most connectors use syncs that are scheduled to run at regular intervals. Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next iteration of a set schedule. You can also start a sync on demand on any connector’s integration page.
+Syncing is a read-only operation. By default, connectors sync every **24 hours**. Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next scheduled sync. You can also start a sync on demand on any connector’s integration page.
+
+For details on sync intervals, continuous sync, on-demand sync, and audit considerations, see [Sync schedule](/baton/sync-schedule).
+
+#### Default sync schedule
+
+C1 automatically syncs each connector on a recurring schedule. The default interval depends on your tenant configuration:
+
+- **Tenants with access requests enabled:** Connectors sync every **1 hour** by default.
+- **All other tenants:** Connectors sync every **24 hours** by default.
+
+These defaults apply when no custom sync schedule has been configured for the connector.
+
+#### Custom sync schedules
+
+You can configure a custom sync schedule for individual connectors. Custom schedules support two formats:
+
+- **Fixed interval:** Set a specific duration between syncs (for example, every 6 hours). The minimum configurable interval is 30 minutes.
+- **Cron schedule:** Use a cron expression with timezone support for more precise scheduling (for example, daily at midnight in a specific timezone).
+
+Some connector types enforce a minimum sync interval that overrides shorter custom schedules to protect the external system from excessive API calls.
+
+#### On-demand sync
+
+You can start a sync at any time from the connector’s integration page in C1, regardless of the configured schedule. There is a short cooldown period between on-demand syncs to prevent overlapping operations.
+
+#### Continuous sync
+
+Some connectors support continuous sync, which supplements the scheduled sync cycle. Instead of waiting for the next scheduled sync, continuous sync listens for change events from the external system and pulls new data as it becomes available. This reduces the delay between a change occurring in the external system and that change being reflected in C1.
+
+Continuous sync works alongside scheduled syncs — it does not replace them. Scheduled syncs still run at their configured interval to ensure a complete, consistent view of the external system’s data.
 
 ### Sync issue or failure notifications
 
@@ -54,7 +84,7 @@
 
 ### Ticketing
 
 Select connectors for helpdesk ticketing systems can also be configured to automatically create tickets to track manual provisioning assignments. C1 tracks the status of the tickets it creates and updates the status of the access request in C1 accordingly.
 
 Ticketing is a read-write operation from C1 to the integrated ticketing system.
 
@@ -98,6 +128,17 @@
     Connectors periodically check in with C1 to request work. When tasks are available, any idle instance can claim the next task. This creates a worker-queue architecture: if one connector instance goes down, the remaining instances will pick up subsequent tasks. Note that only one sync task runs at a time per connector, and if an instance processing a task becomes unavailable, there may be a short delay (up to a few minutes) before the task is released and becomes available for another instance to claim.
     </Accordion>
 
+    <Accordion title="What is the default sync schedule?">
+    C1 automatically syncs each connector on a recurring schedule. The default sync interval depends on your tenant configuration:
+
+    - **Tenants with access requests enabled:** Every **1 hour**.
+    - **All other tenants:** Every **24 hours**.
+
+    You can customize the sync schedule for individual connectors by setting a fixed interval (minimum 30 minutes) or a cron expression with timezone support. Some connector types enforce a minimum interval that overrides shorter custom schedules. You can also trigger a sync on demand at any time from the connector's integration page.
+
+    Connectors that support **continuous sync** supplement the scheduled cycle by listening for change events from the external system in near real-time, reducing the delay between changes and their reflection in C1. Continuous sync works alongside scheduled syncs and does not replace them.
+    </Accordion>
+
     <Accordion title="Where are sync state files stored?">
     The relevant file is `sync.c1z`. By default, the connector stores this in a temporary folder determined by the host operating system (the location varies). You can specify a custom location for the `sync.c1z` file using a command-line flag. For example, in a Docker setup, you can map a volume to the container and specify a path to store the file. The `sync.c1z` file will then be stored in that mapped location.
 

baton/sync-schedule.mdx

@@ -0,0 +1,60 @@
+---
+title: "Sync schedule"
+sidebarTitle: "Sync schedule"
+description: "Learn about default sync intervals, continuous sync, on-demand sync, and how sync scheduling works in C1."
+---
+
+C1 connectors periodically sync data from your integrated systems to keep your access records up to date. This page explains how sync scheduling works, including default intervals, continuous sync, and on-demand options.
+
+## Default sync schedule
+
+C1 automatically syncs each connector on a recurring schedule. The default interval depends on your tenant configuration:
+
+- **Tenants with access requests enabled:** Connectors sync every **1 hour** by default.
+- **All other tenants:** Connectors sync every **24 hours** by default.
+
+These defaults apply when no custom sync schedule has been configured for the connector. Some connectors may have different minimum intervals based on the requirements of the integrated system. For example, connectors for systems with strict API rate limits may have longer minimum sync intervals to avoid exceeding those limits.
+
+## Custom sync schedules
+
+You can configure a custom sync schedule for individual connectors. Custom schedules support two formats:
+
+- **Fixed interval:** Set a specific duration between syncs (for example, every 6 hours). The minimum configurable interval is **30 minutes**.
+- **Cron schedule:** Use a cron expression with timezone support for more precise scheduling (for example, daily at midnight in a specific timezone).
+
+Some connector types enforce a **minimum sync interval** that overrides shorter custom schedules to protect the external system from excessive API calls. If you configure a custom interval below this minimum, C1 automatically raises it to meet the requirement. Custom intervals that exceed the connector's minimum are preserved as configured.
+
+## On-demand sync
+
+You can start a sync at any time from the connector's integration page in C1, regardless of the configured schedule. On-demand syncs run a full sync immediately. There is a short cooldown period between on-demand syncs to prevent overlapping operations.
+
+This is useful when you've made changes in an integrated system and want them reflected in C1 right away.
+
+## Continuous sync
+
+Some connectors support **continuous sync**, which supplements the scheduled sync cycle. Instead of waiting for the next scheduled sync, continuous sync listens for change events from the external system and pulls new data as it becomes available. This reduces the delay between a change occurring in the external system and that change being reflected in C1.
+
+Continuous sync works alongside scheduled syncs -- it does not replace them. Scheduled syncs still run at their configured interval to ensure a complete, consistent view of the external system's data.
+
+<Note>
+  See each connector's documentation to check whether it supports continuous sync.
+</Note>
+
+## Sync failure notifications
+
+If a connector experiences **three consecutive sync failures**, C1 sends an automated email alert to the designated application owner so you can investigate and correct the issue.
+
+C1 also automatically **pauses a connector's sync cycle** and alerts you if significant data anomalies are detected, such as the number of synced resources decreasing by half between consecutive syncs. This safety mechanism is enabled by default and can be configured by navigating to an app's **Configure connector** > **Advanced** tab.
+
+## Pausing and resuming sync
+
+You can pause a connector's sync schedule from the connector's configuration page. While paused, no automatic syncs run, but you can still trigger on-demand syncs. Resume the schedule at any time to return to automatic syncing.
+
+## Audit considerations
+
+For audit purposes, keep the following in mind:
+
+- The default sync interval means that access data in C1 may be up to 1 hour (for tenants with access requests) or 24 hours behind the source system.
+- You can trigger an on-demand sync before generating audit reports to ensure the most current data.
+- Sync history and status are available on each connector's integration page, providing a record of when syncs occurred and whether they completed successfully.
+- If your audit requirements call for more frequent syncs, you can configure a custom sync schedule with a shorter interval (minimum 30 minutes).

docs.json

@@ -333,7 +333,8 @@
             "group": "Manage connectors",
             "pages": [
               "baton/configure",
-              "baton/manage-connector"
+              "baton/manage-connector",
+              "baton/sync-schedule"
             ]
           },
           {