---
title: Set up the Ticket Center
description: >-
  Turn on Ticket Center and set up the catch-all assignee, categories,
  priorities with response targets, statuses, feedback and support seats.
icon: settings
sidebar:
  order: 6
  icon: settings
---

**Ticket Center settings** are where an admin turns the feature into a working help desk: categories, priorities, statuses, feedback, the catch-all assignee and support seats. Open them under **Settings → Management → Ticket Center**.

:::info
You need **Configure Ticket Center**. First turn on **Ticket Center** under **Settings → Configuration Wizard → Features**. When it is off, Ticket Center is hidden from the sidebar.
:::

## Why it matters

Routing only works as well as the setup behind it. Clear categories send tickets to the right team, priorities set honest response targets, and a catch-all assignee makes sure no ticket is left without an owner.

## Before you start

| Requirement | Detail |
|---|---|
| Permission | **Configure Ticket Center** |
| Feature | **Ticket Center** turned on in **Settings → Configuration Wizard → Features** |
| Staff | At least one person with **Edit tickets** or **Configure Ticket Center**. Without staff, **Add category** is disabled. |

## How to turn on Ticket Center

1. Open **Settings → Configuration Wizard** and click the **Features** tab.

2. Find **Ticket Center** (search with "Search features…" if needed) and switch it on.

3. Give the Ticket Center permissions to the right roles. See [Ticket Center permissions](/docs/fuxam-web/base/ticket-center/ticket-center-permissions).

## What the settings page contains

The page has these sections, top to bottom: **Support seats**, **Feedback**, **Ticket Triage**, **Categories**, **Priorities** and **Statuses**. Changes to **Feedback**, the catch-all assignee and category assignees collect in a bar at the bottom; click **Save** to apply them. Categories, priorities and statuses open in a side panel and save on their own.

Each time the page opens, Fuxam checks for the starter catalog and adds any entry that is missing by name: the categories **Bug**, **Feature Request** and **Questions**, and the priorities **Urgent** (3 hours), **High** (2 days), **Mid** (3 days) and **Low** (5 days). Entries that already exist are not changed.

## How to set the catch-all assignee

1. In **Ticket Triage**, choose a person as **Catch-all assignee** (fallback person).

2. Click **Save** in the bar at the bottom.

This person gets the **Other** category and every ticket no more specific rule matches. Until you set one, **Other** can't be created and requesters see "Ticket Center routing is not configured yet."

## How to add a category

1. In **Categories**, click **Add category**.

2. Enter a **Name** (for example "Access"). It is shown when people create a ticket.

3. Optional: add a **Description** (up to 500 characters) so people know when to pick it, plus an **Icon** and a **Color**.

4. Optional: choose a default **Assignee**. New tickets in this category go to this person.

5. Click **Create**. You see **Category created**.

### Edit, manage access or delete a category

Open the row's actions menu:

- **Edit** changes name, description, icon, color or assignee.
- **Manage access** sets **Responsible** (for example study coaches or IT) and **Deputies** (cover for holidays). Each list holds up to 50 people, and one person can't be in both. Everyone named here sees the category's tickets in the queue and can be assigned.
- **Delete** removes the category from routing. Existing tickets keep its name as free text, and new tickets can no longer choose it. **Other** can't be deleted.

## How to add a priority

1. In **Priorities**, click **Add priority**.

2. Enter a **Name** (up to 100 characters) and a **Description** (required, up to 500). The description tells requesters when to choose it.

3. Pick a **Color**.

4. Set the **Response target**: a number and a unit (**Minutes**, **Hours**, **Days**), between 1 minute and 365 days. It counts running time, not business hours.

5. Click **Create**. You see **Priority created**.

The response target measures time to the first public staff reply. Editing or deleting a priority doesn't change existing tickets: they keep the target they got.

## How to add a status

1. In **Statuses**, click **Add status**.

2. Enter a **Name** (up to 60 characters).

3. Choose a **Category**: **Not started**, **In progress** or **Finished**, and a **Color**.

4. Save. You see **Status added**.

You can have up to 50 statuses, including the defaults **Open**, **In progress** and **Resolved**. Defaults can be renamed and recolored, but not deleted, and their category stays fixed. To delete a status that tickets use, pick a status under **Move tickets to** first.

## Feedback and support seats

- **Feedback**: switch it on to "Let students submit feedback as well as tickets." The **Feedback** tab then appears on the **Support** page and in Ticket Center. Click **Save**.
- **Support seats**: shows how many support seats are used, for example "3 of 5 support seats used". It turns red when the quota is exceeded. It only shows usage and blocks nothing.

## Common pitfalls

| Pitfall | What happens | What to do |
|---|---|---|
| Leaving without **Save** | Feedback and assignee changes are lost | Click **Save** in the bottom bar. |
| No catch-all assignee | **Other** is missing and requesters can't send tickets that fit nowhere | Set it first. |
| Same name twice | "A category with this name already exists." (same for priorities and statuses) | Choose a unique name. |
| Deleting a used status | Deletion asks where the tickets go | Pick a target under **Move tickets to**. |
| Too many categories | Requesters pick the wrong one | Keep a short list with clear descriptions. |
| Deleting or renaming a starter category or priority | It is added again the next time the settings page opens | Keep the starter entries and change their description, icon, color or target instead. |

## FAQ

**Can I rename Open, In progress and Resolved?**

Yes, you can rename them and change their color. You can't delete them or move them to another status group.

**Do new priorities change running tickets?**

No. Each ticket keeps the response target it had when the priority was set.

**Why did a deleted category come back?**

**Bug**, **Feature Request**, **Questions** and the priorities **Urgent**, **High**, **Mid** and **Low** are the starter catalog. Fuxam adds any of them that are missing each time the settings page opens.

**Does exceeding support seats stop tickets?**

No. The display turns red, but nothing is blocked.

## Related pages

**[Set up triage and routing](/docs/fuxam-web/base/ticket-center/set-up-triage-and-routing)**

Category people, distribution and triage rules.

**[Ticket Center permissions](/docs/fuxam-web/base/ticket-center/ticket-center-permissions)**

Give roles the right access.

**[Work on a ticket](/docs/fuxam-web/base/ticket-center/work-on-a-ticket)**

How statuses and priorities are used.

**[Ticket Center](/docs/fuxam-web/base/ticket-center)**

Back to the section overview.

