# Access Management Migration Scenarios


{{< announcement >}}
**Permissions Management (RBAC) deprecation timeline**

The legacy [Permissions Management (RBAC) system]({{< ref "access-management/glossary.md#role-based-access-control-rbac" >}}) will be **deprecated on October 31, 2026**. RudderStack recommends completing your migration before this date.

- [Understand the pre-migration considerations]({{< ref "access-management/pre-migration-considerations.md" >}})
- [Start your migration now]({{< ref "access-management/migration-steps.md" >}})
- [Learn how the migration works]({{< ref "access-management/how-migration-works.md" >}})
{{< /announcement >}}

This section provides concrete examples of how permissions from the legacy Permissions Management (RBAC) system map to the member's [workspace policy]({{< ref "access-management/concepts.md#workspace-policy" >}}) in the new Access Management system depending on different scenarios.

{{< info >}}
Note that:

- The examples in this section assume the user is a [Member]({{< ref "archive/dashboard-guides/user-management.md#organization-roles" >}}) within the organization, as Admins have full access to all resources by default.
- These examples also apply to [Service Access Tokens]({{< ref "archive/dashboard-guides/service-access-tokens.md" >}}) created in the [legacy RBAC system]({{< ref "archive/dashboard-guides/user-management.md" >}}).
- 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.
{{< /info >}}

## In this section

| Guide | Description |
|-------|-------------|
| [No Resource-level Permission Restrictions]({{< ref "access-management/migration-examples/no-resource-level-restrictions.md" >}}) | Migration scenarios when users have no resource-level permission restrictions in their access policy |
| [With Resource-level Permission Restrictions]({{< ref "access-management/migration-examples/with-resource-level-restrictions.md" >}}) | Migration scenarios when users have resource-level permission restrictions in their access policy |