Manage group access, role changes, offboarding, and SCIM-managed users.
After SCIM provisioning is configured, your identity provider becomes an important part of ongoing Appspace user and group management.
A clear group strategy can help automate access while making onboarding, role changes, and offboarding easier to manage.
Plan your provisioning groups
Provisioning groups can be organized around the Appspace roles, licenses, features, locations, or responsibilities used by your organization.
For example, your organization may choose groups for:
- Account Owners or IT administrators
- Location Administrators
- Publishers
- Authors
- Premium-enabled users
- Space Reservation users
- Workplace Communications users
- Visitor Management users
These are examples only. Use the group names and identity governance model that best fit your organization.
Use provisioned groups to manage Appspace access
After a group has synchronized to Appspace, it can be associated with Appspace access and functionality.
Depending on your configuration, a provisioned group can be used to assign:
- Roles and permissions
- Licenses
- Channels
- Channel groups
This allows membership in the identity provider group to become part of the user's Appspace access lifecycle.
Keep authentication and provisioning separate
SCIM provisioning controls which users and groups exist in Appspace, but it does not always determine who is allowed to authenticate.
For example, if Microsoft Entra ID is configured to require application assignment, a user can exist in Appspace through SCIM but still be unable to sign in until they are assigned access to the Appspace enterprise application.
Consider both provisioning and authentication policies when designing your access model.
Handle role changes
When a user's responsibilities change, update the user's group membership in your identity provider.
For example, a user moving from an Author role to a Publisher role may be removed from one provisioning group and added to another.
Using identity provider group membership for these changes reduces the need to update individual Appspace users manually.
Handle user offboarding
When a user leaves the organization, remove the user from the applicable Appspace provisioning security groups in your identity provider.
This allows Appspace access to be revoked or adjusted without changing the underlying group structure.
Users removed through the provisioned group workflow may appear as Suspended in Appspace.
Use separation of duties when deleting groups
Avoid having an administrator delete a provisioning security group that they are currently a member of.
For cleaner governance and to reduce the risk of accidental access issues, have another administrator or identity-management owner perform the deletion.
Remove a provisioned group
If a provisioned group is no longer needed, remove it in a controlled order.
- Review the group membership and any Appspace roles, permissions, licenses, channels, or channel groups associated with it.
- Remove or update those assignments as needed.
- In Appspace, locate the provisioned group in the applicable Users, Groups, or identity integration area.
- Delete the group from Appspace.
- After the group is no longer referenced in Appspace and its users have been addressed, remove the group from Entra ID or Okta according to your organization's identity governance process.
Deleting a group from Appspace does not automatically delete the corresponding group from your identity provider.
Repush a group from Okta
If a pushed Okta group is deleted directly from Appspace, Okta may not be able to push that same group again immediately.
Unlink the existing group relationship in Okta and add the group again before attempting to push it back to Appspace.
What happens when User Group Sync is disabled?
Disabling User Group Sync stops group synchronization, but it does not automatically delete groups that were previously synchronized to Appspace.
Remove those groups manually if they are no longer required.
Review your governance model regularly
Periodically review your provisioning groups and their Appspace assignments to confirm that they still match your organization's roles, licensing model, locations, and access requirements.
This is especially important after organizational changes, license changes, or updates to your identity management structure.

