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

Organization → Projects → Assistants → Teams Hierarchy

At the core of Ejento AI lies a fundamental hierarchy that defines how work is structured and organized: Organization → Projects → Assistants. This structure is crucial for managing collaboration and accessibility in the platform, ensuring your enterprise remains organized and secure.

Organization#

The Organization is the highest level of Ejento AI. It acts as the primary container for all users, teams, projects, and assets. Within an Organization, access is governed by three primary administrative roles:
RoleDescription
Global AdminHas full visibility and control over the entire organization, including all Projects, Teams, and Assistants. They can manage all users except other Global Admins.
Application AdminCan manage regular users and create any new resource (Projects, Teams, or Assistants), but cannot manage higher-level administrators.
UserThe base-level role. A User belongs to an organization but must be granted specific permissions to individual Projects or Assistants to interact with them.

Projects#

Projects are secondary containers within the Organization used to cluster related work and initiatives. A Project serves as the home for one or more Assistants and acts as the point where access is typically assigned.

Example: Projects in the Marketing Team#

The Marketing Team might leverage various projects:
SEO Campaign — Focused on improving website visibility.
Social Media Strategy — Dedicated to planning and executing social media outreach.
Email Marketing — Handling email newsletters and communication history.
Create a Project
To create a new project, follow this step-by-step guide: Add a Project

Assistants#

Assistants are the most granular level of the hierarchy. Located within Projects, Assistants are AI-driven tools configured to help with specific tasks. They are equipped with capabilities like language understanding, information retrieval, or specialized functions.

Example: Assistants in the Email Marketing Project#

Content Generator Assistant — Helps draft engaging email content.
Analytics Assistant — Provides insights on open rates and click-through rates.
Contact Manager Assistant — Organizes recipient lists and tracks communication.
Create an Assistant
To create a new assistant, follow this step-by-step guide: Add Assistant

Teams: The Asset Grouping Mechanism#

Teams are a collaborative grouping mechanism used to manage permissions for multiple users at once. Instead of adding users individually to every project, you can add them to a Team and then grant that Team access to specific Projects or Assistants.
RoleDescription
AdminCan manage the team's membership and the resources the team has permission to access.
MemberInherits the access levels granted to the team for various projects and assistants.
Create a Team
To create a new team, follow this step-by-step guide: Add a Team

Permission Levels & Inheritance#

Ejento AI uses a simple but powerful system for resource access:
PermissionDescription
Admin (Manage)Full control over the specific resource (Project, Team, or Assistant), including editing settings and managing members.
Member (View)Can view and interact with the resource (e.g., chatting with an assistant) but cannot change its configuration.

How Inheritance Works#

Permissions flow from the top down. If you are granted access at a higher level, you automatically inherit that same access level for all child resources.
Automatic Propagation
If you are an Admin of a Project, you are automatically an Admin of every Assistant inside that Project.
Team Propagation
If your Team is given Member access to a Project, every person in that Team gains Member access to that Project and all its Assistants.
Highest Privilege
If you have multiple access paths (e.g., you are a Member through a Team but an Admin explicitly), the highest privilege (Admin) will always take precedence.

The Importance of This Hierarchy#

This structured hierarchy ensures seamless collaboration and clearly defined responsibilities:
Precision — Focus on specialized tasks within a well-defined Project scope.
Efficiency — Use Teams to manage group access without manual repetition.
Security — Ensure that users only see the assets relevant to their specific assignment.
By understanding this hierarchy, users can effectively navigate Ejento AI to maximize productivity and maintain organized workflows.
Previous
Basic Operations
Next
Login/Signup