Skip to content

Role-Based Access Control (RBAC)

The new RBAC is a major overhaul of Escape's access control system. At the core of this system lies the concept of Projects, a powerful abstraction for grouping resources at the organization level and managing access to entire scopes at once. Projects can be nested, and all resources and pages are properly scoped to a user's access level.

Role-Based Access Control (RBAC) is a cornerstone of modern access management, ensuring users have the exact permissions they need—no more, no less. Escape's RBAC features allow organizations to define roles and permissions with precision, ensuring robust security and streamlined operations.

Built-in Roles

When you create an organization, Escape seeds two roles. You can create additional roles from the permissions below. See Roles management.

Role Description
Admin Includes the Admin permission. Supersedes all other permissions on the scope where the role is bound.
Viewer Includes the Viewer permission. Read-only access to pages and resources. Can't edit anything.

A project-scoped Admin can manage resources in that project. It can't manage organization-wide users, roles, or settings. Those actions need a global Admin binding. See Access control.

Built-in Permissions

A role is a collection of permissions. Role bindings grant those permissions globally or on a specific project.

Permission Description
Admin Supersedes all other permissions on the bound scope.
Viewer Read-only access to all pages and resources. Can't edit anything.
Edit Assets Create, edit, and delete assets.
Edit Profiles Create, edit, and delete profiles for scanning.
Edit Custom Rules Create, edit, and delete custom rules.
Edit Workflows Create, edit, and delete workflows.
Edit Integrations Create, edit, and delete integrations.
Tag Edition Create, edit, and delete tags.
Manage Reporting Manage reporting settings.