C3 AI Documentation Home

Roles and Permissions

Access to C3 AI Agentix is governed by three core roles that form an administration ladder. Most people need just one, Agentix.User, to chat with agents, run their own automations, manage their own skills and connections, and view their own usage. Two administrator roles layer on top of it: Agentix.AgentAdmin for the people who curate agents and watch the fleet, and Agentix.AppAdmin for the people who operate the environment itself. Optional capability entitlements, such as Agentix.LlmApiUser, layer on Agentix.User without becoming administrator rungs.

This page lists the C3 AI Agentix roles, spells out exactly what each one permits, explains how they nest, and shows how they shape what each user sees.

The C3 AI Agentix roles

The three core roles in this table form a strict ladder—each one includes everything the role above it can do. Agentix.LlmApiUser is a separate bulk entitlement for personal LLM API access; it nests Agentix.User but doesn't grant Agentix.AgentAdmin capabilities:

RoleWhat it's for
Agentix.UserThe base role for everyone who uses the app: chat with agents, run and manage your own automations, manage your own skills and chat sessions, manage your own connections (personal secrets and MCP servers), use applications an admin has connected, and view your own Usage.
Agentix.AgentAdminThe agent administrator. Nests Agentix.User and adds the agent-administration surface: create, edit, and delete agents; create, promote, edit, and delete cluster-wide (Global) skills; view the Monitor dashboard and its Observability traces; provision, rotate, test, and clear the service-account tokens for other clusters; and manage the shared external MCP connection registry, including Global connections.
Agentix.AppAdminThe C3 AI Agentix environment administrator. Nests Agentix.AgentAdmin (and therefore Agentix.User) and adds the Admin page with its fleet-level controls: warm-pool sizing, forcing a Sync, acting on any user's session, the model catalog, embedded chat setup, and application upgrades. It also manages Global secrets, which reach every user's sessions. It grants these without requiring a platform admin role.
Platform administratorA C3 AI Platform-level administrator (C3.AppAdmin, C3.EnvAdmin, or C3.ClusterAdmin). Satisfies the same admin gate as Agentix.AppAdmin, so it can do everything in C3 AI Agentix plus the platform operations that sit outside the app.

Agentix.AppAdmin is a C3 AI Agentix-scoped role, not a platform role. It exists so warm-pool tuning and session administration can be delegated at the C3 AI Agentix level without handing out platform C3.AppAdmin. Internally, both Agentix.AppAdmin and the platform admin roles satisfy the same check (isAtLeastAppAdmin), which is why they share the top row of every table on this page.

What each role can do

The roles nest, so each column below includes everything to its left. A platform administrator can do everything Agentix.AppAdmin can, plus platform-level operations.

CapabilityAgentix.UserAgentix.AgentAdminAgentix.AppAdmin
Chat with agents; connect apps to a chat; manage your own workspace and sessions✓✓✓
Browse the Agents gallery and agent detail✓✓✓
Browse the Skills catalog; upload Personal skills; attach skills to your own chats✓✓✓
Create and manage your own automations (asynchronous agent jobs)✓✓✓
Manage your own connections: personal secrets and your own MCP servers✓✓✓
Use a cross-cluster app an admin has already connected✓✓✓
View your own Usage (your tokens and spend)✓✓✓
View API access and manage your own Nexus LLM keys when access is enabled✓✓✓
Create, edit, and delete agents—✓✓
View the Monitor dashboard and Observability (Laminar) traces—✓✓
Provision, rotate, test, or clear cross-cluster service-account tokens—✓✓
Manage the shared external MCP connection registry—✓✓
Upload or promote a skill to Global (cluster-wide); edit or delete a Global skill—✓✓
Add, rotate, or remove a Global secret——✓
Open the Admin page: agent services, the model catalog, backend services, upgrades, embedded chat, and vanity URLs——✓
Manage agent services fleet-wide: stop, resume, or terminate any user's session——✓
Configure the warm pool and force a Sync on the Admin dashboard——✓
Enable, revoke, suspend, or restore another user's Nexus LLM API access——✓

Two boundaries deserve emphasis because users can infer them incorrectly:

  • The Admin page requires Agentix.AppAdmin. The Admin page holds agent services, the warm pool, Sync, session actions, the model catalog, and upgrades. It requires Agentix.AppAdmin or a platform admin, and Agentix.AgentAdmin alone doesn't open it.
  • Global skills and MCP connections need Agentix.AgentAdmin. That role can upload, promote, edit, or delete a Global skill and register a Global MCP connection. Global secrets are the exception and require Agentix.AppAdmin. A plain Agentix.User works at Personal scope only.

Self-service is built in for everyone. A Agentix.User already manages their own chats, sessions, automations, and connections directly—starting and deleting chats, scheduling automations, storing personal secrets, and connecting their own MCP servers. The admin controls are for managing the whole fleet (everyone's instances) or cluster-wide resources, which is why they require an administrator.

Role-gated navigation

What a user sees in the left navigation follows directly from their role:

Nav itemVisible to
Chat, Agents, Skills, Automations, Usage, ConnectEveryone (Agentix.User and up)
MonitorAgentix.AgentAdmin, Agentix.AppAdmin, platform admins
AdminAgentix.AppAdmin, platform admins

C3 AI Agentix enforces the same rule on a direct URL. A user without either role who opens the Admin page by URL sees a 403 page. The page shows the message "Admin access required to view this page."

Assigning roles

Most roles are granted through the C3 AI Platform's access control. An administrator assigns one or more Agentix.* roles (typically Agentix.User for everyone, plus an admin role for the few who need it) to a user or a group, using your environment's standard role-management tooling.

A practical baseline:

  • Grant Agentix.User to all product users—it's the role that lets people use the product.
  • Grant Agentix.AgentAdmin to the people who curate shared agents and Global skills. The role also covers the MCP connection registry, Monitor, and cross-cluster connections.
  • Grant Agentix.AppAdmin sparingly. It opens the Admin page, where people run the service fleet, tune the warm pool, manage the model catalog, and upgrade the application. It also manages Global secrets.
  • Reserve platform-administrator rights for the small group that operates the cluster itself.

Best practices for limiting access

  • Default to least privilege. Almost everyone needs only Agentix.User. Add Agentix.AgentAdmin for a specific need rather than jumping straight to Agentix.AppAdmin.
  • Prefer Agentix.AgentAdmin over Agentix.AppAdmin. Agent curation, Global skills and MCP connections, the Monitor dashboard, and cross-cluster tokens all live at the agent-admin tier. Reserve Agentix.AppAdmin for the Admin page, its fleet-level controls, and Global secrets.
  • Remember that Global resources and shared agents are cluster-wide. A Global skill, MCP connection, or secret affects everyone. So does an edit to a shared agent. Keep administrator grants to a trusted few. See Share a Skill Across Your Team.
  • Mind the service-account model for cross-cluster apps. Every cross-cluster call runs as the provisioned service account regardless of who triggered it, so scope those tokens to the minimum roles the agent needs. See Connect Apps from Other Clusters.

See also

Was this page helpful?