Skip to main content
RBAC groups permissions into roles like admin, member, and viewer. Users are assigned to roles instead of individual permissions. When to use RBAC:
  • Organization-level Roles: RBAC can simplify user management and match real-world organizational hierarchies.
  • Resource-specific Permissions: Define roles on resources to grant users resource-specific permissions.

Organization level roles

Use RBAC to simplify user management and match real-world organizational hierarchies.

Resource-specific roles

Define roles on resources to grant users resource-specific permissions.

Global roles

Use global roles to give users application-wide permissions across all resources. This is common for internal tools and super-admin functionality.

Resource ownership

Use this pattern to grant additional permissions to resource creators or owners.

Additional RBAC patterns

Explore these additional role-based patterns:

Next steps

After you’ve defined your RBAC policy:
  1. Add facts: Store user roles and resource relationships in Oso Cloud
  2. Make authorization requests: Check permissions in your application code
  3. Test thoroughly: Verify your policies work with test scenarios and realistic data