Role‑Based Access Control (RBAC)

The Team Management tab displays administrator teams. Teams allow global partner admins to organize administrators (for example, by customer or function). To create a team, there must be at least two admin accounts; otherwise, an error message indicates that more than one admin is required. When available, clicking New Team opens a form to name the team and select which right admins in this team will have. Teams simplify permissions management by allowing partner admins to grant or revoke access to entire groups of administrators.

Click New Team to create a team.

Partner actions can be hide out from the admins by selecting No Permission. Read Only access will give them the right to check for settings but they will not be able to edit them. While Read & Write will give a complete control over these actions. In the same way, No Permission on Customer Access will hide that customer from those admins in this team. Read Only admin would only be able to check those customers while Read & Write permission will make those admins the partner admin for those customers.

Add admin users to the team from the Member section which you can access through the menu of that team or by clicking the number on the Members column where teams are listed.

When a partner admin switches into a specific customer, a different RBAC layer governs that customer’s environment.

Admin privileges at the customer level can be assigned per user via the Admin column on the Users menu. Users marked as Admin can manage policies and users for that customer but do not have partner‑wide access. There is also a seperate Admin Users & Teams menu on the customer level which can be used to create multiple Teams for customer’s internal usage. * No Access means only Dashboard visibility without any access to any configuration settings including policies, users, etc. * Read Only means all settings can be accessed without any edit permission. * Read & Write gives complete control over the customer.