RBAC Identity & Access Manager

Identity

Roles assigned to Alice

Permissions granted to role

Access Request

Live State

Effective Permissions

1 / 5

Roles Assigned

1 / 4

Last Access Check

—

How it works

Role-Based Access Control (RBAC) decouples who from what they can do by inserting roles between users and permissions:

effective_perms(user) = ⋃ permissions(role)
                         for role in roles(user)

grant(user, action, resource) ⇔
  permission(action, resource) ∈ effective_perms(user)

This is exactly the model behind AWS IAM roles, Kubernetes RBAC, Active Directory groups and enterprise SSO: a user's access is the union of every permission carried by every role they hold, not a per-user permission list.

Select a user — loads their assigned roles and recomputes effective permissions.
Toggle role checkboxes — assigning/revoking a role changes the user's edges live and updates the graph and stats instantly.
Select a role, toggle permission checkboxes — editing what a role grants ripples to every user who holds that role (privilege escalation in one place affects everyone assigned to it).
Check Access — runs the authorization decision above; a particle traces the real path user → role → permission, turning green on ALLOW or stopping red on DENY, exactly like a real access-control decision log.

The Roles-Assigned and Effective-Permissions readouts double as a least-privilege audit: a user with many roles but few unique effective permissions has redundant role assignments, and a user whose effective-permission count is far above what their job needs is over-privileged — a common real-world cause of breaches when a compromised low-value account turns out to hold high-value access.

Users Roles Permissions Denied path

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.