Access Levels in Ex.Brain define what your team members can do and see. You can use them to set permissions for Ex.Brain, Blocks, meetings, STK, and other features. This lets you create roles like “Admin,” “Analyst,” or “Location Manager” that align with your actual job titles and security requirements.
How to Create a New Access Level #
Where to Manage Access Levels #
- Go to the Team Management section in the sidebar
- Click the Access Levels tab
You’ll see a list of access level profiles. You can view, edit, or add new ones.
Click + Add Access Level and complete the following sections.
Step 1 – Name Your Role #
Field | Description | Required? |
| Access Level Name | Descriptive title like “Franchise Manager” or “Staff – Finance Only” | ✅ |
| Description | Optional text explaining what this role is for | Optional |
Step 2 – Configure Feature Access #
Choose permissions for each product or module.
Ex.Brain Interaction #
- Full access to all answers
- Restricted access to assigned locations
- Personal-only conversation analytics (coming soon)
Blocks (Datasets) #
- Full or limited view of blocks
- Create/edit/delete capabilities
- Manage across all or assigned locations
Meetings (Organizer) #
- Enable meetings
- Full or restricted meeting analytics (coming soon)
STK (Speech to Knowledge) #
- Enable recording and uploads
- View own or team-wide analytics (coming soon)
Data Lake (coming soon) #
- Customer profile and order access controls
Step 3 – Assign Block Category Permissions #
Below the feature matrix, you’ll find a list of your Block Categories.
- Check each category this Access Level can view or manage
- Optionally assign these permissions only for specific Workspaces
Example: A role may be allowed to access “Finance Reports” in the NY branch, but not in HQ or LA
Editing an Access Level #
- Click the Edit (pencil) icon beside any role
- Adjust any toggle, checkbox, or assignment
- Save your changes to apply immediately
All affected users will inherit the updated permissions
Best Practices #
- Create roles based on real responsibilities, not just titles
- Use descriptive naming (“Ops – Read Only”) to avoid confusion
- Test new roles with test users before assigning company-wide
- Set up inheritance-like logic: Editors > Managers > Admins