Skip to content

Znuny System Configuration – Managing Settings

Znuny System Configuration – Managing Settings

Section titled “Znuny System Configuration – Managing Settings”

The System Configuration in Znuny is the heart of customization and fine-tuning:
– All changes are made via a central graphical interface.
– Versioning and audit logs document who, when, and which values were changed.
– In case of errors, every setting can be reset to a previous state.

Section titled “The System Configuration in Znuny is the heart of customization and fine-tuning: – All changes are made via a central graphical interface. – Versioning and audit logs document who, when, and which values were changed. – In case of errors, every setting can be reset to a previous state.”

1. Quick Start: Opening System Configuration

Section titled “1. Quick Start: Opening System Configuration”
  1. Log in as an administrator in the Agent interface.
  2. Navigate to Administration → System Configuration.
  3. Use the full-text search bar to find what you need immediately among the approximately 2,200 configuration keys.

  1. Enter search term – the full-text search scans names, descriptions, and values.

  2. Select result:

  3. Expand widget:


  1. Hover the mouse over the widget → “Edit this setting”:

  2. Change the value and click Save:

  3. Confirm the change:


After saving, a Diff Log is automatically generated – this allows you to see old vs. new values at a glance:

If something goes wrong, you can jump back to the previous value at any time using “Reset”:


A click on “Deploy settings” applies all local changes:


The navigation tree on the side organizes configurations by modules and subgroups.
Each category shows the number of its entries in parentheses:

This helps you keep track even when using add-on packages (e.g., ITSM, FAQ, OAuth).

Section titled “This helps you keep track even when using add-on packages (e.g., ITSM, FAQ, OAuth).”

7. Import & Export of Entire Configurations

Section titled “7. Import & Export of Entire Configurations”
  • Export: Create backups or transfer your settings into .yml files.
  • Import: Load previously exported configurations into another system or synchronize test/staging instances.

Change the agent logo centrally via
`.yml“

And adjust the customer portal logo: NotificationSenderEmail

Enable OAuth2/OpenID Connect or LDAP flexibly – entirely via System Configuration: support@<ZNUNY_CONFIG_FQDN>

Add new DynamicField drivers without programming: PostmasterDefaultQueue

Activate or deactivate front-end modules like AgentTicketZoom or CustomerTicketSearch via configuration: FirstnameLastnameOrder


The Znuny System Configuration provides you with:

  • Real-time search function: Find any key in seconds.
  • Audit & Versioning: Every value change is documented.
  • Rollback mechanism: One click back – no fear of misconfigurations.
  • Import/Export: Perfect synchronization between production, staging, and test instances. With these features, you can adapt your Znuny system securely, transparently, and agilely to any new scenario – from branding and auth to individual plugins.

Further details can be found in the official Znuny documentation.

Here are the 30 most common system configurations in a clear table.

Configuration KeyDescriptionValue
NotificationSenderEmailSender email address for system notificationssupport@<ZNUNY_CONFIG_FQDN>
PostmasterDefaultQueueDefault queue for the postmaster
FirstnameLastnameOrderOrder of first and last name
Elasticsearch::TicketSearchFieldsFields used for ticket search in Elasticsearch
Elasticsearch::TicketStoreFieldsFields used for storing tickets in Elasticsearch
GenericAgentAllowCustomScriptExecutionAllows the Generic Agent to execute custom scripts
DashboardBackend::AllowCmdOutputAllows displaying console output in the dashboard
Ticket::Frontend::CustomerTicketZoom###StateDefaultDefault state for the customer ticket view
Ticket::Frontend::CustomerDisableCompanyTicketAccessDisables customer access to company tickets
ACL::PossibleNot→Form→<Feldname>ACL setting for negated form conditions
PostmasterFollowUpStateState for postmaster follow-up emails
PostmasterFollowUpStateClosedClosed state for postmaster follow-ups
Ticket::Frontend::AgentTicketZoomReplyAllows replies in the agent ticket zoom
AgentTicketComposeSettings for composing new agent tickets
Ticket::Frontend::MenuModule###550-AppointmentMenu module for appointments in the ticket front-end
Ticket::Frontend::MoveTypeSettings for the ticket move type
Ticket::Frontend::AgentTicketMove###RequiredLockRequires lock when moving tickets by agents
Ticket::Frontend::TicketNote###OwnerMandatoryForces “Owner” as a mandatory field for ticket notes
Core::Crypt::PGPPGP encryption settings
CustomerDashboard::Tiles###ServiceCatalog-01Dashboard tile for the service catalog
Frontend::Module###CustomerTicketMessageFront-end module for customer ticket messages
CustomerTicketMessageConfiguration for customer ticket messages
CustomerDashboard::Tiles###TicketList-01Dashboard tile for ticket list
CustomerFrontend::Module###CustomerTicketMessageCustomer front-end module for ticket messages
Ticket::GenericAgentAllowCustomScriptExecutionAllows Generic Agent to execute custom scripts (ticket module)
Ticket::Frontend::AgentTicketNote###SubjectSubject setting for agent ticket notes
Core::Time::Calendar1Time settings for calendar 1
TimeAccountingTime accounting module
DynamicField_<Name>Placeholder for dynamic fields
Ticket::NumberGenerator::MinCounterSizeMinimum counter length for ticket numbers