> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/service-desk/ticket-settings.md).

# Ticket Settings

## Open Ticket Settings

To open the **Ticket Settings**, follow these steps:

1. **Navigate to the ticket view:** In the *sidebar*, click on **Tickets**.
2. **Open settings:** In the top bar of the ticket view, you will see a **gear icon** <img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FMLaXX9P158E7VhzagJVD%2Fimage.png?alt=media&#x26;token=b8b06766-5f61-4a3d-a3b7-93f6c6139296" alt="" data-size="line">.\
   ▷ Click on this icon to open the *Ticket Settings* window.

## Configure Ticket Settings

The **Ticket Settings** window in *Eliona* offers various options to configure notifications and default assignments for tickets. The individual elements are structured as follows:

<figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FAjt7l7HczNlhMbg9Efgg%2FTickets%20Setting%20(1).png?alt=media&#x26;token=514b87fe-7cb0-4a84-8ee0-66071dbd0160" alt=""><figcaption></figcaption></figure>

* **Activate email notifications \[A]:** Turn on this option to automatically notify the assigned person by email as soon as a new ticket is created.
* **Notification from priority level \[B]:** Select the minimum priority from which notifications should be sent (e.g., "Medium" or higher).
* **Default assignee \[C]:** Define a default person who is automatically entered as the assignee for new tickets.
* **Delete default assignee \[D]:** Remove the defined default assignee by clicking on this button.
* **Save changes \[E]:** Save all changes you have made or cancel the process to leave the settings unchanged.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/platform/service-desk/ticket-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.