> 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/mandatory-base/platform-core/workspace-and-identity/users/change-a-users-role.md).
# Change a User's Role
## Change a Role
As explained in the previous chapter, a user receives a role when they are assigned to a tenant.
You can adjust that role afterward.
Fig. 1 – Customizing the role
1. Click on **Engineering \[A]**
2. Make sure the **Tenants** tab **\[B]** is selected
3. Click on the user whose role you want to adjust **\[C]**
▷ The tenant settings open
▷ In **\[D]**, you can see all users assigned to this tenant
4. For the user whose role you want to adjust, click on **\[E]**
▷ The **Edit user** window **\[F]** appears
5. In **\[G]**, select the role you want to assign to this user.
6. Click on **Save \[H]**
{% hint style="info" %}
**Why can't I adjust the role in the user settings?**
Users can have different roles in different tenants. Therefore, you set which role a user has in this tenant in the respective tenant settings.
[-> Learn more about roles](/collection/mandatory-base/platform-core/workspace-and-identity/roles.md)
{% endhint %}
---
# 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/mandatory-base/platform-core/workspace-and-identity/users/change-a-users-role.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.
