Skip to content
Znuny Logo Znuny Community Docs

Introduction to Znuny

Introduction to Znuny

Section titled “Introduction to Znuny”

Welcome to the Znuny Community Docs! This guide will help you get started with Znuny – the open-source ticket system for professional service management.

What is Znuny?

Section titled “What is Znuny?”

Znuny is a powerful, flexible ticket system for managing customer inquiries, support tickets, and service processes. It offers:

  • Structured ticket management – Capture, categorize, and prioritize requests efficiently
  • Automation – Reduce manual work through rules, processes, and generic agents
  • Dynamic fields – Customize forms and data fields to your requirements
  • REST API & Web Services – Seamlessly integrate Znuny into your existing IT landscape
  • AI integration – Leverage artificial intelligence for automatic categorization and text analysis

Who is this documentation for?

Section titled “Who is this documentation for?”
Target audienceRecommended starting points
AgentsTicket basics – Ticket creation and editing
AdministratorsSystem administration – Configuration and maintenance
DevelopersPlugin development – Extensions and integrations

Quick Start

Section titled “Quick Start”
  1. Installation: Deploy Znuny using Docker or on a traditional server
  2. First login: Sign in as root@localhost with the setup password
  3. Basic configuration: Adjust system settings, queues, and users
  4. Create a ticket: Create a first test ticket to explore the interface

Key Concepts

Section titled “Key Concepts”

Tickets

Section titled “Tickets”

The heart of Znuny. Each ticket represents a customer inquiry, incident, or task with a unique ticket number, status, priority, and assigned agent.

Queues

Section titled “Queues”

Organizational units for tickets (e.g., Support, Sales, Technical). Tickets are sorted into queues and can be moved between them.

Dynamic Fields

Section titled “Dynamic Fields”

Additional data fields that you define yourself – for custom information like customer numbers, product versions, or internal codes.

Processes

Section titled “Processes”

Visually modeled workflows for complex procedures with defined activities, transitions, and conditions.

Next Steps

Section titled “Next Steps”