Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Guides
  • Basic Operations
    • Features
      • Organization → Projects → Assistants → Teams Hierarchy
    • Guides
      • Login/Signup
  • Assistants
    • Overview
    • Features
      • Assistant Access Control
      • Assistant Evaluation
      • Evaluation Metrics
      • URL-based Chat Thread Creation and Prepopulation
      • Reasoning Patterns
      • Staging & Publishing
    • Guides
      • Add Assistant
      • Evaluate Assistant
      • Edit Assistant
      • Assistant Edit Access
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • Voice Calling with Assistants
  • Corpus
    • Overview
    • Features
      • Corpus Permissions
      • PII Redaction
      • ETag Setup for Corpus Incremental Refresh
    • Guides
      • Assistant Corpus Setup
      • Assistant Corpus Settings
      • Corpus Access Control
      • Corpus Connections
      • View Corpus Id
      • View Document Id
      • Tagging
        • Corpus tagging
        • Document tagging
  • Teams
    • Overview
    • Guides
      • Add a Team
      • Edit a Team
      • Delete a Team
      • View Team Id
  • Projects
    • Overview
    • Guides
      • Add a Project
      • Edit a Project
      • Managing Assistants in a Project
      • Delete a Project
      • View Project Id
  • User Settings
    • Overview
    • Features
      • Ejento AI User Access Levels
    • Guides
      • Add new user
      • Invite Users via Link or Email
      • View my User Id
  • API Keys
    • Overview
    • Guides
      • How to generate API Key and Auth Token
  • Workflows
    • Overview
    • Features
      • Workflow Access Control
    • Guides
      • Add Workflow
      • Workflow Chat
      • Workflow Edit Access
  • Tools
    • Overview
    • Guides
      • Tools Overview
      • Create External Tool
      • Connect Tool to Assistant
  • Analytics
    • Overview
    • Guides
      • Analyzing Data in the Analytics Dashboard
  • Chatlogs
    • Overview
    • Guides
      • Managing Chatlogs
      • View Chatlog & Chat thread Id
  • Integrations
    • Overview
    • Guides
      • Email Indexing
      • Microsoft Teams
      • Sharepoint Indexing
      • Google Drive Connector
      • MS Teams Integration Setup
      • Creating a Connection in Credential Manager
      • Slack App
      • Discord Bot
  • Ejento AI Shield
    • Overview
    • Features
      • Understanding Guardrails
    • Guides
      • How to enable Guardrails
  • Assistant Security
    • Overview
    • Features
      • Assistant Red Teaming
    • Guides
      • Red Team an Assistant
  • Permission Sets
    • Overview
    • Guides
      • Add Permission Set
  • Usage
    • Overview
    • Guides
      • Set Spend Limits
  1. Guides

Corpus Access Control

A corpus often holds knowledge that only some people should see or change, such as HR policies, financial reports, or customer contracts. Corpus access control lets you decide exactly who can use each corpus and what they can do with it, so you can share knowledge widely without losing control of it.

Why manage corpus access?#

Protect sensitive content. Keep confidential documents visible only to the people who need them.
Collaborate safely. Let teammates help maintain a corpus (uploading documents, updating settings) without giving everyone that power.
Scale with teams. Share a corpus with a whole team in one step. When people join or leave the team, their corpus access follows automatically.
Stay accountable. The owner of a corpus always keeps access, so every corpus has someone responsible for it.

Roles at a glance#

RoleWhat it allows
MemberViewing the corpus
AdminViewing, changing, and deleting the corpus, including managing who has access
OwnerThe person who created the corpus. Has full access, and can't be removed or changed
A role says which corpus someone can work with. What they can actually do also depends on the Permission Sets they hold. For the full details, see Corpus Permissions.

Use cases#

Read-only users: Add a support agent as Member when their assistant needs the help articles, or they need to browse them, but they shouldn't change anything.
Co-maintainers: Add a content manager as Admin so they can upload new policy documents each quarter.
Whole groups: Share an "HR Policies" corpus with the HR team as Admin and with all managers as Member, so access follows people as they join or leave those teams.

Open the Corpus section. If you're not sure how, see Assistant Corpus Setup.

1. Open the corpus access settings#

On the Corpora page, find your corpus and click the edit (pencil) icon in its Actions column. The Corpus Settings window opens, listing everyone who has access under Permissions.
You can also rename the corpus here, in the Corpus Name field.
Step 1 screenshot

2. Add a user and choose their role#

Click Add User, choose one or more people under Select Users, and pick a Role: Admin or Member. Then click Add. You can search the list or use Select All.
Step 2 screenshot

3. Add a team#

To give a whole team access, click Add Team, choose the teams under Select Teams, pick a Role, and click Add.
Sharing with a team doesn't give its members access automatically. Each member also needs a Permission Set that allows the action on corpora shared with their teams. A team Member role is limited to viewing, even if a Permission Set would allow more.
Step 3 screenshot

4. Review and save the changes#

New entries are marked New in the list. To change someone's access, use the Role dropdown in their row; to remove them, click the delete icon in Actions. When everything looks right, click Update Corpus. The message Permissions saved appears.
The Owner can't be removed and their role can't be changed.
Step 4 screenshot

FAQs#

Who can change a corpus's access?#

Only its Admins and Owner. Members can't change who has access.

What happened to the Viewer and Editor roles?#

Viewer was renamed Member. Editor was merged into Admin, which can also delete the corpus and manage access if the person's Permission Sets allow it.

Is a public corpus visible to everyone?#

A public corpus is shared with everyone in the organization at Member (view-only) level. Each person still needs a Permission Set that lets them view corpora.
Previous
Assistant Corpus Settings
Next
Corpus Connections