- Introduction
- Access control
- Account management
- Role-based access control (RBAC)
- Managing access
- Managing projects
- Licensing
IXP overview guide
Role-based access control (RBAC)
The role-based access control (RBAC) in IXP is integrated with the AuthZ authorization system RBAC service of Automation Cloud. This integration allows you to assign roles to Automation Cloud user groups in IXP. For more details on Automation Cloud groups, check the About accounts and groups and Managing access pages.
The RBAC experience is available to all IXP users in Automation Cloud. Initially, RBAC is available for any newly created tenants, followed by its availability for existing tenants once they have been migrated to the new experience.
If you integrate with Automation Cloud through SSO, you can manage permissions through Automation Cloud user groups. Next, you can apply these permissions in IXP to ensure a seamless and consistent access control experience. For more details, check Understanding authentication models.
Beginning in the week of February 24, 2025, existing IXP tenants will be migrated to the new role-based access control (RBAC) experience. RBAC is integrated with Automation Cloud through the AuthZ authorization system, and allows administrators to provision roles to Automation Cloud groups as well as users.
The goal of the new experience is for the IXP access management to be properly integrated with Automation Cloud, and allow users to assign roles to Automation Cloud groups instead of just users.
IXP does not yet support custom roles. Therefore, we have mapped the granular Communications Mining legacy permissions to a set of temporary legacy roles. These will be deprecated in the future, when custom roles are supported.
The legacy roles are an exact mapping of the old permissions that required migrating, to ensure that none of the underlying permissions of the users were changed in the migration. For a complete list of the roles, check Legacy roles.
After the migration, your existing permissions are preserved; first through Automation Cloud roles. Then, we have used legacy roles to cover any gaps with additional permissions.
