Control when Alida applies user provisioning changes from your identity provider.
After you create user auto-provisioning groups and generate a SCIM authentication token, SCIM synchronization starts in a paused state. While sync is paused, your identity provider (IdP) can send provisioning data to the Alida SCIM server, but Alida does not apply user account changes until you resume sync.
Pause sync when you need to finish or update your IdP configuration (for example, group mappings, Group Push, or assignments) without deleting and regenerating tokens. This workflow applies to all supported IdPs, including Microsoft Azure, Okta, and OneLogin.
Important: Do not click Resume Sync
until your IdP provisioning setup is complete and the correct users and groups are
configured. If you resume sync before setup is ready, Alida may interpret the lack
of IdP users and groups as having no eligible users and remove existing user
accounts.
When sync is resumed, Alida
applies user create, update, and deprovision actions from your IdP based on
your configured group mappings.