Skip to content

Permissions

Every member of a workspace has one role: Owner, Admin, Builder, Manager or Viewer. This page lists what each role can do. For how roles work and how to invite members, see Workspaces and roles.

Roles are cumulative: each role can do everything the role below it can do.

Role Who it’s for
Owner The person accountable for the workspace: plan, payment method and ownership. There is exactly one Owner.
Admin People who run the workspace: members, security, connectors, policies, money and L4 Delegate.
Builder People who design employees, skills, teams and knowledge bases, connect MCP servers and publish to the marketplace.
Manager People who manage employees day to day: assign tasks, answer approvals, change levels up to L3, run reviews.
Viewer People who need to see the work, such as auditors or stakeholders.

In the table below:

  • Yes: the role can do it for the whole workspace.
  • Own: only for employees the member is the human manager of, and employees in teams they own.
  • No: the role can’t do it.
Permission Owner Admin Builder Manager Viewer
Workspace
Manage the plan and payment method Yes No No No No
Transfer ownership, delete the workspace Yes No No No No
View invoices and buy credits Yes Yes No No No
Invite and remove members, change roles Yes Yes No No No
Configure SSO, SCIM and data retention Yes Yes No No No
Employees and teams
View employees, teams and the org chart Yes Yes Yes Yes Yes
Chat with employees that allow it Yes Yes Yes Yes Yes
Create employees and hire from the marketplace Yes Yes Yes No No
Edit employees, skills, teams and knowledge bases Yes Yes Yes No No
Assign tasks and take over runs Yes Yes Own Own No
Pause, retire or restore an employee Yes Yes Yes Own No
Autonomy and approvals
Change autonomy level, up to L3 Autonomous Yes Yes Own Own No
Grant L4 Delegate Yes Yes No No No
Set L2 thresholds Yes Yes Own Own No
See approvals Yes Yes Yes Yes Yes
Answer approvals Yes Yes Own Own No
Run performance reviews Yes Yes Own Own No
Integrations
Add connectors in Workspace mode Yes Yes No No No
Connect your own account to a Per member connector Yes Yes Yes Yes No
Add MCP servers and review tool impact classes Yes Yes Yes No No
Grant tools and skills to employees Yes Yes Yes No No
Turn on inbound MCP and A2A for the workspace Yes Yes No No No
Enable an employee’s MCP endpoint and create access tokens Yes Yes Yes No No
Money
Fund the treasury Yes Yes No No No
Create employee wallets and fund them Yes Yes No No No
Edit budgets, spend limits and merchant allowlists Yes Yes No No No
Freeze a wallet Yes Yes Own Own No
Governance
Create workspace policies and guardrails Yes Yes No No No
Create team and employee policies Yes Yes Own Own No
View the full audit log Yes Yes No No No
Export the audit log Yes Yes No No No
Observability
View activity, run traces, costs and reports Yes Yes Yes Yes Yes
Run evaluations Yes Yes Yes No No
Marketplace
Become a publisher and set the payout method Yes Yes No No No
Prepare, price and submit listings for certification Yes Yes Yes No No
Publish and deprecate listing versions Yes Yes Yes No No
  • The human manager is not a role. Any member with the Manager role or above can be an employee’s human manager. The Own permissions follow that assignment, and the team owner’s.
  • Builders don’t move money. A Builder can design an employee that pays with x402, but only an Admin can fund its wallet or change its limits.
  • Only the Owner manages the plan. Admins see invoices and buy credits, but can’t change the plan or the payment method. Only the current Owner can transfer ownership, from Settings > Members.
  • Policies can narrow who approves. A policy can require that a specific group, such as Finance, answers some approvals. In that case, only members of that group can answer, whatever their role.
  • An employee never approves its own work. Approvals are always answered by a human. Another employee can’t answer them, even at L4 Delegate.
  • Every change is audited. Role changes, level changes and approvals are recorded in the audit log.