Roles and permissions
The roles available in a Vulgate Organization, plus when to assign each.
May 21, 2026
Vulgate Organizations have five roles: Owner, Super Admin, Developer, Content Admin, and Member. Roles are scoped per Organization — you can have a different role in each Organization you belong to.
Permissions matrix
| Action | Member | Content Admin | Developer | Super Admin | Owner |
|---|---|---|---|---|---|
| Read documents in shared Library | ✓ | ✓ | ✓ | ✓ | ✓ |
| Use Chat and Search | ✓ | ✓ | ✓ | ✓ | ✓ |
| Use the in-document AI Assistant | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create personal Bookmarks and Collections (private or shared) | ✓ | ✓ | ✓ | ✓ | ✓ |
| Translate documents | ✓ | ✓ | ✓ | ✓ | ✓ |
| Upload documents | ✓ | ✓ | ✓ | ✓ | ✓ |
| Manage documents (edit, delete, publish) | — | ✓ | ✓ | ✓ | ✓ |
| Manage Organization Collections | — | ✓ | ✓ | ✓ | ✓ |
| Mark documents as Organization-wide | — | ✓ | ✓ | ✓ | ✓ |
| Create and revoke own API keys | — | — | ✓ | ✓ | ✓ |
| See and revoke any member's API keys | — | — | — | ✓ | ✓ |
| Invite members, change member roles, remove members | — | — | — | ✓ | ✓ |
| Access other admin-only features (custom fields, billing) | — | — | — | ✓ | ✓ |
The Owner has all permissions. Changing the Owner is handled directly by Vulgate support; please contact us if you need to transfer Ownership.
When to assign each role
Member
For most teammates whose primary job is to read, search, chat, and upload documents. Members can shape their experience with Bookmarks and private or shared Collections without risk to the Organization-wide corpus, and can add their own uploads.
Content Admin
For teammates who curate the Library — librarians, content managers, project leads. In addition to everything a Member can do, they can edit, delete, and publish documents, and they manage Organization-wide Collections.
Developer
For teammates building on the Vulgate API. A Developer can do everything a Content Admin can, and can also create and revoke their own API keys — without gaining access to other members' keys, member management, custom fields, or billing.
Super Admin
For Organization administrators who need full configuration access — managing members, custom fields, API keys, and billing.
Owner
The Owner is the person ultimately responsible for the Organization. The Owner has every permission a Super Admin has.
Changing a role
- Open Settings → Org settings → Members.
- Click the member row.
- Pick a new role from the role picker (Super Admin, Developer, Content Admin, or Member).
Owner cannot be assigned through this dialog; contact us if you need to transfer Ownership.
Frequently asked
Can a Member see another Member's chats? No. Chats are private to the user who created them.
Can a Member delete a Bookmark another Member made? No. Bookmarks are personal.
Related
Search help