> 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/english-v14/documentation/tickets/rechte-fuer-tickets-und-tasks.md).

# Rights for tickets and tasks

Ticket permissions are granted via the [-> project roles](/collection/english-v14/documentation/rollen/projektrollen.md) assigned. In addition, the assignee, creator and owner can perform certain actions. An action is only available if both the project role and the business status rules allow it.

## Areas and permission levels

The **ticket list view**, the **ticket details** and the **tasks** are authorized separately. For ticket details and tasks, the levels **Read**, **Write** and **Manage (Ticket Manage)** are available.

<table><thead><tr><th width="217.2000732421875">Area or level</th><th>Options</th></tr></thead><tbody><tr><td><strong>ticket list view</strong></td><td>Controls whether the ticket overview may be displayed. The visible tickets are additionally restricted by asset tags and Expert Mode.</td></tr><tr><td><strong>Read</strong></td><td>Display details, comments, timeline and work log of the authorized area. If the ticket time is adjusted manually, only the adjusted value is shown.</td></tr><tr><td><strong>Write</strong></td><td>Create and edit content in the authorized area. Write permissions require read permissions.</td></tr><tr><td><strong>Manage (Ticket Manage)</strong></td><td>Includes reading and writing as well as privileged administrative actions. Confirmed administrative actions are deleting one's own tickets and changing task status regardless of whether the user is the assignee or creator.</td></tr></tbody></table>

The universal switch **Tickets** enables or disables all ticket permissions of the project role.

## Who may perform which action?

<table data-header-hidden data-search="false"><thead><tr><th width="226.159912109375">Action</th><th>Required condition</th></tr></thead><tbody><tr><td>Show ticket list</td><td>Access to the <strong>ticket list view</strong> as well as access according to project role, tags and Expert Mode.</td></tr><tr><td>Show ticket details</td><td><strong>Read</strong> for ticket details.</td></tr><tr><td>Show task details</td><td><strong>Read</strong> for tasks.</td></tr><tr><td>Create or edit ticket</td><td><strong>Write</strong> or <strong>Manage</strong> for ticket details as well as access to the respective object.</td></tr><tr><td>Create or edit task</td><td><strong>Write</strong> or <strong>Manage</strong> for tasks as well as access to the respective object.</td></tr><tr><td>Delete ticket</td><td>Ticket owner with <strong>Manage (Ticket Manage)</strong> for ticket details.</td></tr><tr><td>Accept, complete or cancel task</td><td>task assignee, task creator, assignee or creator of the parent ticket, or user with <strong>Manage (Ticket Manage)</strong> for tasks.</td></tr><tr><td>Close ticket</td><td>ticket assignee with the corresponding write or administrative access; additionally, at least one task must exist and all tasks must be completed.</td></tr><tr><td>Cancel ticket</td><td>ticket assignee with the corresponding write or administrative access.</td></tr><tr><td>Complete task</td><td>In addition to the permission, the task must have been started and a time effort entered.</td></tr><tr><td>Adjust time manually</td><td>The action must be available to the user in the ticket or task details. Users with read-only access see only the overridden value when the ticket time has been adjusted.</td></tr></tbody></table>

{% hint style="info" %}
Since database version v14.2.7, the creator of a task may also change its status. Previously, only the assignee could do this.

Since database version v14.2.9, the assignee and the creator of the parent ticket may additionally accept, complete or cancel the task. Unauthorized API calls are rejected with HTTP 403 instead of returning a successful response without a status change.
{% endhint %}

## Access via tags and Expert Mode

The asset and tag permissions of a project role influence which tickets are visible. With activated **Expert Mode** tickets can be visible for assets to which the user has no access; the asset name then remains hidden. [-> Examples for Expert Mode](/collection/english-v14/documentation/rollen/projektrollen.md#c-der-expert-mode)


---

# 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/english-v14/documentation/tickets/rechte-fuer-tickets-und-tasks.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.