Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Assistants
  • 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. Assistants

Overview

Assistants in Ejento AI are AI helpers built for a specific job, such as answering HR questions, supporting a sales team, or explaining a company policy. Each assistant combines a language model with your organization's documents, tools, and instructions, so its answers fit your work instead of the open internet.
An assistant's page with its Configuration panel

Why assistants matter#

Answers grounded in your knowledge. An assistant searches the documents in its corpus, so people get answers based on your current policies and guides.
Built for a role. Each assistant has its own role and instructions, so it stays on topic and speaks the way you want.
Safe to change. You edit a private Staging copy and deploy when you're ready, so people never see half-finished changes.
Shared on your terms. Keep an assistant private, share it with chosen users and teams, or make it public to the whole organization.
Measurable. Evaluations score an assistant's answers, so you can prove that a change made it better.

How assistants work#

1.
Create an assistant in a project by describing its job. See Add Assistant.
2.
Configure it in Staging: add documents, tools, guardrails, and instructions, and pick a model. See Edit Assistant.
3.
Test it by chatting in Staging, or by running an evaluation. See Evaluate Assistant.
4.
Deploy your changes to Production, where people use the assistant.
5.
Share it with users and teams, embed it, or make it public. See Assistant Edit Access.

Key terms#

Project: The group an assistant belongs to. People with access to a project get access to its assistants. See Hierarchy.
Staging and Production: Every assistant has a Staging version, where you make changes, and a Production version, which people use. Changes reach Production only when you deploy them. See Staging & Publishing.
Draft and Live: A new assistant starts as a draft. It becomes live the first time you deploy it.
Visibility: A Private assistant is available only to you and the people you give access to. A Public assistant is available to everyone in your organization. See Assistant Access Control.
Corpus: The documents an assistant searches to ground its answers. Each new assistant gets its own default corpus. See Corpus Overview.
Model: The large language model (LLM) that understands requests and writes the assistant's responses.

What makes up an assistant#

You configure an assistant in the Configuration panel on its page, in Staging:
SectionWhat it controls
Assistant ToolsExtra capabilities. Internal tools are built into Ejento AI; External tools connect to other applications. See Tools.
CorpusThe documents the assistant searches.
GuardrailsSafety filters: Topical Control, Ethical Moderation, Jailbreak Detection, Hallucination, and PII Redaction. See Understanding Guardrails.
CustomizeThe Assistant Role, Custom Instructions, Conversation Starters, and Tags.
AdvancedThe Assistant Default Model, Reasoning Pattern (how the assistant works through a request; see Reasoning Patterns), Visibility, Publish to Coworkers, voice Call, and Enable Embed Link.
Deployment HistoryPast deployments, which you can restore.
The panel also lists the assistant's Chats, Attachments, and Pinned Messages.

Use cases#

Employee self-service: An HR assistant with the employee handbook in its corpus answers leave and benefits questions at any hour, so the HR team spends less time on repeat questions.
Policy guide: A finance assistant answers travel and expense questions only from the official policy, with a custom instruction to say when the policy doesn't cover a question.
Team expert: An engineering assistant connected to your runbooks helps new team members find the right procedure without interrupting colleagues.

Who can work with assistants?#

What a person can do with an assistant depends on its visibility, the role they have on the assistant or its project (Member or Admin), and their Permission Sets. See Assistant Access Control.
To create your first assistant, see Add Assistant.
Previous
Assistants
Next
Assistant Access Control