Roles and access control
This article refers to Platform v3.0.0. The current Platform version is v3.2.0.
Overview
Barbara Panel uses a Role-Based Access Control (RBAC) model to govern what each user can see and do across your organization. Four roles are defined; each user is assigned exactly one of them. Understanding the responsibilities of each role is the first step to operating the platform safely and respecting your data-protection and compliance obligations.
User roles can only be assigned or modified by users with the Administrator role.
The internal identifiers used by the platform API are:
| Role | API identifier |
|---|---|
| Administrator | role_company_admin |
| Supervisor | role_company_edit_plus |
| Editor | role_company_edit |
| Viewer | role_company_read |
Administrator
The highest-level role, intended for top-level operators of the platform. Administrators have unrestricted access to every feature: they can add and remove users, change roles, modify audit logs, and perform every action available in the platform.
Supervisor
The role for senior operators or operations team leads. Supervisors can perform almost every action a user might need:
- Run firmware updates, power-offs, and batch operations.
- Delete critical assets — devices, custom images.
- See and edit sensitive material — Secrets and Credentials.
Supervisors cannot change user roles or modify audit logs.
Editor
The default role for team members handling day-to-day operations:
- Download OS images.
- Activate and operate nodes.
- Upload, configure, and run applications.
Editors cannot see secret values they didn't set themselves; the Secrets and Credentials cards mask values for them.
Viewer
A read-only role for users who must stay informed but should not operate the platform:
- See basic company information.
- Read node status, deployed applications, and real-time telemetry.
- No write operations of any kind.
Summary
Pick Administrator for platform owners, Supervisor for senior operators who need write access on every critical asset, Editor for the default day-to-day user, and Viewer for read-only stakeholders. The mapping to the API identifiers above is the source of truth used by every backend authorisation check.