DOCSEARCHbyAlgolia
Submit Docs

Ejento AI Documentation

website·Indexed 32 days ago

https://docshub.ejento.ai

Documentation for Ejento AI, a platform for creating dynamic multi-assistant workflows and AI assistants. Features include an Analytics dashboard, permission sets, and tools for content creation and customer support. Includes integration guides for Discord, Slack, Google Drive, and SharePoint MCP, as well as setup instructions for Microsoft SSO and Vertex AI keyless authentication.

Tokens
13.1K
Snippets
20
Records
96
Agent score
51%

What's inside Ejento AI

  1. Overview of Azure App Service to Vertex AI Keyless Authentication

    Workload Identity Federation (WIF) allows Azure workloads (App Service, VM, Container App) to authenticate with Google Cloud Platform (GCP) without long-lived service account keys. The authentication flow is:

    1. Azure App Service Managed Identity issues a short-lived Azure AD JWT.
    2. The JWT is exchanged at the GCP Security Token Service (STS) for a federated token.
    3. The federated token is used to impersonate a GCP Service Account.
    4. The service account token is used to call Vertex AI model endpoints.

  2. Overview of the Ejento AI Analytics Dashboard

    The Analytics dashboard is a monitoring tool for Global Admins to track system-wide activity and performance across an organization. It aggregates raw usage data into interactive charts and distribution tables to help administrators optimize AI implementation and identify usage trends. Access to the Analytics section is restricted exclusively to Global Admins.

  3. Overview of Ejento AI Tools

    Tools are a framework that provides Ejento AI assistants with specialized abilities to retrieve information, perform external actions, interact with APIs/databases, and work with documents. Access to the Tools section in the Ejento app is restricted to Global Admins.

  4. Manage access using Permission Sets

    Permission Sets are reusable bundles of access rules assigned to users to control what they can create, view, edit, delete, and deploy across the organization. They govern three resource types: assistants, corpora, and workflows. Each resource type is configured separately within a set, allowing for granular control (e.g., wide access to assistants but restricted access to corpora).

  5. Configure ETags for Corpus Incremental Refresh

    The Incremental Refresh feature in Corpus relies on correctly configured ETags (Entity Tags) to identify changes in resources. If the ETag value of a URL remains unchanged, Corpus skips re-indexing that content. Without proper ETag setup, Incremental Refresh will not function as intended.

  6. Understand Ejento Workflow operation and supervisor types

    Ejento workflows allow users to combine multiple assistants to process complex queries. Every workflow requires a supervisor to manage how assistant responses are handled and delivered to the user. Depending on the supervisor chosen, the system will either select a single best response or aggregate multiple responses, while always referencing which assistants contributed to the final answer.

  7. Manage Public assistants and corpora

    Making an assistant or corpus Public shares it with all users in the organization at a member access level. This does not override Permission Set requirements; a user must still possess a Permission Set that grants 'view' capability for that resource kind to actually access the public resource.

    Note: Workflows cannot be made public.

  8. Connect a Google Drive folder to the agent corpus

    To sync a Google Drive folder as a knowledge source, navigate to the Corpus page and click Add +. In the Sync Content section, select Google Drive. You must provide a URL that points to a folder (not an individual file). After entering the URL, click + Connect, sign in with the Google account that has access to the folder, and grant the requested read permissions. Once authorized, the folder will appear in the documents list with a 'Completed' status when indexing is finished.
    Example folder URL format: https://drive.google.com/drive/u/0/folders/<FOLDER_ID>

  9. Index a website via Sitemap in Ejento AI

    To index an entire website, navigate to the "Sitemaps" tab and enter the website's sitemap URL.

    Configuration Option:

    • Enable sync: When toggled on, Ejento AI automatically keeps the sitemap updated with new files and changes. If disabled, only the documents present at the time of connection are indexed once.

    After entering the URL and setting the sync preference, click "Connect" to begin indexing.

  10. Automate Azure AD app registration using sso_app.ps1

    Developers can automate the creation of the Ejento MS SSO Azure AD app registration using a PowerShell script. This script handles app creation, service principal creation, permission setup, and client secret generation, outputting the results to a JSON file in the local directory.

    Prerequisites:

    • Azure CLI installed and added to PATH.
    • User must be signed into the correct Azure tenant (az login --use-device-code).
    • Tenant setting 'Users can register applications' must be set to 'Yes' in Entra ID → User settings.
    # Save the provided script as sso_app.ps1
# Run in PowerShell:
.\sso_app.ps1

  11. Grant Corpus access to individual users

    To add a user to a corpus:

    1. In the Edit Corpus menu, click Add User.
    2. Select the desired user.
    3. Assign a role: Admin or Member.
    4. Click Add.
    5. Click Update Corpus to save changes.

    Important: Sharing a corpus only specifies which corpus a user can access. The actual actions they can perform (view, edit, delete) are determined by the intersection of their assigned role and the Permission Sets they hold.

  12. Generate and Secure a Client Secret for SharePoint MCP

    A client secret is required for the MCP server to authenticate with Microsoft Entra ID:

    1. Navigate to Certificates & secrets → Client secrets → New client secret.
    2. Provide a description and expiry date, then click Add.
    3. Copy the Value immediately, as it is only displayed once.

    Security Warning: Store the client secret only in Azure Application Settings. Never commit it to source control or include it in screenshots. Rotate the secret before it expires.