Every person in your Ejento AI organization has a role. The role decides what they can manage across the whole organization, while their access to individual teams, projects, and assistants decides what they can use day to day. Getting both right lets people collaborate freely without exposing data they shouldn't see.Why roles and access matter#
The right access for each job. Administrators get the controls they need, and everyone else gets a simple, focused workspace.
Security by default. New users start with the least access, and you raise it only where it's needed.
Less manual work. Access is inherited from organizations, projects, and teams, so you rarely need to grant it person by person.
How access is organized#
Access in Ejento AI works on three levels:1.
Organization roles set what someone can manage across the whole organization: Global Admin, Application Admin, or User.
3.
Assistant visibility sets who can find an assistant: Private or Public.
Organization roles#
When you add a user, you choose one of three roles. The app describes them as follows.| Role | Best for | What it allows |
|---|
| Global Admin | Business owners and company administrators | The highest level of control. Acts as an Admin for every team, project, and assistant in the organization, and can access Organization settings, including Users & Teams. |
| Application Admin | Managing users and teams | Elevated access for running day-to-day operations, such as creating teams, projects, and assistants. |
| User | Interacting with app features and functionalities | The default role. Uses the projects and assistants they have access to, and manages the assistants they create or are given Admin access to. |
User is the default role for new users, and people who join through an invite link join as Members. You can change someone's role later from the Users tab.
How access flows down#
Access in Ejento AI is inherited from the top down:1.
Organization: Global Admins automatically have Admin access to every project and assistant.
2.
Project: An Admin of a project is automatically an Admin of every assistant in it.
3.
Team: When a team is given access to a project, every member of the team gets that access to the project and its assistants.
4.
Highest access wins: If someone has access in more than one way, they get the highest level.
For example, if someone is a Member of a project through their team but was also added directly as an Admin, they get Admin access.
Use cases#
Small company: Make the founders Global Admins so they can step into any project, and everyone else a User. People see only the projects and assistants they've been given, plus Public assistants.Delegated operations: Make an operations lead an Application Admin. They set up new teams, projects, and assistants day to day, without having full control of the organization.Client work: Create one project per client and add each consulting team to its client's project as a Member. Consultants use only their own clients' assistants.FAQs#
Who can add users or change their roles?#
Only Global Admins can access the Users & Teams settings, where users are added, invited, and given roles.What are Permission Sets?#
Organization-wide, reusable rules that decide which actions a person can perform, for example whether they can create corpora. They're assigned to users or teams and work together with roles. See Corpus Permissions for an example.How do I give someone access to a specific project?#
