As we continue transitioning accounts from legacy Groups (Sharing) to the Lucid teams experience, we want to share some critical preparation steps and specific behaviors for accounts utilizing SCIM provisioning.
Required action
Your account admin must complete the SCIM migration survey located directly in your Lucid admin panel and self-serve migration steps
- Complete the SCIM migration survey: If you haven’t already, navigate to the Lucid admin panel and complete the two-question survey regarding your current configuration. The survey is located in a banner at the top of the admin panel overview page. Once the survey is submitted a self-serve SCIM migration path will appear. Please complete these steps by Sept. 8. Account owners and account admins can respond to the survey. Only one response is required.
- Check for group hierarchy: If your Identity Provider (IdP) contains a group hierarchy structure, you must remove this hierarchy prior to migration. Leaving a group hierarchy will cause the SCIM sync to flatten your group structure, meaning the system will behave as if no hierarchy exists at all. While groups will still sync, no membership will be inherited from parent to child groups, and users who previously held group membership via the hierarchy will lose access to those groups.
Going forward, we recommend avoiding hierarchical structures in your IdP for Lucid provisioning.
How your groups will migrate to teams
SCIM-enabled accounts feature a few distinct behaviors designed to protect your provisioned data:
- User roles: All users will be added as team members with “Edit and share” permissions by default.
- Flattened nested groups: Lucid teams do not support nested sub-teams. Consequently, any child groups from the legacy experience will be converted into standalone Lucid teams, and their original parent-child relationships will be removed. While groups will still sync individually, membership inheritance is no longer supported. Users who previously accessed parent groups via a child group will lose access and must be assigned to those teams directly.
- Naming conflicts favor your IdP: If a legacy group being migrated has the same name as an existing team already in your account, the existing team will be renamed ("Team" becomes "Team (1)"). This ensures the newly migrated team perfectly matches the group name coming from your SCIM sync.
- Empty and inactive groups: All empty and inactive groups will be migrated as active teams to ensure they remain fully aligned with your current IdP sync configurations.
- Salesforce User Group: The Salesforce User Group will maintain existing users and permissions but will now link to Lucid teams instead of Groups (sharing), appearing under the teams tab in the admin panel. This will not affect your current Salesforce integration or team folders, and all associated content and permissions will remain intact.
[Optional post-migration] Clean up duplicate teams
Migrating your IdP groups alongside existing teams may create duplicates if they share the same name. There are two ways to quickly clean these up if desired:
- Bulk archive duplicate teams
- Merge duplicate teams into one
Bulk archive
Use the bulk archive option by following these steps from the Lucid admin panel:
- Click Groups from the navigation menu on the left.
- Select Teams.
- Check the box next to each duplicate team you want to remove.
- Click Bulk actions from the top-right of the list.
- Select Archive teams.
- Review the information and click Archive.
You can restore archived teams by following the steps in our Lucid admin panel: Group management article.
Merge teams
Merge duplicate teams by following the steps below from the Lucid admin panel. Merging teams moves team members and content to the destination team and permanently deletes the original team in Lucid. After merging, deleted teams cannot be retrieved.
- Click Groups from the navigation menu on the left side of the admin panel.
- Select Teams from the dropdown menu.
- Click the three-dot menu to the right of the team you want to merge another team into.
- Select Merge team.
- Use the dropdown to select the team you want to merge with.
- Click Merge teams.
Note: If you use an IdP, it remains your source of truth for teams. This means that merging a team into a different SCIM-managed team transfers content only, and will not transfer membership. The original team in Lucid is then automatically deleted. Team members cannot be manually merged into a SCIM team, as the IdP must remain the source of truth. If you need to update team membership, you must do so in your IdP.
Questions or feedback?
If you have any questions about these steps, let us know in the comments below! If you are a user on a FedRAMP account, please reach out directly to our support team using this form.
Your privacy choices
