Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Features
  • Basic Operations
    • Features
      • Teams → Projects → Assistants Hierarchy
    • Guides
      • Login/Signup
  • Assistants
    • Features
      • Introduction to Assistants
      • 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
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • View Dataset Id
  • Corpus
    • Features
      • Introduction
      • Corpus Permissions
      • PII Redaction
    • Guides
      • Assistant Corpus Setup
      • Assistant Corpus Settings
      • Corpus Access Control
      • Corpus Connections
      • ETag Setup for Corpus Incremental Refresh
      • View Corpus Id
      • View Document Id
      • Tagging
        • Corpus tagging
        • Document tagging
  • Teams
    • Features
      • Introduction
    • Guides
      • Add a Team
      • Edit a Team
      • Delete a Team
      • View Team Id
  • Projects
    • Features
      • Introduction
    • Guides
      • Add a Project
      • Edit a Project
      • Delete a Project
      • View Project Id
  • User Settings
    • Features
      • Introduction
      • Ejento AI User Access Levels
    • Guides
      • Assistant Edit Access
      • Add new user
      • Add User in a Team
      • Remove User from a Team
      • View my Access level in a Team
      • View my User Id
  • API Keys
    • Features
      • Introduction
    • Guides
      • How to generate API Key and Auth Token
  • Workflows
    • Features
      • Introduction
    • Guides
      • Add Workflow
      • Workflow Chat
  • Tools
    • Features
      • Introduction
    • Guides
      • Tools Overview
      • Create External Tool
      • Connect Tool to Assistant
  • Analytics
    • Features
      • Introduction
    • Guides
      • Analyzing Data in the Analytics Dashboard
  • Chatlogs
    • Features
      • Introduction
    • Guides
      • Managing Chatlogs
      • View Chatlog & Chat thread Id
  • Integrations
    • Features
      • Introduction
    • Guides
      • Email Indexing
      • Microsoft Teams
      • Sharepoint Indexing
      • MS Teams Integration Setup
      • Creating a Connection in Credential Manager
  • Ejento AI Shield
    • Features
      • Introduction
      • Understanding Guardrails
    • Guides
      • How to enable Guardrails
  • Assistant Security
    • Features
      • Introduction
      • Assistant Red Teaming
    • Guides
      • Red Team an Assistant
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Features

Ejento AI User Access Levels

This guide details the granular permission structures for teams and assistants within Ejento AI, enabling you to control collaboration, visibility, and access at every level.

Team-Level Permissions#

Ejento AI Teams have two permission levels, each defining how users can access and manage assistants within the team.

Team Owner#

The Team Owner holds full administrative privileges across all assistants in the team.
They can:
Edit and delete any assistant within the team.
Access and manage corpora connected to those assistants.
Invite or remove team members.
Oversee overall team settings and performance.
This role is ideal for users responsible for managing multiple assistants and team operations.

Team Viewer#

The Team Viewer is the default access level for members added to a team.
They can:
View and chat with all assistants in the team.
Explore assistant outputs and interactions without making changes.
Team Viewers are best suited for users who need visibility and interaction but not editing or management rights.

Assistant-Level Permissions#

Ejento AI assistants have two permission levels, each providing different levels of control and access:

Assistant Owner#

The Owner (or Creator) has full administrative rights over the assistant.
They can:
Edit the assistant's configuration and settings.
Delete the assistant if no longer needed.
Chat with the assistant to test or interact with it.
Access and manage the Corpus (knowledge base) linked to the assistant.
This role is ideal for users who created the assistant or need complete management control.

Assistant Editor#

The Editor has collaborative permissions with certain limitations compared to the Owner.
They can:
Edit the assistant's settings and content.
Chat with the assistant for testing and usage.
Access the knowledge base associated with the assistant.
Editors are best suited for team members who help maintain or update the assistant but do not require full administrative control.

Assistant Accessibility Levels#

The Assistant Accessibility Level determines who can view, edit, and interact with an assistant in Ejento AI.

Only Me#

Assistants set to Only Me are visible exclusively to the assistant's Owner (and the Global Admin).
This option is ideal for private development, testing, or experimental assistants that you don't want to share with others.

Only Team#

Assistants with Only Team accessibility are visible to all members within the same team.
This level ensures smooth collaboration while keeping the assistant restricted to internal team use.

Public#

A Public Assistant is accessible to everyone — both inside and outside the organization.
It can be shared in multiple ways:
View Only: Users can chat with the assistant through a shared link but cannot make any edits.
Edit Access: Users with this link can chat, edit, and access the assistant's knowledge base.
Public assistants can also be:
Embedded into external websites by copying and pasting the provided script into your site's HTML.
→ Learn how to embed an assistant here: Embed Assistant Guide
Shared through an interactive chat widget, offering a seamless conversational experience for end users.
Choose the accessibility level carefully to balance collaboration, security, and visibility across your organization.
Previous
Introduction
Next
Assistant Edit Access