Access Management Migration Scenarios
Concrete examples of how Access Management migration works in different scenarios.
less than a minute
Permissions Management (RBAC) deprecation timeline
The legacy Permissions Management (RBAC) system will be deprecated on October 31, 2026. RudderStack recommends completing your migration before this date.
This section provides concrete examples of how permissions from the legacy Permissions Management (RBAC) system map to the member’s workspace policy in the new Access Management system depending on different scenarios.
Note that:
- The examples in this section assume the user is a Member within the organization, as Admins have full access to all resources by default.
- These examples also apply to Service Access Tokens created in the legacy RBAC system.
- These examples reflect the Import members with policies strategy (Use existing policies), where existing resource and Data Privacy (PII) permissions are preserved during import.
If you choose Import members (Start fresh), member permissions are not preserved from legacy roles. Review and configure both resource and PII permissions in staging before deployment.
In this section
| Guide | Description |
|---|---|
| No Resource-level Permission Restrictions | Migration scenarios when users have no resource-level permission restrictions in their access policy |
| With Resource-level Permission Restrictions | Migration scenarios when users have resource-level permission restrictions in their access policy |
