The permissions listed on this page grant access to features that have to be enabled or configured system-wide in the Admin Panel first.
Erlaubt Zugang zum 📞 Anrufer-Protokoll
Editor permissions always include reader permissions.
read privileges for internal content
Public articles are always visible.
Zammad supports granular permissions on knowledge base categories.
This function allows agents with editor permissions to restrict specific internal categories & answers to chosen roles.
In order to allow your agents to set granular role permissions, the roles in question require at least reader permission for the knowledge base.
Keep in mind that this may be dangerous, as reader permission provides access to internal answers!
🙅 Gewähren Sie diese Berechtigung niemals Ihren Kunden.
Giving customers access to reporting constitutes a serious data breach, as it includes all ticket and user information across the entire system!
This permission is the exception to the rule on this page:
the feature it enables is not for communicating with customers;
the button appears at the bottom of the sidebar; and
it is typically reserved for admins and supervisors.
🤔 What’s this big table doing here in the middle of my permissions?
Okay, so remember when we said that “roles are just collections of permissions”? That wasn’t entirely true—they can also be collections of group access levels.
To learn more, see Group Access Levels.
🤓 Point of technicality
As of Zammad 3.5, you can assign both agent and customer roles to the same user—but but you can’t assign both
ticket.customerpermissions to the same role!
To make it work, you need two separate roles: one with
ticket.agentand the other with