Group Permissions¶
When assigning an agent to a group, Zammad gives you fine-grained control over what actions that agent can perform within it:
Within each group, the different permissions allow an agent to…
- READ
…view tickets
- CREATE
…create new tickets
- CHANGE
…modify existing tickets
- OVERVIEW
…see ticket overviews (but not ticket details)
- FULL
…all of the above and be assigned / receive notifications for tickets
Note
🔔 Full group access also enables notifications for that group’s tickets.
Setting Permissions¶
There are two ways to define an agent’s per-group permission levels:
Directly, in the Edit User dialog in the table of group permissions:
Implicitly, by editing a user role
First, head over to Roles to set up the permissions you want to assign. Example:
Then you are good to go to assign the role to a user in the user edit dialog. Example:
Attention
Make sure to click on the ➕ Add button after assigning the last group. Otherwise, your last selection will not be saved.
Note
⚖️ We recommend choosing one or the other; things can get confusing if you use both at the same time.
So which one is right for you? Whichever one is less work. If you’re trying to assign multiple agents to the same group with the same permissions, create a role for them to share—that’s what roles are for!
🤔 Can’t see the group permission table?
Please make sure that you have selected the ticket.agent
permission for
the user or role.
Examples¶
- “The Standard Issue”
-
When a system only has one group, this is the default permission level assigned to all agents. Unless you have special needs in mind, this is the way to go.
- “The Supervisor”
-
Agents with all permissions except for “full” cannot be assigned tickets. Otherwise, their privileges are identical to agents with “full” access. Great for letting other people do the real work.
- “The Meddler”
-
Agents with “read”, “change”, and “overview” access can do everything except create tickets or be assigned to them. Great for getting involved in other people’s business.
- “The Intern”
-
Agents with only “create” permission can do just that, and nothing else—once they hit Save, they’ll never see that ticket again. Great for taking phone calls for someone more important than you.