AdminAccess Control

Access Control

Give people Can use on an agent to let them run it without changing it. Give them Can edit when they need to change it.

Share a Resource

Resource sharing is an Enterprise feature.

  1. Open the item's Permissions control.
  2. Add a person, team, role, service account, OAuth client (on Knowledge Bases, knowledge connectors, and files), or Everyone in the organization.
  3. Choose their level, then save.
LevelAllows
Can readView the item.
Can useRun or invoke it.
Can editEdit its configuration.
Full accessDelete it and manage access.

You need Manage access on the item to share it. To share every current and future item of a kind, use Permissions beside Create or Add on its list; this requires accessPolicies:update.

Sharing with everyone or a role also requires that permission or Full access on every item of that kind. You cannot grant access you do not hold.

Sharing an agent does not share its MCP servers. Share the servers separately so the person can use their tools. MCP registry entries have an extra Full access + deploy level for changing deployments and secret sources; see server permissions. Agent Runtimes have a Can use and configure level instead of Can edit; see who can use each runtime.

Share Across Teams

Owners and anyone with Manage access on an item can share it with any team in the same organization, including teams they do not belong to. Under Who can use it, select Add access, choose a team and its access level, then save. No additional role permission is required.

Predefined Roles

Roles control organization actions, such as creating resources and managing users. Resource grants determine which individual items a person can use or change.

Member is the default. Choose a broader role only when the person needs it:

RoleChoose it for
MemberUsing Chat and creating agents, apps, skills, and gateways.
EditorAlso managing providers, models, budgets, environments, Knowledge, and Guardrails.
Platform AdminAdministering the platform without viewing everyone's logs or impersonating users.
AdminFull organization administration, including everyone's logs and user impersonation.

See the exact permission matrix. To change a member's roles, open Settings → Users, choose Change role on their row, and save with Update Roles.

Compose Access from Granular Roles

Give someone exactly what their job needs without writing a custom role: assign a few granular roles, such as Agent Writer and Log Reader, and their permissions add up. Granular roles are built in, grouped by area, and cannot be edited.

  1. Open the role picker where roles are assigned: Change role on a row in Settings → Users, Inherited Roles on a team, or Roles on a service account.
  2. Pick an area on the left, such as Agents or MCP, and check the roles you need on the right. The checkbox beside an area takes all of its roles. The chevron at the end of a role shows what it grants.
  3. Each choice applies as you make it. Close the picker and save.

What to know:

  • Each granular role grants a few permissions, such as agent:read. View built-in roles on Settings → Roles lists every built-in role and what it grants, and the permissions reference has the full table.
  • A granular role opens a page, not every item on it. Which agents or servers someone sees still depends on what is shared with them.
  • A new custom role can start from one of the four preset roles or from another custom role, not from a granular role.

Create a Custom Role

  1. With ac:create, open Settings → Roles and create a role.
  2. Select only the permissions the job needs.
  3. Assign it to a member, team, or service account.

An account gets the permissions of every role assigned to it directly, plus the roles it inherits from its teams and their parent teams. Set the roles a team passes down under Inherited Roles when you edit the team.

Team Member and Admin Roles

Within each team, a person is a member or an admin. Members receive the team's grants but cannot manage its limits just by being members. Admins manage only that team's members and settings.

Team admins can manage child-team allocations and member key caps across their team hierarchy, and see those teams' costs. Their own team's ceiling stays protected unless they also administer a parent team.

Remove Access

Open the item's permissions and remove the recipient. Check inherited grants too: removing a direct grant leaves access through teams, roles, or the organization intact. Team grants reach descendant teams, but not parents or siblings.

Keep at least one recipient with Manage access. If a role or team change would delegate access you cannot grant, the form identifies the affected resources and missing permissions.

Transfer Ownership

Choose Make owner on another person's row in the permissions editor. You need edit and full access on the item.

The new owner receives Full access. The previous owner keeps their grant until you remove it separately. An owner's grant cannot be removed while they still own the resource.

For request and audit-log access, see Logs and Auditing. For automated permission changes, use the Permissions API.