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”- Log in as an administrator in the Agent interface.
- Navigate to Administration → System Configuration.
- Use the full-text search bar to find what you need immediately among the approximately 2,200 configuration keys.
2. Finding and Opening a Setting
Section titled “2. Finding and Opening a Setting”-
Enter search term – the full-text search scans names, descriptions, and values.
-
Select result:
-
Expand widget:
3. Editing and Saving Values
Section titled “3. Editing and Saving Values”-
Hover the mouse over the widget → “Edit this setting”:
-
Change the value and click Save:
-
Confirm the change:
4. Version Comparison & Resetting
Section titled “4. Version Comparison & Resetting”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”:
5. Activating Changes (Deploy)
Section titled “5. Activating Changes (Deploy)”A click on “Deploy settings” applies all local changes:
6. Navigation & Category Tree
Section titled “6. Navigation & Category Tree”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
.ymlfiles. - Import: Load previously exported configurations into another system or synchronize test/staging instances.
8. Special Cases & Best Practices
Section titled “8. Special Cases & Best Practices”8.1 Logos & Branding
Section titled “8.1 Logos & Branding”Change the agent logo centrally via
`.yml“
And adjust the customer portal logo:
NotificationSenderEmail
8.2 Authentication & SSO
Section titled “8.2 Authentication & SSO”Enable OAuth2/OpenID Connect or LDAP flexibly – entirely via System Configuration:
support@<ZNUNY_CONFIG_FQDN>
8.3 Dynamic Fields via Configuration
Section titled “8.3 Dynamic Fields via Configuration”Add new DynamicField drivers without programming:
PostmasterDefaultQueue
8.4 Controlling Menu Modules Individually
Section titled “8.4 Controlling Menu Modules Individually”Activate or deactivate front-end modules like AgentTicketZoom or CustomerTicketSearch via configuration:
FirstnameLastnameOrder
9. Conclusion
Section titled “9. Conclusion”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.
Popular System Configurations
Section titled “Popular System Configurations”Here are the 30 most common system configurations in a clear table.
| Configuration Key | Description | Value |
|---|---|---|
NotificationSenderEmail | Sender email address for system notifications | support@<ZNUNY_CONFIG_FQDN> |
PostmasterDefaultQueue | Default queue for the postmaster | – |
FirstnameLastnameOrder | Order of first and last name | – |
Elasticsearch::TicketSearchFields | Fields used for ticket search in Elasticsearch | – |
Elasticsearch::TicketStoreFields | Fields used for storing tickets in Elasticsearch | – |
GenericAgentAllowCustomScriptExecution | Allows the Generic Agent to execute custom scripts | – |
DashboardBackend::AllowCmdOutput | Allows displaying console output in the dashboard | – |
Ticket::Frontend::CustomerTicketZoom###StateDefault | Default state for the customer ticket view | – |
Ticket::Frontend::CustomerDisableCompanyTicketAccess | Disables customer access to company tickets | – |
ACL::PossibleNot→Form→<Feldname> | ACL setting for negated form conditions | – |
PostmasterFollowUpState | State for postmaster follow-up emails | – |
PostmasterFollowUpStateClosed | Closed state for postmaster follow-ups | – |
Ticket::Frontend::AgentTicketZoomReply | Allows replies in the agent ticket zoom | – |
AgentTicketCompose | Settings for composing new agent tickets | – |
Ticket::Frontend::MenuModule###550-Appointment | Menu module for appointments in the ticket front-end | – |
Ticket::Frontend::MoveType | Settings for the ticket move type | – |
Ticket::Frontend::AgentTicketMove###RequiredLock | Requires lock when moving tickets by agents | – |
Ticket::Frontend::TicketNote###OwnerMandatory | Forces “Owner” as a mandatory field for ticket notes | – |
Core::Crypt::PGP | PGP encryption settings | – |
CustomerDashboard::Tiles###ServiceCatalog-01 | Dashboard tile for the service catalog | – |
Frontend::Module###CustomerTicketMessage | Front-end module for customer ticket messages | – |
CustomerTicketMessage | Configuration for customer ticket messages | – |
CustomerDashboard::Tiles###TicketList-01 | Dashboard tile for ticket list | – |
CustomerFrontend::Module###CustomerTicketMessage | Customer front-end module for ticket messages | – |
Ticket::GenericAgentAllowCustomScriptExecution | Allows Generic Agent to execute custom scripts (ticket module) | – |
Ticket::Frontend::AgentTicketNote###Subject | Subject setting for agent ticket notes | – |
Core::Time::Calendar1 | Time settings for calendar 1 | – |
TimeAccounting | Time accounting module | – |
DynamicField_<Name> | Placeholder for dynamic fields | – |
Ticket::NumberGenerator::MinCounterSize | Minimum counter length for ticket numbers | – |