Understanding assistant accessibility levels and collaborative permissions in Ejento AI is essential for managing who can view and modify your work. These settings provide the flexibility to keep projects secure while enabling seamless teamwork across your organization.
Assistant Accessibility Levels#
Assistants in Ejento AI have two primary accessibility levels that determine their visibility:1. Private#
| Attribute | Details |
|---|
| Visibility | Restricted to specific authorized users. |
| Access Path | Only visible to the assistant's creator, Global Admins, and anyone who has been granted access through a parent Project or an assigned Team given that they have a permission sets assigned that grants them relevant access. |
| Purpose | The default setting for most assistants. It ensures complete privacy while developing or working on sensitive organizational tasks. |
Private is the default accessibility level for all newly created assistants.
2. Public#
| Attribute | Details |
|---|
| Visibility | Accessible to everyone, including those outside your organization, via a direct link or external embed. |
| Purpose | Ideal for widely shared tools, customer-facing support widgets, or public knowledge bases. |
| View Only | Users can chat with the assistant but cannot see its internal configurations. |
| Edit Access | Allows others with the link to help configure and refine the assistant. |
Public assistants are accessible to everyone given that the user must also hold a Permission Set granting view permission on assistants at any scope. Ensure no sensitive or confidential information is embedded in a Public assistant's configuration.
Permission Propagation & Collaboration#
Access to an assistant is often inherited from higher levels in the hierarchy. This makes managing large groups of users simple and efficient.Inherited Access#
| Inheritance Type | Details |
|---|
| Project Inheritance | If a user is added as a Member or Admin of a Project, they automatically receive that same level of access to every Assistant within that project. |
| Team Assignment | Granting a Team access to a Project or Assistant immediately shares that access with every individual in that team. |
Access inherited from a project or a team does not grant its members access automatically. Each member gains access only if they hold a Permission Set that allows the action on assistants in the projects they have access to or assistants shared with their teams.Member — allows a user to view the assistant if their Permission Set grants view on assistants shared with the user's teams or the assistants in the projects user has access to. It is capped at view: the member cannot edit, delete, or deploy the assistant, even if a Permission Set would otherwise grant those actions.
Admin — allows a user to view, edit, delete, or deploy the assistant, action by action, for each action their Permission Set grants on assistants shared with the user's teams or the assistants in the projects user has access to.
Collaborative Edit Access#
The Assistant Edit Access capability allows those with Admin rights — either assigned directly or inherited — to modify the assistant's settings. This facilitates:| Benefit | Details |
|---|
| Shared Responsibility | Multiple team members can co-manage an assistant's knowledge base and tools. |
| Security | Only authorized users with Admin status can perform destructive actions like deletion or sensitive configuration changes. |
| Flexibility | Ownership and management rights can be adjusted as project needs evolve. |
Whether you are building a private tool for personal productivity or a public assistant for global reach, Ejento AI's access control ensures your work remains secure and accessible to the right people. By leveraging Projects and Teams, you can maintain control over your assistants with minimal administrative effort.
