> 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/roles/why-are-roles-so-important.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/users/assign-a-user-to-a-project.md) how to assign a user to a project. {% endhint %} ### Why is that? If a user is not assigned to any project, then for this user *Users* no project role applies either. If no project role applies to a user, only the settings of the system role apply. The default system role of every new user is "System-User". This role has no read permissions at all. 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 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/roles/why-are-roles-so-important.md?ask=&goal= ``` `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.