> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/system-notifications-and-automatic-ticket-creation.md).

# System notifications & automatic ticket creation

This section explains how to manage and customise notifications within the platform. It includes setting up notification preferences to ensure relevant alerts are received, configuring in-app notifications for real-time updates, and automating ticket creation in systems such as Jira to streamline issue tracking and resolution. We will cover the following topics in this section:

1. [Notification Preferences](/getting-started/system-notifications-and-automatic-ticket-creation/notification-preferences.md): Setting up notification preferences for your BalkanID account on the tenant-level by administrators and on the user-level by each individual user.
2. [In-app Notifications](/getting-started/system-notifications-and-automatic-ticket-creation/in-app-notifications.md): Setting up notification streams to receive within the BalkanID application.
3. [Supported Ticketing Systems](/getting-started/system-notifications-and-automatic-ticket-creation/supported-ticketing-systems.md): Setting up automatic ticket creation systems on your environment to provision access to users when access requests are approved and de-provision access from users when access requests are approved or access reviews are denied.


---

# 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.balkan.id/getting-started/system-notifications-and-automatic-ticket-creation.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.