Docs/Aigovernance/Rbac

Access Control (RBAC)

ANTS Platform controls access with roles. Access is who + role + where: a person holds a role of one product, in the whole organization or in one project. The platform turns roles into permissions and checks them on every request.

ℹ

Roles are managed in the app, not through an SDK. Assign them under Organization Settings → Members. Build your own AI governance roles under Organization Settings → Custom Roles (Enterprise).

Two products

ProductCoversRoles
AI governanceDiscover AI, Gauge AI, Tracing and Sessions, Datasets, Governance, and AI governance settingsGovernance Owner, Security & Compliance, Cost Analyst, Governance Viewer, Auditor, End User, No access, and custom roles
Budget AIThe AI gateway: keys, budgets, departments, models and routingBudget AI Owner, Budget AI Viewer, Budget AI Department Admin, Budget AI Department Viewer

Nothing is implied across products. An AI governance role, including a custom role, gives no Budget AI access, and a Budget AI role gives no AI governance access. Owner (per organization) and Super Admin (the whole platform) have full access to both. The Platform Viewer option in Members gives Governance Viewer and Budget AI Viewer together. See Members & Roles.

Each product also manages its own people: a Governance Owner grants only AI governance roles, and a Budget AI Owner grants only Budget AI roles.

The model

ConceptWhat it is
MembershipA person's link to an organization (organization role) and, optionally, to a project (project role).
RoleA built-in role of one product, or an organization-defined custom role (AI governance only).
ModuleAn area of AI governance: Discover AI, AI TrailMaps, Gauge AI, Governance, Datasets and experiments, Audit & Export, PII / raw-prompt content, Data export, User data export, AI Agent data export, User & role management, Custom-role authoring, Integrations & service accounts, Tenant security & data retention, Billing & subscription, Ants Assist, AI tool access requests, Support tickets, Support settings.
Sub-moduleA page or settings surface inside a module, for example Risk Dashboard inside Governance.
Access levelNo access, Read, Read & Write or Admin. Each module and sub-module offers only the levels that apply to it.

A sub-module inherits its module's level unless a custom role sets it explicitly. Built-in roles set module levels only, so every page in a module follows the module.

Organization and project scope

  • The organization role applies in every project, now and in the future. New organization-level grants accept only Owner, Governance Owner, Governance Viewer, End User, No access and custom roles; Security & Compliance, Cost Analyst and Auditor are given per project.
  • A project AI governance role replaces the organization role inside that project, in either direction.
  • Budget AI roles add up: an organization-level Budget AI role applies in every project, and project or department roles add to it.
  • A member whose organization role is No access sees only the projects where they hold a project role or a Budget AI role. This is how you give an external auditor access to one project.
  • Organization-level views that span projects, such as Audit Logs and the Executive overview, show a member only the projects they can access.

Project roles need the rbac-project-roles entitlement. See Members & Roles.

Built-in roles at a glance

ModuleOwnerGovernance OwnerSecurity & ComplianceCost AnalystGovernance ViewerAuditor
Discover AIFullRead & WriteReadReadRead-
Gauge AIFullRead & WriteReadRead & WriteRead-
GovernanceFullAdminAdmin-ReadRead
Budget AIFull-----
Audit & ExportFull-Read & Write--Read
PII / raw-prompt contentRead-Read---
User & role managementFullRead & Write----
Tenant securityAdmin-Admin---

End User has no module access beyond the agents they own. Project Admin (formerly Department Admin) and Manager Viewer are no longer offered; existing holders keep them. Budget AI comes from Budget AI roles. The full matrix, including settings tabs, is on Members & Roles.

Super Admin

A Super Admin has Owner rights in every organization and manages the platform from Platform in the account menu: organizations (create, rename, suspend, delete, manage Owners), the list of Super Admins, and platform settings. Only a Super Admin can remove or change an Owner. Every Super Admin grant and removal, and every time a Super Admin opens prompt content, is written to the audit log. See Super Admin.

Agent ownership

Ownership of an AI agent adds access on top of a role, for that agent only. A member who owns an agent but whose role does not include AI Agent Center, Tracing & Sessions, the Gauge AI dashboards or a Governance page, such as End User, sees those pages with data from their own agents only. Whether they also see their agents' prompt and response content is decided by the organization switch Agent owners can see prompts and responses (Hidden by default); when hidden, they get the content-free view. Ownership never narrows a role: a member whose role already includes a page keeps the full view.

In Governance, owners read the Risk Dashboard, AI Guardrails (read only), AI Violations, Available Requests, Evidence Collection, Framework Coverage, and their agents' profiles and drift alerts (read only), can fill in and submit their agents' compliance assessments, and can export evidence for them. They cannot create or delete governance profiles, change guardrail policies, approve assessments, or open My Requests and Audit & Export. Nobody can approve or send back an assessment they submitted. See Agent owners.

Assigning owners is member management: it needs userRoleManagement.projectMembers:write, and nobody can grant ownership that gives more access than they hold, including prompt content. Among the built-in roles only Owner can do it, and only an Owner can make themselves an owner. Owner changes are written to the audit log. See Agent owners.

Agent tool governance

An agent's tool permissions, approvals and behaviour settings follow the Agent Profiles & Drift permission under Governance: Read to view them, Read & Write to change them and to approve or deny tool calls. Among the built-in roles, Owner, Governance Owner and Security & Compliance can change them. Nobody can decide an approval request made for themselves.

Prompt and response content

The text of prompts and responses is protected by its own gated permission, PII / raw-prompt content. It covers trace and session input and output, observation bodies and metadata, and the flagged content behind AI Violations. Dashboards, counts, trace lists and violation summaries do not need it.

Among the built-in roles only Owner and Security & Compliance hold it. Everyone else who can see traces opens them in a content-free view: timings, cost, tokens, model and scores are shown, and content shows Content hidden. Their exports run with content left empty. In a custom role the permission is marked Sensitive, and it cannot be combined with data export.

Three switches under Organization Settings → Security can show content to agent owners, Governance Owners (AI agent traces) and Budget AI Owners (Budget AI traces). See Content switches.

Separately, the Trace input and output feature switch under Organization Settings → Features hides prompts and replies for everyone in the organization or in selected projects. See Data Privacy.

Separation of duties

The platform prevents one person from holding duties that are meant to check each other:

  • Custom roles cannot combine user and role management with audit log access, user and role management with tenant security administration, or prompt content with data export. The role editor explains the conflict and refuses to save.
  • No self-escalation: nobody can grant a role that includes permissions they do not hold, and nobody can change their own access, Owners and Super Admins included. Nobody can edit a custom role they hold.
  • Custom-role authoring is Owner-only and can never be granted through a custom role.
  • Owners are changed only by a Super Admin.
  • The built-in roles follow the same split: Governance Owner manages people but has no audit log, prompt content or tenant security access. Security & Compliance administers security but cannot manage members.

Enforcement and audit

  • The sidebar and settings tabs only show what a role grants, but the decision is made on the server. Every page, API call and settings tab belongs to one product and is checked against it, and a refused call is logged as a denied action.
  • Sensitive changes (changing roles and Budget AI roles, creating or editing custom roles, adding or removing Super Admins) require step-up verification.
  • Membership changes, invitations, role changes, custom role changes, Super Admin and Owner changes, and access to sensitive settings pages are written to Audit Logs.
  • Some pages also need a plan entitlement or a feature to be enabled, whatever the role. See Billing & Plans.

Learn more

© 2026 ANTS Platform, Inc.Docs v1.0 · Last updated June 2026