When you assign a user to a custom admin level, you can control what permissions the user has, allowing you to limit the scope of actions that the user is allowed to perform. To learn more about custom admin levels, view Custom Admin.

The permissions that you can assign to a custom admin level are less granular than the permissions available in the permission tree of a role. As a result, there may not always be a one-to-one match between the permissions that a role has and the permissions that a custom admin can have.

The permissions of a custom admin are grouped into categories (e.g., Users and groups, Reporting), and within each category you can choose whether you want to assign View or Modify permissions to a user. When you migrate a role to a custom admin level, you may have to decide on a case-by-case basis whether a particular role will have more or less permissions when recreated as a custom admin level. To learn more about permission categories and what the View or Modify permissions allow a custom admin to do, view About custom admin level permissions.

To recreate a role as a custom admin level, follow the instructions here: Manage custom admin levels in the new Admin Console

If you have a role created in the old Admin Console and it has not been recreated as a custom admin level in the new Admin Console, then when the admin who has the role logs in to the new Admin Console, they will get a 403 Forbidden error.

If a custom admin level has no corresponding role created in the old Admin Console, then when the admin with the custom admin level tries to log in to the old Admin Console, they will get a Login forbidden error.