Sub-tab: Users
Everyone in your organization who currently has access to this agent, and the agent-level role each one holds. Add a user, change a role, or revoke access from here.
| Setting | Description | When to use |
|---|---|---|
| Agent Owner | Full control: change every setting, train the agent, enable skills, upload and read documents, grant or revoke access for others, and delete the agent. | One per agent — the person accountable for it. Ownership can be transferred but not shared. |
| Agent Admin | Everything the Owner can do except delete the agent or transfer ownership. Can train, configure skills, upload documents, and manage user access. | Day-to-day operators who maintain the agent alongside the owner. |
| Editor | Can configure skills and content and use the agent, but cannot delete or reassign it, and cannot reach its training documents when Document Access is restricted. | Contributors who tune behavior but should not see the underlying knowledge base. |
| Authenticated User | Must sign in (magic link, code, or your own authentication) before interacting. Can use the agent in its intended channel but sees no configuration. | Internal staff or customers who must be identified before a conversation starts. |
| Public User | Anonymous access limited to front-end surfaces such as a public Live Chat widget. No configuration, no history, no document access. | Public-facing website agents — pair with IP or geographic restrictions on the Live Chat skill. |
Sub-tab: Invited Users
Pending invitations that have been sent but not yet accepted. Each row shows the invited email, the role it will grant, and when the invite was sent. You can resend or revoke an invitation before it is accepted.
- Invite by email and assign the agent role at the same time — the role applies the moment the invite is accepted.
- An invited user who is not yet in your organization is also added at the organization level (usually as Org User) when they accept.
- Revoking a pending invite immediately invalidates the link.
Sub-tab: Data protection controls
Agent-level controls over training data and who may extend the agent's memory.
- Document Access — when restricted, only the agent owner (and admins) can view, download, or export the agent's training documents. Editors and users can still chat with the agent; they just cannot read the source material.
- Training feedback — only admins can promote a conversation thread into the agent's memory, so end users cannot inject content into the knowledge base.
- Webhook and API access — endpoints and keys can only be created or rotated by an Agent Admin or Owner. Rotate keys whenever someone with access leaves.
- Live Chat restrictions — IP allow-lists and country-level geographic restrictions are configured on the Live Chat skill and apply before a conversation is created.
Tips
- Organization roles (Org Owner, Org Admin, Org User) are managed under Organization Management → Users. Agent roles only govern this agent.
- Org Owner and Org Admin implicitly reach every agent in the organization — do not rely on agent roles alone to hide an agent from them.
- Copilot's "Always Admin Mode" lets agent admins see every thread on the agent; it is a per-user setting inside Copilot, not here.
Related documentation
Role-based access control
The full org, agent, and moderator role model with a capability matrix.
Security overview
How raia protects data across the platform.
Auditor skill
PII detection, abuse monitoring, and alert recipients.
Live Chat skill
Security keys, IP allow-lists, and geographic restrictions.
Enterprise setup module
Hands-on walkthrough of RBAC, Auditor, and enterprise OAuth.