What can each organization member access?
A person in an organization is an admin here, an admin for the whole account, or a member with limited access made of presets. Presets cover an area across the organization; they do not limit someone to one task, agent, or skill. Every console page in this documentation says which access it needs.
| Preset | Lets the person | Pages |
|---|---|---|
| Task observer | Read task standards, comparisons, and live results | The standard, Compare and release |
| Skill contributor | Read skills, import packages, and save drafts | Shared skills |
| Skill manager | Create, publish, and retire skills | Shared skills |
| Agent observer | Inspect agent runs, steps, and permission decisions | Agent rules and limits |
| Agent operator | Set up agents, inspect runs, and save steps for review | Connect, Agent rules and limits |
| Agent permissions manager | Inspect runs and change tool rules and limits | Agent rules and limits |
| Agent approver | Review held actions and approve or reject them | Approvals |
| Reviewer | Review labels, saved steps, and proposed corrections | Live answers and corrections |
| Evidence auditor | Read recorded history and metadata without changing work | Evidence |
Admins can do all of this and also manage people, keys, provider credentials, models, and notifications under Settings. Access can carry an expiry date, and every change to it is recorded.
Runtime keys are for applications and agents, not people: they carry scopes, and some actions are never available to a key. See Sign up and create a key.