Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Features
  • Basic Operations
    • Features
      • Organization → Projects → Assistants → Teams Hierarchy
    • Guides
      • Login/Signup
  • Assistants
    • Overview
    • Features
      • Assistant Access Control
      • Caching Responses for Assistants
      • Assistant Evaluation
      • Evaluation Metrics
      • URL-based Chat Thread Creation and Prepopulation
      • Reasoning Patterns
    • Guides
      • Add Assistant
      • Evaluate Assistant
      • Edit Assistant
      • Assistant Edit Access
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • View Dataset 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
      • View my User Id
  • API Keys
    • Overview
    • Guides
      • How to generate API Key and Auth Token
  • Workflows
    • Overview
    • Guides
      • Add Workflow
      • Workflow Chat
  • 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
      • 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
  1. Features

Assistant Access Control

Understanding assistant accessibility levels and collaborative permissions in Ejento AI is essential for managing who can view and modify your work. These settings provide the flexibility to keep projects secure while enabling seamless teamwork across your organization.

Assistant Accessibility Levels#

Assistants in Ejento AI have two primary accessibility levels that determine their visibility:

1. Private#

AttributeDetails
VisibilityRestricted to specific authorized users.
Access PathOnly visible to the assistant's creator, Global Admins, and anyone who has been granted access through a parent Project or an assigned Team.
PurposeThe default setting for most assistants. It ensures complete privacy while developing or working on sensitive organizational tasks.
NOTE
Private is the default accessibility level for all newly created assistants.

2. Public#

AttributeDetails
VisibilityAccessible to everyone, including those outside your organization, via a direct link or external embed.
PurposeIdeal for widely shared tools, customer-facing support widgets, or public knowledge bases.
View OnlyUsers can chat with the assistant but cannot see its internal configurations.
Edit AccessAllows others with the link to help configure and refine the assistant.
CAUTION
Public assistants are accessible to everyone. Ensure no sensitive or confidential information is embedded in a Public assistant's configuration.

Permission Propagation & Collaboration#

Access to an assistant is often inherited from higher levels in the hierarchy. This makes managing large groups of users simple and efficient.

Inherited Access#

Inheritance TypeDetails
Project InheritanceIf a user is added as a Member or Admin of a Project, they automatically receive that same level of access to every Assistant within that project.
Team AssignmentGranting a Team access to a Project or Assistant immediately shares that access with every individual in that team.

Collaborative Edit Access#

The Assistant Edit Access capability allows those with Admin rights — either assigned directly or inherited — to modify the assistant's settings. This facilitates:
BenefitDetails
Shared ResponsibilityMultiple team members can co-manage an assistant's knowledge base and tools.
SecurityOnly authorized users with Admin status can perform destructive actions like deletion or sensitive configuration changes.
FlexibilityOwnership and management rights can be adjusted as project needs evolve.

TIP
Whether you are building a private tool for personal productivity or a public assistant for global reach, Ejento AI's access control ensures your work remains secure and accessible to the right people. By leveraging Projects and Teams, you can maintain control over your assistants with minimal administrative effort.
Previous
Overview
Next
Caching Responses for Assistants