Advanced RBAC

Enterprise (advanced_rbac entitlement). Grant exactly the access each person needs, down to a single action or a single request. The core role model (org owner/admin/member plus team leads) is free and covers most teams. Advanced RBAC adds two layers on top when fixed roles stop being enough: custom roles with wildcard permissions, and ABAC policies for attribute-based rules.

Custom roles

A custom role is a named, org-scoped set of permission strings, assigned per-user in addition to their core role. Create one under Settings, or via the API. A role is just a name, a description, and a permission list:

{
  "name": "agent-operator",
  "description": "Run and inspect agents, read everything else",
  "permissions": ["agents:*", "*:read"]
}

Assign or unassign a role per user, disable a role without unassigning it (active: false), and read a user’s effective permissions (the union across their active custom roles). All RBAC management requires org admin/owner. The full endpoint list is in the API reference.

Permission format

Permissions are resource:action pairs with wildcards on either side:

Role names are unique per org; permission lists are normalized (trimmed, deduplicated) on save.

ABAC policies

When a rule depends on values rather than resource types (“deny agent execution when amount > 10000 unless the caller has the finance role”), use an ABAC policy:

{
  "name": "block-large-amounts",
  "effect": "deny",
  "action": "agents:execute",
  "conditions": [
    { "attr": "resource.amount", "op": "gt", "value": 10000 }
  ],
  "priority": 100
}

• Conditions are {attr, op, value} triples, ANDed together. attr is a dot-path into the evaluation context (subject.*, resource.*, context.*). Operators: eq, neq, gt, gte, lt, lte, in, nin, contains (e.g. subject.roles contains "finance").
• Evaluation is deny-overrides: if any applicable deny policy matches, access is denied regardless of allows. Otherwise the highest-priority matching allow wins.
• Policies are immutable: delete and recreate to change one.

How the layers combine

Core roles answer “is this person an admin?”; custom roles answer “does this person hold agents:execute?”; ABAC answers “is this particular request allowed?”. Custom roles are purely additive (they never reduce what a core role grants), while a matching ABAC deny beats everything.