You can provide overviews to your agents and customers. They can be used as a kind of worklist of tasks that the agent is supposed to work off. You can also create individual overviews for individual agents or agent groups.

In the overview management area you can add new overviews, edit or delete them.


Please note that overviews can cause performance issues leading to no longer or less often refreshing overviews!

Whenever possible, try to use the same overviews for as many agents and groups as possible to keep the number of overviews low. For best results, you might want to use between 15-20 overviews maximum. Also, any overview will only show a total of 2100 elements.


Overviews will only show tickets to your users, that the user have rights on (group or role based).

The following attributes can be set when creating an overview:


Available for the following roles / Restrict to only the following users


Roles are assigned to users, per default there are agents, admins and customers. Further information about Roles.


The setting “available for the following roles” is mandatory.

Define roles that are supposed to see and use the overview in question.

If your overview is rather specific for a sub group of users of your role, use the “Restrict to only the following users” option to further restrict the visibility of the overview to defined users.


You will still have to provide a role!

Only available for users with shared organization



Shared organization is a setting in the organization management. See Organizations for more information.

This is only important if the available role is a customer. Whether you select Yes or No depends on whether you want one of your customer’s contacts to see all of their organization’s tickets.


Users also refers to the customer role in this case.

Only available for users which are absence replacements for other users.

This selection refers to the setting in the user preferences (profile-picture / initials of agent in the left corner > profile > out of office). If this option is checked, this selection is only displayed if someone has been entered as a substitution.

For example: Agent A is on vacation and Agent B will take care of his tickets. Then an overview can be set up, which only shows Agent B all new tickets from Agent A for this period of time, without having to search for them separately.


Replacement users are part of our Out of Office function.

Conditions for shown tickets

Which tickets should be shown in this overview? The conditions can be seen like a filter. You can add more than one condition. In the preview you have the possibility to double check if your entry of the conditions makes sense by directly displaying tickets that match your filtering.


👋 Looking for more depth explanation on conditions? 🤓

Many condition settings in Zammad, no matter if in ticket scope or not, re-appear in several places of Zammad. For this reason we created a dedicated documentation section to avoid duplicate content.

Have a look at Object conditions to learn even more! 🎉


Which attributes (column headers) shall be shown in the overview?

With this setting you can select the headlines of your overview. Depending on which information is important in this selection, it can be displayed individually. For this example “Unassigned and open”, the overview would look like this:


These settings can also be adjusted individually by admins at a later time (in the overview, top right: Options).


Please note that overview column and sort settings are global settings which affect all users seeing those overviews.

Sorting, Grouping and Active
Sorting by

In which order should the tickets be displayed? (Sorted by the attributes)

Sorting order

The direction of the sorting.

Grouping by

Should the tickets be grouped by a specific attribute within the list?

Grouping order

The direction of the grouping.


Should the overview be active or not? Rather than deleting an overview entirely, you can set it to inactive to make it unavailable to your users.


Users can define their own overview order. Renaming or reordering overviews has no effect on custom orders!

You can learn more about this setting in the user documentation.