Ejento AI
GuidesQuickstartRecipesREST APIsRelease NotesFAQs
GuidesQuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Features
  • Getting Started
  • 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 Modes
    • Guides
      • Add Assistant
      • Evaluate Assistant
      • Edit Assistant
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • View Dataset Id
  • Workflows
    • Features
      • Overview and Types of Supervisors
    • Guides
      • Add Workflow
      • Workflow Chat
  • 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
  • Tools
    • Features
      • Introduction
    • Guides
      • Tools Overview
      • Create External Tool
      • Connect Tool to Assistant
  • Analytics
    • Guides
      • Analytics
  • User Settings
    • Features
      • 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
  • Chatlogs
    • Guides
      • Chatlogs
      • View Chatlog & Chat thread Id
  • API Keys
    • Guides
      • API Keys
  • Integrations
    • Email Indexing
    • Microsoft Teams
    • Sharepoint Indexing
    • MS Teams Integration Setup
  • 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
  • Ejento AI Shield
    • Introduction
  1. Features

Ejento AI User Access Levels

1. User Types#

Ejento AI supports three types of users: Global Admin, Application Admin, and User. Each with a set of responsibilities and levels of control in the system in aspects like User Management, Team Management, Admin Panel Access, Content Viewing, Privileges and Testing.

Global Admin#

Global Admin has the highest level of access and control in the system.
User Management: Can assign roles to others, including making them Application Admins, Global Admins, or Users.
Team Management: Can create teams and has access to all teams, projects, and assistants (acts as the Team Owner for all teams).
Admin Panel Access: Full access to the admin panel, including Analytics, User settings, Chatlogs, API Keys.
Content Viewing: Can view the Supporting Content and Thought Process for each chat response.
Privileges: Possesses all privileges of an Application Admin and a User.
Testing: Can perform evaluation regression testing on assistants.

Application Admin#

An Application Admin manages applications and teams with elevated privileges.
User Management: Can assign roles to others, making them Application Admins or Users.
Team Management: Can create teams and manage users within teams (acts as the Team Owner for their created teams).
Admin Panel Access: Access to the admin panel, limited to analytics, user settings, and aliases.
Privileges: Possesses all privileges of a User.

User#

A User can explore and utilize various functionalities and features within the system.
Project Creation: Can create projects.
Assistant Management: Can create assistants, index data, and engage in chat.
Default Role: Assigned by default in case of SSO login.

2. 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.

3. 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.

4. 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.

5. Permissions Based on User Role#

RolePermissionsDescription
Global AdminFull access to all teams, assistants, and the admin panel. Can perform evaluation testing.Holds the highest level of control — can assign roles, manage teams and users, access all data, and view analytics.
Application AdminCan create and manage teams, assign roles (Application Admin or User), and manage app settings.Has elevated privileges with limited admin panel access (analytics, user settings, aliases). Cannot perform advanced testing or access all content.
UserCan create projects, assistants, and index data.Default role for standard users — can use platform features but has no admin or management access.
Previous
Analytics
Next
Assistant Edit Access