Considerations

Review key considerations for SAML and SCIM mapping, API support, and current limits on granular setting selection.

Things to keep in mind regarding the new groups and settings management experience

SAML mapping is authoritative and removes users from non-matched groups at each login

When SAML mapping is configured—with or without multi-mapping enabled—it becomes the authoritative source for group membership. At each login, the SAML assertion determines group assignments, and the user is removed from any group not matched by the assertion. Manual and SAML-based group assignment cannot be mixed for the same user. If an organization uses SAML mapping for group management, it should be applied to all group assignments for SAML-mapped users.

SCIM and SAML multi-mapping should not be configured with conflicting group information

While SCIM group push and SAML multi-mapping can coexist on the same account, they should not be configured with conflicting group assignments. If SCIM and SAML assign a user to different groups, the two mechanisms will conflict. SCIM updates occur within an hour of changes in the identity provider, while SAML requires the user to log in again. From a timing perspective, SCIM would likely take precedence if both are processing the same change.

Groups APIs remain fully compatible

The existing Groups APIs remain fully compatible with the new experience for legacy operations, including user assignment, group creation, and group listing. Features introduced with the new experience, including group cloning, priority management, and granular setting configuration, are currently available only through the Admin console web UI.

Granular per-setting selection is available for several primary settings areas

Individual setting selection within product categories is currently available for the following primary settings areas:

• AI Companion

• Audio Conferencing

• General

• Meetings

• Recording & Transcript

• Webinars