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

Assistant Edit Access

Give specific users and teams access to an assistant, and choose whether they can only use it or also manage it. Direct access is the way to share one assistant with people who aren't in its project, or to give someone more rights than the project gives them.
Open the Assistants section. If you're not sure how, see Add Assistant.

How assistant access works#

People can get access to an assistant in two ways:
Direct access: You add a user or a team to the assistant itself. This guide covers direct access.
Inherited access: Users and teams that have access to the assistant's project get the same role on every assistant in it. You can see them on the Inherited Access tab, but you change them in the project.
Each user or team gets one of two roles. A role decides which assistant a person can act on; what they can actually do still comes from their Permission Sets.
RoleWhat it allows
MemberView and use the assistant, if a Permission Set grants view. Members can't edit, delete, or deploy it.
AdminView, edit, delete, or deploy the assistant, for each action a Permission Set grants.
Whether the assistant is Private or Public is set separately, under Advanced > Visibility. To learn how visibility and roles work together, see Assistant Access Control.

Use cases#

Share a private assistant with a pilot group: Add five testers as Member so they can try a new assistant before you make it public.
Hand over maintenance: Add a colleague as Admin so they can update the instructions and deploy changes while you're away.
Give a whole department access: Add the department's team instead of each person. As people join or leave the team, their access follows automatically.

1. Open Edit Access#

Search for your assistant, click the three dots in its Actions column, then click Edit Access. The Access Control window opens and shows the assistant's status and visibility, with three tabs: Direct Access, Inherited Access, and Associated Workflows (workflows that use this assistant).
Step 1 screenshot

2. Add a user or team#

On the Direct Access tab, click Add User. In Select Users, search for and check one or more users (or Select All), choose a Role, and click Add. To give a whole team access, click Add Team instead and choose teams the same way.
The message Permission added (will be saved when you update) appears, and the new entries are marked New in the table. Nothing is saved yet.
Step 2 screenshot

3. Save the permissions#

Check the entries in the table and change a Role if needed, then click Update Permissions. The window closes and the access is saved. When you open Edit Access again, the new users and teams are listed with their roles.
The person who created the assistant is listed with the role Owner, which you can't change. To remove someone's direct access, click the trash icon in their row, then click Update Permissions.
Step 3 screenshot
Previous
Edit Assistant
Next
Embed Assistant