professional plan

Role-Based Access Control

Control who can view and edit tests, per project.

What It Does

Role-Based Access Control gives each person the access their work needs. Administrators manage users, roles and settings. Contributors create and edit tests and workflows. Reviewers and Readers view tests, workflows and reports, and Reviewers also triage security findings. Administrators can change what any role is allowed to do, and a user can hold a different role on each project. Writes across tests, endpoints, projects, users, roles and settings are recorded with the user, timestamp, IP address and before and after values, which gives your auditors access-control and change-history evidence for frameworks such as SOC 2 and ISO 27001.

Role-based access control matrix: Administrator can manage users and settings, create and run tests and view results; Environment Manager and Reader can view results; Contributor can create and run tests and view results. A contributor running a pack is allowed, a reader editing a test is blocked with 403 by the server, and changes are recorded in the audit trail

Overview

Five built-in roles — Administrator, Contributor, Reviewer, Reader and Environment Manager — drawn from a catalogue of 53 permissions in 12 categories that administrators can tailor for their organisation. A user can hold a different role on each project, and the project role overrides the global role inside that project. Permissions are checked by the server on every gated route, including test cases, users, roles, settings, comments and security testing. Platform API keys can never exceed the permissions of the person who created them, and each user is limited to one signed-in machine at a time. Changes to tests, endpoints, projects, users, roles and settings are recorded in the audit log with before and after values.

Key Capabilities

Five built-in roles: Administrator, Contributor, Reviewer, Reader, Environment Manager
Per-project roles that override the global role inside that project
Invite collaborators with specific role assignments via email
53 permissions in 12 categories, editable per organisation with lockout protection
Permissions checked by the server on every gated route
Role assignments visible in each project’s Members tab

How It Works

  1. 1

    Invite team members by email with a role; the invitation link is valid for 72 hours

  2. 2

    Give someone a different role on a single project from its Members tab

  3. 3

    Tailor what each role can do under Role Permissions

  4. 4

    Changes are recorded in the audit log with user, timestamp and before and after values

  5. 5

    Administrators can review and change role assignments at any time

Available on

professional Plan & Above

Upgrade to the professional plan to unlock this feature.

Available on Professional plan and above
See pricing →

Built for regulated teams

Teams in regulated industries rely on this capability to ship API changes with an audit trail.

Try RBAC Today

Start your 15-day free trial — no credit card required.