Access control

Roles & Permissions

raia cX controls access at two levels that add together: your organization and each individual agent. This page is the reference for what every role can do, which agents each role can see, and how the two grants combine into someone's effective access.

What you will learn

The difference between organization roles and agent roles
What each role can and cannot do
Why some people see every agent and others see only a few
How organization and agent grants combine into effective access
Who can create, publish, and delete agents

Two levels of access

Every permission in raia comes from one of two places. Your organization role is granted once when you join a workspace and governs org-wide capabilities — settings, membership, billing visibility, and whether you can reach every agent. Your agent role is granted per agent on that agent's Security tab and governs what you can do on that specific agent.

Access is the union of the two. An organization role that already covers an agent cannot be narrowed by leaving the agent role off, and an agent role can grant access to someone whose organization role gives them nothing else.

Membership gate

Before any role is evaluated, the person's organization membership must be active. A suspended or inactive member sees nothing at all, whatever roles they hold.

Organization roles

Organization roles are assigned under Organization Management → Users. Owners can assign any role; Admins can assign every role except Owner.

Role	What it can do	Best for
Org Owner	Every capability in the organization: billing and subscription visibility, security and authentication settings, org limits, brand, domains, integrations, API keys, membership, and full access to every agent.	One or two accountable people per organization. Ownership should not be spread widely.
Org Admin	Everything the Owner can do apart from assigning the Owner role itself. Manages members, invites, org settings, agents, packs, and functions.	The platform team that runs raia day to day.
Org Manager	Works across every agent — create, train, export, delete, and manage packs and functions — but cannot touch organization settings, membership, or billing, and has no org-wide conversation oversight.	Agent builders who need breadth across agents without administrative control of the org.
Org User	A member of the organization with no org-level administration. Sees only the agents they hold an agent role on. Can be allowed to create their own agents through an org setting that is off by default.	Business users and contributors who work on a handful of specific agents.
Copilot Admin	A Copilot-only role. Sees every active and draft agent in Copilot, reads all conversations including admin mode, and can assign conversations — but does not configure agents.	Support leads and supervisors who oversee conversations rather than build agents.
Copilot Manager	Chats with every active agent in the organization and can read all conversations in admin mode and review feedback. No agent configuration, no org settings.	Team leads who need visibility across the whole conversation queue.
Copilot User	The most restricted role. On its own it grants almost nothing — it must be paired with an agent-level Copilot User row before the person can see or chat with anything.	Front-line operators assigned to specific agents only.

Agent roles

Agent roles are assigned on the Launch Pad Security tab of the agent itself. They only apply to that agent.

Role	What it can do	Best for
Agent Owner	Full control of the agent: settings, training, skills, scraping, webhooks, limits, documents, user access, export, and deletion. Can assign every agent role.	The single person accountable for the agent.
Agent Admin	Manages the agent day to day — configuration, skills, documents, memory, conversations, and invites. Invites are limited to people who are already members of the organization.	Operators who maintain the agent alongside its owner. This is also the role a self-service creator receives.
Agent Editor	Can work on the agent's content and conversations and add files to memory, and the agent appears in their Launch Pad list. Does not manage access or delete the agent, and cannot read training documents when Document Access is restricted.	Contributors who tune behavior and knowledge without owning the agent.
Copilot Admin (agent)	Reads the agent and its conversations, including admin mode, assigns conversations, and can be assigned to one. No configuration rights.	Supervisors scoped to one agent's queue.
Copilot User (agent)	Chats on the agent and handles conversations assigned to them. Cannot read the full conversation history of other operators and cannot configure anything.	Front-line operators working a single agent.

Which agents each role can see

This is the question behind most access support tickets: someone has been added to the organization but their agent list is empty. The answer is almost always that their organization role is scoped and they have no agent role.

Role	Agents visible	Needs an agent role?
Org Owner	All active and draft agents.	No — access is inherited.
Org Admin	All active and draft agents.	No — access is inherited.
Org Manager	All active and draft agents.	No — access is inherited.
Org User	Only agents where they hold an active Agent Owner, Agent Admin, or Agent Editor row.	Yes — without a row the agent is invisible.
Copilot Admin	All active and draft agents, in Copilot.	No — access is inherited.
Copilot Manager	All active agents. Drafts are hidden.	No — access is inherited.
Copilot User	Only agents where they hold an active Owner, Admin, Editor, Copilot Admin, or Copilot User row.	Yes — without a row they see nothing.

Common cause

An Agent Editor row makes the agent visible in Launch Pad. If someone reports a missing agent, check the agent's Security tab first — an inactive row hides the agent just as effectively as no row at all.

How org and agent roles combine

Organization role	Agent role on agent X	Effective access on agent X
Org Owner / Admin / Manager	Any agent role, or none at all.	Full access to the agent — the organization grant already covers it.
Org User	No agent role.	The agent is invisible to them.
Org User	Agent Editor.	Sees the agent in Launch Pad and can edit its content and conversations.
Org User	Agent Admin.	Manages the agent end to end. This is what a self-service creator gets.
Org User	Agent Owner.	Full control of that one agent, nothing else in the organization.
Copilot User	Copilot User on specific agents.	Chats on the agents they are assigned to, and nothing more.
Copilot Manager	No agent role.	Chats on every active agent in the organization.

Creating, publishing, and deleting agents

Who can create

Org Owners, Org Admins, and Org Managers can always create agents. Org Users can create their own agents only when the organization enables self-service agent creation, which is off by default.

Who owns the result

When an Org Owner creates an agent they become its Agent Owner. When anyone else creates one, they become Agent Admin and the Org Owner becomes Agent Owner — so ownership always stays with the organization.

Draft and active

New agents start as Draft. Draft agents are visible to Org Owners, Admins, and Managers only. Publishing an agent to Active exposes it to Copilot roles across the organization.

Invitations

Org Owners and Admins can invite brand-new external email addresses to an agent. Org Managers, Org Users, and Agent Admins can only add people who are already members of the organization. An org-wide setting can additionally restrict all agent invites to verified email domains.

Reading the agent Security tab

The Security tab of an agent lists people in two groups. Direct rows are explicit agent-role grants on this agent — they can be edited, deactivated, or removed here. Inherited rows are Org Owners, Admins, and Managers who reach the agent through their organization role; they have no row to edit, so removing their access means changing their organization role.

The status dot beside a Direct row is the membership status of that grant: green for active, grey for inactive. An inactive grant leaves the row in place but revokes the access, which is the safest way to pause someone without losing their configuration history.

Practices worth adopting

Grant the narrowest role that still lets someone do their job — Agent Editor is the right default for most contributors.
Keep Org Owner to one or two people; use Org Admin for the platform team and Org Manager for agent builders.
Remember that Org Owners, Admins, and Managers reach every agent. Agent roles cannot hide an agent from them.
Review agent Security tabs when someone changes team, and deactivate rather than delete so history stays intact.
Restrict Document Access on agents whose training material is sensitive — Editors keep working, but the source documents stay closed.
Rotate agent API keys and webhook secrets whenever someone with Agent Admin access leaves.

→