Under Administration > Ticket System > Settings you configure all ticket-specific options company-wide. The order of the following sections matches the layout of the settings dialog exactly.
Customer access
Three settings control what customer contact persons see via customer access and which actions they may perform. The detailed configuration of the access itself is described in the article on customer access.
Customer access to tickets is read-only
Disables all editing actions for customer contact persons. They can only view tickets, no comments or attachments can be added, no status changes performed.
Access to all assigned tickets regardless of permissions
Overrides per-project permissions whenever the contact person is set as customer contact person on the ticket, they always see the ticket, even without explicit project access.
Access permission to internal projects
Adds internal projects to the per-contact permission picker. Without this option, only external customer projects are selectable.
Creator and history
These three options control whether fields and comment entries can be changed afterwards and who may make such changes.
The creator of a ticket can be changed
When creating or editing a ticket, the creator can be chosen manually from project or task members.
Last history entry editable by author after the fact
The author of a comment can edit their last entry and attachments as long as no further entry follows.
History editable by project managers after the fact
Project managers can adjust any entry in the entire history, including comments written by others.
Time recording on tickets
Three options control which tickets are offered in the project-time picker and whether bookings outside the duration or on closed tickets are allowed.
Offer tickets of all employees in time recording
By default, employees see only their own tickets in time recording. With this option, tickets of other project members also appear in the picker.
Allow time recording only within the ticket duration
Bookings before the start date or after the deadline are rejected by the system.
No time booking on closed tickets
Tickets in an end status (accepted, rejected) are locked for project-time bookings.
Permissions, visibility and entry
Up to four options control permission scope, visibility of planned hours and keyword maintenance. The first option is only shown if the corresponding parameter was saved at least once before.
Ticket permission only for project members
Restricts ticket visibility to project members. Without this option, employees outside the project may also see tickets if their role allows it.
Show planned hours for all employees
By default, planned hours are only visible to project managers and administrators. With this option, all users with ticket access see the stored planned hours.
Creator may enter planned hours on new ticket
Allows the creator to enter planned hours on creation or on the first edit step in status new, otherwise only project managers and administrators can do so.
Employee may add keywords
Lets employees create new keywords directly on the ticket, which are then taken into the master data. Without this option, only administrators may create new keywords.
Mailbox address as sender
Via the option Use the e-mail address of the associated ticket mailbox as the sender address for ticket e-mails you control whether ZEP sends notifications with the mailbox address, so replies land directly in the correct inbox. Without this option, the global ZEP sender address from the mail settings is used.
Custom labels for priorities
The checkbox Use custom designations for ticket priorities enables custom texts for the five standard priorities (1 to 5). Once active, 5×3 input fields appear below the checkbox: one entry per priority and per available language (German, English, French).
If a language field stays empty, the standard numbering ("1", "2", …) is used. Common pattern: "A, Immediately", "B, High", "C, Medium" etc. The internally used priority (1–5) stays unchanged; the aliases only affect the display in the UI and in mails.
Filter for the ticket mailbox
Under the label Check mailboxes for tickets (matching the name of the corresponding scheduler task) you configure a global regex filter for all mailbox retrievals. This setting affects every active mailbox.
Filter messages by subject
Activating the checkbox shows a textarea where you enter the regular expression. Only mails whose subject matches are processed into tickets.
Delete filtered-out messages from the mailbox
Sub-option of the filter: when active, non-matching mails are immediately deleted from the server, otherwise they remain.
Note: The filter only applies to the mail subject, not the mail body. The detailed processing logic is described in the article Mailboxes and automatic tickets.



