Organization roles
User
Creates personal agents, prompts and skills. Can share them with other users or groups if the organization allows it. Uses agents and skills shared with them.
Admin
Everything a user can do, plus organization-wide administration: Groups, Tool policies, per-feature permissions, and the RBAC audit log.
Only the organization owner can access User Management. Other admins manage groups, tool policies and permissions, but not the user list itself.
Sharing agents, prompts and skills
Any user can share what they create — an agent, a prompt or a skill — directly from its settings, without needing an admin.1
Open the item's sharing settings
From the agent, prompt or skill you own, open Share.
2
Choose who to share with
Share with specific users, with a group, or with everyone in your organization (if your administrator allows organization-wide sharing).
3
Set the permission level
Assign Viewer, Editor or Owner to each person or group you share with.
Permission levels
Viewer
Viewer
Can use the agent, prompt or skill in conversations. Cannot change its configuration or share it further.
Editor
Editor
Can use it and modify its configuration — instructions, tools, knowledge. Changes apply for everyone it’s shared with. Cannot re-share it or delete it.
Owner
Owner
Full control: use, edit, share with others, transfer ownership, or delete. The creator is Owner by default.
What administrators manage
Administrators configure organization-wide access from Settings → Organization.Groups
Organize users into groups so you can share agents, prompts and skills, and grant connector access, to a whole team at once.
Tool policies
Allow or deny specific connectors (MCP servers) per user or group — for example, letting only a team use a CRM connector.
Per-feature permissions
Control, organization-wide, who can create or share agents, prompts, skills and memories — for example, restricting agent creation to a subset of users.
RBAC audit log
A record of every permission change: tool policies, groups, role changes and connector access, for accountability and review.
Single sign-on, two-factor authentication and organization settings are covered in SSO and 2FA and Organization settings.
Restricting what an agent’s tools can do
When you build an agent and add a connector (for example Outlook or a CRM), you can enable only the specific actions it needs and leave the rest off.- Example: drafting only
- Why this matters
Keep read emails and draft email, and leave send email and delete email off. The agent can prepare a draft for you to review, but cannot send or delete anything — the capability doesn’t exist for it.
Good practices
Limit admins
Keep the number of administrators small. Most people only need to create and share their own agents.
Share narrowly first
Share with the specific users or group who need it before sharing with the whole organization.
Review the audit log
Periodically check the RBAC audit log for unexpected permission or tool-policy changes.
Match tools to purpose
Enable only the connector actions an agent needs for its task, nothing more.