> 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/academy/eliona-as-a-ticketing-platform/guide-from-the-admin-perspective.md).
# Guide from the admin perspective
As an administrator, you are responsible for configuring and managing the ticketing system. To perform these tasks, you need either the system role «System admin» or «System owner». These roles grant you all the necessary permissions to set up and manage ticketing in Eliona.
## Create project
When working with a new Eliona instance, use the existing project for ticketing. If an Eliona instance already exists, you must first create a new project in the settings.[ ](/collection/english-v14/getting-started/1.-create-users-and-projects/create-a-project.md)[->Create project](/collection/english-v14/getting-started/1.-create-users-and-projects/create-a-project.md)
## Tags
Once the project is set up, create the required tags. These are used to show users only their own tickets and to filter and sort assets efficiently. At least one tag must be created for each customer. Additional tags help improve clarity and make it easier to search for assets and users. [>Tags](/collection/english-v14/documentation/tags.md)
Tags
## Users
Each customer receives an individual login or their own user account, and multiple if needed. For the service team, an individual user is also created for each employee. In addition, there is a general service user whose task is to distribute tickets to the right employees. If there is only one service employee, this mechanism is not needed. For better overview, the tags created earlier are assigned to the customer's users. [->Users](/collection/english-v14/documentation/users.md)
Users
## Roles
For the service employees, a special role is created that makes all tickets visible to everyone. Own tickets can be found using filters. If not all tickets should be visible to all service employees, additional roles must be created. The service employee role requires permissions to manage, write, and read tickets, as well as permissions to write and read assets. The required permissions can be adjusted depending on the application.
Each customer receives their own role, which only has access to their own tags. In principle, the customer only needs the permission to read and write tickets and to read assets. These permissions can be further adjusted depending on the requirements and existing dashboards. [->Roles](/collection/english-v14/documentation/roles.md)
Roles
## Assets
Service objects are created as assets. These can include individual devices or entire buildings. Depending on the assignment of permissions, the assets are recorded either exclusively by the administrator or also by the service employees. It is important that the assets are provided with the customer-specific tags so that they are assigned to the correct customer. All important information about the service object is entered in the asset. Additional fields can be added if needed via asset modelling to capture further information. [->Assets](/collection/english-v14/documentation/assets.md)
Asset modelling
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.buildings.ability.abb/collection/english-v14/academy/eliona-as-a-ticketing-platform/guide-from-the-admin-perspective.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.