This release introduces Controlled User Exclusion, enabling Administrators to manage how individual Users are included in or excluded from an active Connector integration. Only Users originally synced through the Connector can be managed using this feature.

For more information:

• Connectors: Controlled User Exclusion

Controlled User Exclusion provides Administrators with greater flexibility and control over user synchronization, without requiring changes to the integration configuration.

Exclude Users from Connector Sync

Administrators can exclude Users who are currently synced from a Connector. This prevents the integration from updating those Users while keeping them active within the LMS.

Excluded Users remain fully accessible and can be managed manually within Absorb.

Re-Include Users in Connector Sync

Previously excluded Users can be re-included in the Connector at any time. Once re-included, the integration resumes managing the User during the next sync cycle.

This supports scenarios such as correcting identifier mismatches or re-aligning Users with integration rules.

Granular User-Level Control

Actions are performed at the individual User level, allowing precise control over which Users are managed by the integration without impacting the broader configuration.

This enables more flexible governance, especially for managing sensitive Users or handling edge cases.

Improved Integration Flexibility

Administrators can now adjust User participation in sync processes without dismantling or re-configuring the Connector.

This reduces reliance on support intervention and enables faster resolution of synchronization issues.

Considerations

There are important limitations to be aware of when using this feature.

• Actions are limited to individual Users; bulk updates are not supported.
• The feature applies only to Portals with an active Connector.
• Only Users previously synced by the Connector can be excluded or re-included.
• Users not originally synced from the Connector cannot be excluded.
• There is no dedicated filter to identify excluded Users.