Roles & Permissions
Roles & Permissions lets you control what each team member can see and do in EzPulze. You create roles (like "Sales Agent" or "Campaign Manager"), assign specific permissions to each role, and then assign the role to users.
2. Capture the table showing several roles with different statuses and agent role indicators
Save to:
static/img/screenshots/organization/roles-and-permissions/roles-list.pngRoles list​
The list page shows all roles in a table:
| Column | Description |
|---|---|
| # | Row number |
| Name | Role name |
| Status | Active or Inactive |
| Is Agent Role | Yes or No — indicates if this role is for agents (see Agent roles) |
| Actions | View, Edit, Delete |
Actions​
| Action | Description |
|---|---|
| View | See the role's permissions in read-only mode |
| Edit | Modify the role name, status, or permissions |
| Delete | Remove the role (only if no users are assigned to it) |
System roles like Super-Admin and Admin are marked with a lock icon. They cannot be edited or deleted — only viewed.
Pagination​
You can display 10, 25, or 50 roles per page.
Creating a role​
Click the Add Role button to open the role dialog.
2. Enter a role name
3. Select several permissions from different categories
4. Capture the full dialog showing the 3-column layout
Save to:
static/img/screenshots/organization/roles-and-permissions/create-role-dialog.pngRole fields​
| Field | Required | Description |
|---|---|---|
| Name | Yes | A descriptive role name (e.g., "Sales Agent", "Campaign Manager", "Viewer") |
| Is Agent Role | No | Check this if the role is for frontline agents (see Agent roles) |
| Status | Edit only | Active or Inactive (only shown when editing) |
| Permissions | No | Select which features this role can access |
Permission selector​
The permission selector uses a 3-column layout to make it easy to find and assign permissions.
2. Show the available scopes in the center column
3. Select a few scopes so the right column shows selected permissions
4. Capture all three columns
Save to:
static/img/screenshots/organization/roles-and-permissions/permission-selector.pngLeft column — Categories​
Browse permissions by category. Each category shows a badge with the count of selected / total permissions.
| Category | What it covers |
|---|---|
| Dashboard | Dashboard access and viewing |
| Messaging | Templates, broadcasts, chat, compose message |
| Customer Management | Contacts, leads, groups, follow-ups, custom fields |
| Automation | Chatbot flows, drip campaigns |
| Reports & Analytics | Reports and analytics access |
| Organization | Users, roles, teams, departments |
| File Manager | Upload and manage files |
| Settings | System configuration, billing |
| Developer Tools | API keys, webhooks, WhatsApp Flows |
| Other | Ungrouped or miscellaneous permissions |
Center column — Available scopes​
Shows all permissions in the selected category. Each permission appears as a chip:
| Icon | Meaning |
|---|---|
| Check circle (green) | Already selected |
| Plus circle (blue) | Available to add |
| Block (gray) | Disabled — requires a parent permission to be selected first |
Use the search bar at the top to filter permissions by name.
Quick actions:
- Select All — Selects all permissions in the current category
- Clear — Removes all selected permissions
Right column — Selected scopes​
Shows all permissions you've selected across all categories, grouped by category. Click the remove button on any permission to deselect it.
A counter at the top shows the total number of selected permissions.
Permission dependencies​
Some permissions depend on others. For example:
leads:createrequiresleads:readAll— you can't create leads without being able to view themcontacts:updaterequirescontacts:read
If a permission depends on another, the dependent permission is disabled (shown with a block icon) until the parent permission is selected.
Agent roles​
When you check Is Agent Role, the system automatically:
- Removes restricted permissions — Certain system-level permissions (like managing roles, billing, or system configuration) are automatically excluded from agent roles
- Enables agent-specific features — The user appears in the agent dropdown for chat assignment, lead assignment, and auto-assignment
What agents typically need​
| Permission | Why |
|---|---|
| Chat access | To respond to customer messages |
| Contact read | To see customer information |
| Lead read/update | To manage assigned leads |
| Follow-up create | To schedule follow-ups with customers |
| Template read | To send template messages from chat |
What agents typically don't need​
| Permission | Why |
|---|---|
| User management | Only admins manage team members |
| Role management | Only admins define roles |
| Billing access | Only admins manage billing |
| System configuration | Only admins change settings |
| API key management | Only developers manage integrations |
Editing a role​
Click Edit on any role to modify it. The edit dialog is the same as the create dialog, with an additional Status field to set the role as Active or Inactive.
If you change a role's permissions, all users with that role are immediately affected — they gain or lose access based on the updated permissions.
Deleting a role​
Click Delete on a role, then confirm the deletion.
You cannot delete a role that is assigned to users. Reassign those users to a different role first.
Built-in roles​
EzPulze comes with these system roles:
| Role | Agent role | Restricted | Description |
|---|---|---|---|
| Super-Admin | No | Yes (locked) | Full access to everything. Cannot be edited or deleted. |
| Admin | No | Yes (locked) | Full access. System-protected. |
| Agent | Yes | No | Basic agent permissions. Can be customized. |
You can create as many additional custom roles as needed.
Tips​
- Start with scope groups — Begin by giving roles broad category access, then fine-tune individual permissions as needed
- Create role per function — Instead of one generic "Staff" role, create specific roles like "Sales Agent", "Support Agent", "Campaign Manager"
- Test with a user — After creating a role, log in as a user with that role to verify they see exactly what they should
- Use the agent role flag — Mark frontline staff roles as agent roles so they appear in assignment dropdowns
- Review permissions regularly — As your team grows, review roles to ensure everyone has appropriate access