Roles

Documentation Index

Fetch the complete documentation index at: https://ai-kb.automationanywhere.com/llms.txt

Use this file to discover all available pages before exploring further.

EKB supports a project-level Role-Based Access Control (RBAC) security model, which determines what users can view, create, modify, and manage within a specific project. These permissions apply only to the selected project and do not affect a user’s access to other projects or their team-level permissions. Each project starts with three default roles — Admin, Editor, and Viewer — which provide a baseline level of access. To support more complex collaboration models, project admins can extend these defaults by creating Custom Roles. Custom Roles allow you to define granular permissions for individual features, including chat, actions, agents, knowledge base content, workflows, analytics, settings, and member management. Project-level roles are evaluated independently from team-level roles. This means a user may have broad permissions at the team level while having limited or highly specific permissions within an individual project, depending on their assigned role. By using project-level RBAC, organizations can:

• Enforce the principle of least privilege within projects.
• Assign access based on responsibilities rather than job titles.
• Safely collaborate with cross-functional or external users.
• Maintain consistency while still allowing flexibility through Custom Roles.

​

Roles List

The Roles list displays all roles available in the project. Use the Search roles field to filter by name. Each role shows the following columns:

​

Default Roles

Every project starts with three default roles:

​

Custom Roles

Custom Roles are created by setting the access level for each feature to View Self, View All, or Edit. When neither View All nor Edit is selected, the default is N/A, meaning the user will either have access only to their own data or will have no access to that feature. Details on what N/A means for each feature are described below.

​

Creating a Custom Role

1. Navigate to Settings → Roles and select the Create New Role button in the upper-right corner.
2. Enter a name in the Role Name field.
3. Select View Self, View All, or Edit for the Chat feature.
   • View Self: Only allows this role to view their own chats.
   • View All: Allows this role to view any chat created by any team member of this project.
   • Edit: Allows this role to edit or delete chats they can view.
4. Set one or more of the following permissions to View All or Edit. The default will be N/A for any feature not configured.
   • Actions: Controls access to the Actions (Tools/Workflows) feature.
     • N/A: Can only access their own Actions.
     • View All: Can view all Actions created in the project by any member.
     • Edit: Can edit all Actions they have access to.
   • Agents: Controls access to create or modify Agents.
     • N/A: Can only access their own Agents.
     • View All: Can view all Agents created in the project by any member.
     • Edit: Can edit all Agents they have access to.
   • Knowledge Base: Controls access to add or modify Knowledge Base content, including Smart Tables.
     • N/A: Cannot access the Knowledge Base.
     • View All: Can view all content within the Knowledge Base.
     • Edit: Can upload, modify, and remove content from the Knowledge Base, including Smart Tables.
   • Documents: Controls access to the Knowledge Base’s Documents section.
     • N/A: Cannot access the Documents section of the Knowledge Base.
     • View All: Can view all Documents in the Knowledge Base.
     • Edit: Can add, edit, and delete Documents in the Knowledge Base.
   • Automator: Controls access to Workflows.
     • N/A: Can only access their own Workflows.
     • View All: Can view all Workflows created in the project by any member.
     • Edit: Can edit all Workflows they have access to.
   • Public Chatbot: Controls access to the Public Chatbot feature.
     • N/A: Has no access to this feature.
     • View All: Can view the Public Chatbot feature.
     • Edit: Can edit the settings within the Public Chatbot feature.
   • Analytics: Controls access to the project Analytics feature.
     • N/A: Cannot access the Analytics feature.
     • View All: Can view the Analytics page.
     • Edit: Can modify the data ranges of the Analytics page.
   • Settings: Controls access to the project Settings feature.
     • N/A: Cannot access the project Settings feature.
     • View All: Can view the project’s Settings.
     • Edit: Can access and modify all project settings.
   • Roles: Controls access to the Roles feature within project Settings.
     • N/A: Cannot access the Roles feature within project Settings.
     • View All: Can view Roles within project Settings.
     • Edit: Can add, modify, and delete Roles within project Settings.
   • Add Members: Controls whether the user can add, modify, or remove members from the project.
     • N/A: Cannot add, modify, or remove members from the project.
     • View All: Can view the project members.
     • Edit: Can add, modify, or remove members from the project.
5. Select the Create button to save the role. The new Custom Role will appear in the Roles list and in the Roles dropdowns used when adding or modifying members.

​

Modifying a Role

1. From the list of Roles, select the Edit link for the role you want to modify.
2. Update the name, description, or access controls, then select the Update button.

Changes will be reflected immediately on the Roles page.

​

Deleting a Role

1. From the list of Roles, select the Delete link for the role you want to remove.
2. Select the Delete User Role button in the confirmation popup.

​

Best Practices

1. Naming: Give Custom Roles descriptive names that make it clear what type of user they are or what they have access to.
2. Documentation: Document your Custom Roles and their purposes with detailed descriptions.