General Strategy
This document describes a general strategy to follow when building a migration plan for the permissions system.
General migration strategy
Use the following steps to help you build your migration strategy:
- Make an inventory of your users’ current access levels and permissions.
- Audit those permissions to ensure they’re accurate for the users’ needs.
- Analyze the results of your audit to determine logical functional groups.
- Add permission groups to match those bundles of access rights to profiles and product features.
- Add users to those permission groups.
- Assign admin roles to users in your account to delegate management of users, features, and profiles.
- Set PII permissions for each user.
- Test the permissions with your users.
- Test saving and publishing rights with your users.
- Adjust the permission groups and admin roles as needed.
If you need assistance with this process, please contact Tealium Support.
Migration suggestions
Some important things to consider as you plan your migration:
- Non-disruptive migration - Building your permissions groups and admin roles under the platform permissions system will not disrupt your current permissions and access. Your account continues to use the legacy permissions until you enable Permissions Enforcement to use the platform permissions system. If you have any major problems with the platform permissions system, you can switch back to the legacy system to make any necessary changes.
- Permission groups are cumulative - You can create a permission group with view rights on one profile, create another permission group with editor rights on other profile, and then add a user to both. The user inherits permissions from both groups, and if the permissions overlap, the user inherits the greater permissions for a resource.
This page was last updated: December 7, 2023