> 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/systems-and-projects.md).

# Systems and projects

## Overview&#x20;

### System

<figure><img src="/files/31bb9678d82247eaeb6444535ef356e39e043a6a" alt=""><figcaption><p>Using the log-in window, you log in to a system</p></figcaption></figure>

When you log in to eliona with your access data, you log in to the system.

### Projects

Within a system, there is one or more projects.&#x20;

## Who can create projects?

Projects can be created by users who have a [-> system role](/collection/english-v14/documentation/roles.md#systemrollen) assigned that has write permissions for "Projects"

For each project, users can be granted their own permissions. The users of all projects are visible in the system settings.

## How should projects be structured?

Eliona can be customized down to the smallest detail to your individual requirements. This also applies to the project structure. There are no rules regarding the scope of a project.&#x20;

For example: You have several infrastructures distributed worldwide. \
You could now create a separate project for each infrastructure.&#x20;

You could also create projects by geographic region, and create separate projects for Europe, Asia, etc., and sort all corresponding infrastructures into the respective projects. &#x20;

But you could also create a single project and sort all your infrastructures into it.&#x20;

None of these solutions is right or wrong.&#x20;


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/systems-and-projects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
