Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Roles (RBAC — 5 levels)

On this page (11)

Role-based access control (RBAC) defines what each person can do. There are 4 workspace roles (with cumulative inheritance) plus 1 organization role, which is orthogonal.

The 5 roles#

Workspace (cumulative inheritance owner ⊇ admin ⊇ member ⊇ viewer):

RoleProfileSummary
viewerConsumessees dashboards and reports
memberBasic analysteverything viewer has + interacts (filters/drill) and exports
adminOperatoreverything member has + runs queries/refresh/AI, manages content, sources, people and keys
ownerOwnereverything admin has + billing, workspace deletion and role assignment

Organization (separate dimension):

RoleProfileSummary
org_adminAdministers the structuremanages the org's workspaces/members/settings — no access to data

owner is structural (the workspace owner). A regular member never becomes owner through configuration — the boundary is fail-closed.

Role × capability matrix#

Action (RBAC)viewermemberadminownerorg_admin
dashboard viewing / report viewing✓✓✓✓—
data interaction (filters/drill)—✓✓✓—
data export—✓✓✓—
data.query.run——✓✓—
refresh.trigger——✓✓—
AI features——✓✓—
dashboard management / report management——✓✓—
source.manage——✓✓—
member.manage——✓✓—
apikey.manage——✓✓—
workspace.settings——✓✓—
billing.manage———✓—
workspace.delete———✓—
role.assign———✓—
org.workspace.manage————✓
org.member.manage————✓
org.settings————✓

Availability#

  • Plans: all. RBAC is a core security feature.
  • How it works: deterministic matrix, covered by automated tests.

Permissions#

  • Only the owner can assign roles (role.assign).
  • admin can manage people (member.manage), but not billing or deleting the workspace.

Setup#

  • The member's role comes from permissionsJson.role (admin / member / viewer).
  • Missing/invalid role → member (legacy default); unknown value or an attempt at owner via JSON → viewer (fail-closed).
  • The org_admin role is assigned in the organization context.

Validation (fail-closed)#

  • Unknown/garbage role → treated as viewer (least privilege).
  • Unknown action → denied (it doesn't belong to any set).
  • org_admin only enables org.* actions — never workspace data.

Example#

At Comércio Aurora: Maria is owner (does everything, including billing). João is admin (runs pipelines, manages sources and people, but doesn't handle billing). Ana is member (interacts and exports). Managers are viewer. In Grupo Aurora, João is also org_admin to administer the organization's structure — without seeing the sales data because of it.

Cost#

  • RBAC uses no cloud resources: R$ 0.

Security#

  • Fail-closed at every boundary; least privilege as the default.
  • RBAC is a check made before the account-in-good-standing check: a role without the capability → 403 without even querying the central billing service.
  • org_admin isolated from data (the org is structural).

Limits#

  • 5 fixed roles (4 workspace + 1 org). Fully custom roles are not part of the current product.
  • For row-level restriction (e.g., only your own branch), RBAC isn't enough — use RLS/ABAC.

Troubleshooting#

SymptomLikely causeWhat to do
Member can't handle billingonly owner has billing.manageaction exclusive to the owner
"Action not allowed for the role"role below what's requiredraise the role (owner assigns)
org_admin can't see dataexpected behaviorbecome a member of the target workspace
Role "dropped" to viewerinvalid JSON / attempt at ownercorrect the role to admin/member/viewer

Next steps: Row-level security (RLS).

Related links