Roles and permissions
What owners, editors, viewers and maintainers can do, and which decisions always stay with a person.
Roles on a collection
| Action | Viewer | Editor | Owner |
|---|---|---|---|
| Read terms, history and changes | Yes | Yes | Yes |
| Search, export, star and watch | Yes | Yes | Yes |
| Add and edit terms, import, merge proposals | No | Yes | Yes |
| Commit agent pushes and answer their items | No | Yes | Yes |
| Rename, archive, set agent policy and webhooks | No | No | Yes |
| Invite and remove collaborators | No | No | Yes |
| Publish releases, enable automatic contributions | No | No | Yes |
Organization roles use the same three names. An organization owner is an owner of all its collections, and only owners manage the organization's members, handle and settings.
Maintainers
Maintainers review what enters the public bank and handle reports, takedowns and merges of duplicate public concepts. It is an account role, checked on every request, and only works in a maintainer's own browser session.
What always stays with a person
- Granting power to an agent: connecting it, choosing its collection range and restrictions, and revoking it.
- Authorizing agent access to your account. Collection owners can delegate collection publication and license management.
- Managing members and invitations.
- Answering merge suggestions and pushes that exceed a limit.
- Changes beyond a token restriction or collection review policy require a person.
Sensitive actions such as issuing tokens, approving agent access and disabling an account ask you to confirm your password if you have not done so in the last 10 minutes.
How permissions combine
Requests follow your current collection role, the authorized collection range and optional credential restrictions. Revocation and role changes apply on subsequent requests; the database also enforces collection isolation.