Why Mobile Devices Are Unenrolled Before Processing Changes in Identity Panel

To maintain accurate data and prevent conflicts, the Identity Panel Suite un-enrolls connected mobile devices before applying certain changes. This is a deliberate safeguard that ensures synchronization processes—especially those involving HyperSync Panel—operate smoothly and without unintended consequences across systems.

Preventing Synchronization Conflicts

Before executing identity changes, the system checks for any active mobile device connections associated with the user or object being modified. These connections are temporarily un-enrolled (disconnected) to prevent any data from being unintentionally pushed to or pulled from the device during synchronization. This is especially important in environments where mobile device management (MDM) or identity apps are configured to sync data directly, such as user attributes, credentials, or group memberships.

Without this step, conflicting updates could occur—such as a mobile device syncing outdated information right as new data is being written. This could result in:

• Overwritten updates

• Partial or duplicated records

• Application errors on the device or in the directory

By un-enrolling the mobile device, Identity Panel ensures that only the intended, updated information is processed and stored.

Automatic Re-enrollment After Sync

Once changes are successfully processed, devices can be re-enrolled automatically or prompted for re-connection. This behavior ensures that the device receives the most up-to-date and validated data, preventing stale information from being introduced back into the system. This re-enrollment is seamless and generally requires no user action, depending on the organization's configuration.

Key benefits of this approach:

• Prevents synchronization errors across systems

• Supports data integrity and consistency

• Reduces risk of identity-related support issues