Adjust permissions for a role or a single user

The Owner creates a role — optionally from an Omnichannel reference permission set — or adjusts the permissions of an existing role or of one user, so that access matches how the company works.

When this happens: Owner opens User Management — Roles, or a your Permissions tab.

Step by step

1
Open User Management — Roles and clicks New Role.
EasyCRM shows the role editor with a Start from a reference set selector: Supervisor, Operator, or none.
2
Select Operator and names the role (e.g. Inbox agent).
Pre-selects the Operator permissions and default visibility scope *Own and unassigned*. Nothing is saved yet.
3
Adjusts individual permissions (e.g. Removes EasyCrm.Conversations.Transfer) and clicks Save.
EasyCRM creates the role, stores its permissions and default scope, and records RoleCreated and one PermissionGranted entry per permission.

Other paths

Adjust an existing role

Open an existing role, toggles permissions and saves. Static roles keep their name; their permissions can still be adjusted.

Adjust a single user

Open a your Permissions tab and grants a permission their roles do not give (e.g. EasyCrm.ReplyTemplates.ManageShared). The grant applies to that user only.

Delete a custom role

Delete a non-static role that no user holds. The system records RoleDeleted.

If something goes wrong

Role still assigned

At the role is held by users. Deletion is blocked: [N] users hold this role. Move them to another role first

Static role deletion attempted

The delete action is not offered for static roles.

Good to know

Personas are reference sets, not seeded roles; the company decides which roles exist.
Effective permissions are the union of the your roles and user-level grants.
Permission changes take effect on the your next request.
Content permissions cannot be granted to host-side roles.