Teams and permissions
Let teammates inspect the same work without giving everyone permission to change it.
Choose a role for the team
| Role | What they can do |
|---|---|
| Owner | Manage members, invitations, keys and Space administration; edit and run agents |
| Editor | Create and edit agents and their data; run checks; read full operations and usage |
| Viewer | Read full operation inputs/results, context, Knowledge and usage; make no changes |
Roles apply across the team’s Spaces. Viewer is read-only, not a redacted view: grant it only to people allowed to read the underlying data.
Keep SDK access under Owner control
Owners issue and revoke SDK keys and manage invitations and role changes. The API retains legacy role values owner, admin and member; the dashboard displays Owner, Editor and Viewer.
Changing an Editor to Viewer revokes their issued keys. Previously issued Editor keys are not silently broken by the role-label update; review and revoke them deliberately where needed.