Role-Based Access Control (RBAC) enables the management of user permissions across infrastructure: public and private clouds, containers, hypervisors, and bare-metal devices. Each organization can have a number of teams, each with different access policies to the infrastructure.
Note: Each organization will require a subscription plan.
RBAC workflow for an account owner
Rules will apply to all team members
Organizations, Teams, and Rules are created by an account owner. A policy is always associated with a Team. Rules are always associated with a Policy and define Member’s permissions. Example:
- An account owner can create Rules which reside in a policy that specifies the public clouds a team member can provision a virtual server on.
Rules are always assigned to a Team rather than directly to Members. To grant permissions to a Member, you first need to assign a member to a Team. Members inherit access permissions from the Team. A Member can belong to more than one Organization and/or Team.