docs: note scope-narrowing as a common sync-pause trigger

baton/configure.mdx

@@ -38,9 +38,11 @@
 
 ## Connector sync pause
 
-C1 automatically pauses a connector’s sync cycle and alerts the connector owner if significant data anomalies are detected (for example, if the number of resources decreases by half between one sync and the next).
+C1 automatically pauses a connector’s sync cycle and alerts the connector owner if significant data anomalies are detected (for example, if the number of resources decreases by half between one sync and the next, or if a large number of grants are removed).
 
-When a significant drop in resources is detected during a connector sync, C1 does not immediately apply the change as a precaution against unintentionally removing access. A banner explaining that the sync has been paused is displayed. Click **Confirm changes** in the banner on the application’s page to let C1 know that the change is expected and that it’s safe to proceed.
+When a significant drop in resources or grants is detected during a connector sync, C1 does not immediately apply the change as a precaution against unintentionally removing access. A banner explaining that the sync has been paused is displayed. Click **Confirm changes** in the banner on the application’s page to let C1 know that the change is expected and that it’s safe to proceed.
+
+A common way to trigger this pause: adding a setup field that narrows what a connector syncs — for example, limiting it to specific tenants, projects, orgs, or sites — to a connector that already synced without that field set. Excluding scope that was previously synced also excludes the grants and memberships tied to it, which registers as a significant drop. This is expected; confirm the change to apply the narrower sync going forward. Check the connector’s own documentation for which setup fields can narrow its sync scope.
 
 ### Turn off connector sync pause
 

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,7 +24,7 @@
 
 ### 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:
 
@@ -37,7 +37,7 @@
 
 If a connector experiences three consecutive sync failures, an automated email alert is immediately dispatched to the designated owner, letting you take action quickly to correct the issue.
 
-We’ll also automatically pause a connector’s sync cycle and alert you if significant data anomalies are detected (such as if the number of synced resources decreases by half between one sync and the next). This setting is on by default, but you can configure it by navigating to an app’s **Configure connector** > **Advanced** tab.
+We’ll also automatically pause a connector’s sync cycle and alert you if significant data anomalies are detected (such as if the number of synced resources decreases by half between one sync and the next, or if a large number of grants are removed — for example, after narrowing a connector’s setup fields to sync a smaller scope than it previously synced). This setting is on by default, but you can configure it by navigating to an app’s **Configure connector** > **Advanced** tab. See [Connector sync pause](/baton/configure#connector-sync-pause) for details.
 
 ### Provisioning
 
@@ -54,7 +54,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.