Professional Znuny Support & SLA
Ensure smooth helpdesk operations. Our support plan delivers binding SLAs, expert guidance, and fast incident resolution.
Enter search term – the full-text search scans names, descriptions, and values.
Select result:
Expand widget:
Hover the mouse over the widget → “Edit this setting”:
Change the value and click Save:
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:
.yml files.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:
Further details can be found in the official Znuny documentation.
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 | – |
Professional Znuny Support & SLA
Ensure smooth helpdesk operations. Our support plan delivers binding SLAs, expert guidance, and fast incident resolution.
To access Znuny's System Configuration, you must first log in to the Agent interface with administrator privileges. Once logged in, navigate to the "Administration" section, and from there, select "System Configuration." This central graphical interface provides access to approximately 2,200 configuration keys, allowing you to manage and fine-tune nearly every aspect of your Znuny system, from user interface elements to backend functionalities. The interface also features a full-text search bar to quickly locate specific settings by searching names, descriptions, or even current values.
Quellen / Sources
No, changes made within Znuny's System Configuration do not apply immediately after you click "Save." Saving a setting only stores your local modifications. To activate these changes and make them effective across the entire system, you must explicitly click the "Deploy settings" button. This two-step process ensures that you can make multiple adjustments and review them before pushing them live, preventing partial or unintended configurations from affecting your production environment. It provides a crucial control point for administrators to manage system stability.
Quellen / Sources
Yes, Znuny provides robust mechanisms to undo or revert configuration changes. Every time a setting is modified and saved, the system automatically generates a "Diff Log." This log records the old and new values, offering a clear audit trail of who changed what and when. If a configuration change leads to unintended behavior or errors, you can easily navigate back to the specific setting and use the "Reset" function. This allows you to restore the previous value with a single click, effectively rolling back the change and ensuring system stability without complex manual interventions.
Quellen / Sources
Znuny's System Configuration allows for significant customization of branding and logos. For instance, the agent interface logo can be changed centrally, often involving modifications through .yml files, which are used for deeper system customizations. Additionally, adjustments for the customer portal, such as the sender email for notifications, which can influence branding perception, are managed via configuration keys like NotificationSenderEmail. While NotificationSenderEmail primarily sets the sender address for system notifications, its mention in the context of customer portal branding suggests it's a key setting for customer-facing communication. These configurations ensure a consistent brand experience across both internal and external interfaces.
Quellen / Sources
Znuny's System Configuration offers several key benefits for managing system settings, making customization secure, transparent, and agile. Firstly, it provides a central graphical interface for all modifications, eliminating the need for manual file editing. Secondly, it includes robust versioning and audit logs, documenting who made which changes and when, which is invaluable for compliance and troubleshooting. Thirdly, a built-in rollback mechanism allows administrators to reset any setting to a previous state with a single click, minimizing the risk of misconfigurations. Finally, features like real-time search and import/export capabilities streamline the process of finding settings and synchronizing configurations across different environments (e.g., development, staging, production instances).
Quellen / Sources
Yes, Znuny's System Configuration supports both importing and exporting of entire configurations. This functionality is crucial for several best practices in system administration. You can export your current settings into .yml files to create comprehensive backups, providing a safety net in case of unforeseen issues. Furthermore, the export feature allows you to transfer your customized settings between different Znuny instances, such as moving configurations from a development or staging environment to a production system. Conversely, the import function enables you to load previously exported configurations, facilitating quick synchronization of settings or restoring a system to a known state, ensuring consistency and reducing manual setup time.
Quellen / Sources
Znuny's System Configuration provides comprehensive support for enabling and managing advanced authentication methods, including OAuth2/OpenID Connect and LDAP. These powerful options allow organizations to integrate Znuny seamlessly with their existing identity management systems or Single Sign-On (SSO) solutions. All the necessary parameters and settings for configuring these authentication protocols are available directly within the System Configuration interface. This flexibility ensures that administrators can securely set up and manage user authentication, providing a streamlined and secure login experience for agents and customers without requiring complex command-line interventions or custom code.
Quellen / Sources