Corpus permissions in Ejento AI define the actions users can perform on a corpus, including viewing, editing, and managing its content and settings. Access can be granted to individual users or entire teams, each assigned one of four roles.
Roles Overview#
| Role | Description |
|---|
| Viewer | View the corpus, documents, sitemaps, conversation starters, and connected agents. No changes allowed. |
| Editor | Everything a Viewer can do, plus: edit corpus metadata, upload/delete documents, manage sitemaps, trigger re-indexing, and annotate. |
| Admin | Everything an Editor can do, plus: delete the corpus and manage the permissions panel (grant, update, and revoke access for users or teams). |
| Owner | The corpus creator. Identical to Admin but cannot be removed or changed via the permissions panel. |
Permission management is exclusively an Admin/Owner action. The Editor role does not grant access to the permissions panel.
Key Behaviors#
Creator is Always the Owner#
The user who creates a corpus is automatically assigned the Owner role. This assignment cannot be changed or revoked through the UI.
Team Permissions#
Granting a role to a team applies it to all current members of that team. Adding or removing users from the team automatically updates their corpus access — no manual re-granting required.
Organization Global Admins#
Organization Global Admins automatically have manage-level access on all corpora within the organization. No explicit grant is needed.
