Permissions system migration guide

How it works

Previously, account administrators had to manage client-side users, server-side users, and administration rights separately. Separately administering accounts required a lot of time and effort to audit each user’s viewing and editing rights as well as manage their access to profiles.

Tealium now provides a unified permissions system that lets you manage user access to your account and profiles through permission groups and admin roles. Permission groups can manage user access to both client-side and server-side profiles, simplifying the process of assigning and managing permissions.

For more about the new permissions management system, see Platform Permissions System.

Terminology

Before you plan out your migration strategy, review the following basic concepts:

• Product: A grouping of features licensed at the account level (for example, Customer Data Platform (CDP), Event Streaming API Hub, Tag Management, etc.)
• Feature: A subsection of a product that allows management and access to data and configurations.
• Account: Contains configuration and access that spans multiple profiles.
• Profile: A configuration set for either server-side or client-side products and features.
• User: An individual login to an account, defined by the user’s email address.

The platform permissions system introduces the following two new concepts:

• Permission group: (usually referred to as group) defines a set of access levels to product features in specific profiles. They also determine access to publishing. Users in a group receive permissions for the associated profiles, making it easier for you to manage permissions for a large number of users.
• Admin role: grants access to specific account-level features. Use admin roles to delegate specialized or highly sensitive responsibilities to trusted members of your team. Users without admin roles receive a basic user role.

To access Tealium, users must be assigned to one or more permission groups that provide the necessary product and feature permissions.

Tealium’s project rollout plan

We plan to roll out platform permissions in the following steps:

1. All new customers after December 18, 2023 use platform permissions to manage their Tealium account.
2. Existing customers are migrated to EEA platform permissions without Permissions Enforcement enabled, so they can continue to use legacy permissions until they are ready to migrate.
3. Tealium assists existing customers with setting up platform permissions for their accounts.
4. Customers enable Permissions Enforcement to change from legacy to platform permissions.
   • If your users encounter problems, disable Permissions Enforcement to roll back to legacy permissions while you diagnose and fix the problems.
5. When all customers are on platform permissions, platform permissions EEA becomes platform permissions GA.

Benefits of migration

Migrating from the old permissions system to the new one gives you an opportunity to audit the permissions, security, and structure of your account:

• Remove users who no longer use the platform or work for your organization.
• Use admin roles to delegate account management responsibility to others.
• Remove unnecessary levels of access on the platform.
• Organize access to profiles for easier management.
• Give permission groups descriptive names for easier security auditing and management.
• Gather data for any future plans to break up profiles into multiple regional profiles to better handle regional brands, offices, management structures, and data privacy compliance regulations.
• It is easier for Tealium Support to assist you with access issues on the platform permissions system than with the legacy system.