> 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/rollen/warum-sind-rollen-so-wichtig.md). # Why are roles so important? Since the introduction of ACL, it is particularly important to assign newly created users to a project immediately. A user without an assigned project cannot see anything in eliona and cannot perform any actions. {% hint style="info" %} Learn [-> here](/collection/english-v14/documentation/benutzer/einen-nutzer-einem-projekt-zuweisen.md) how to assign a user to a project. {% endhint %} ### Why is that? If a user is not assigned to any project, then *Users* they also have no project role. If no project role applies to a user, only the system role settings apply. The default system role of every new user is "System-User". This role has no read permissions whatsoever. Therefore, a user with the system role "System-User" cannot see any menu items and cannot perform any actions.

Fig. 1 – This is what a user sees who is not assigned to any project. The entire menu bar is empty and no actions can be performed

--- # 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/rollen/warum-sind-rollen-so-wichtig.md?ask=&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.