This guide details the granular permission structures for resources within Ejento AI, enabling you to control collaboration and visibility at every level. Resource Permissions (Teams, Projects, Assistants)# Every resource in Ejento AI — whether it's a Team, a Project, or an individual Assistant — uses two primary permission levels: Admin and Member . Admin# The Admin holds full administrative privileges over the specific resource. Capability Details Manage Can edit settings, change configurations, and manage the list of members and admins. Delete Has the authority to delete the resource if it is no longer needed. Usage Full access to all features (e.g., chatting with assistants, indexing data). Propagation Admin access to a Project automatically grants Admin access to all Assistants within that Project.
Member# The Member role is designed for standard usage and collaboration. Capability Details Usage Can view the resource and use its primary functions (e.g., chatting with an assistant). Restrictions Cannot delete the resource, change its settings, or manage other users' access.
Assistant Accessibility Levels# The Accessibility Level determines who can find and interact with an assistant. Private# A Private assistant is restricted to specific users. Attribute Details Visibility Only visible to the assistant's creator, Global Admins, and anyone explicitly granted access — either directly or through a Team or Project. Usage Ideal for internal collaboration, protected data, or focused project work.
Public# A Public assistant is accessible to a wider audience, including those outside your organization. Attribute Details Visibility Can be searched and accessed by anyone with a link or via an embedded widget. View Only Users can chat with the assistant but cannot see the underlying configurations. Edit Access Collaborative sharing that allows others to help configure the assistant. Embeddable Public assistants can be added to external websites.
Embedding a Public Assistant
How Access Flows Down (Inheritance)# To keep management simple, access is inherited through the hierarchy: 1.
Organization Roles — Global Admins automatically have Admin access to everything.
2.
Team Assignments — If your Team is added to a Project as a Member, you gain Member access to that Project and every Assistant inside it.
3.
Project Assignments — If you are added as an Admin to a Project, you are automatically an Admin for all current and future Assistants in that Project.
Choose your access levels carefully to balance ease of collaboration with the security of your organizational assets.