> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.4/user-administration/user-admin-edit-user-info.md).

# Edit User Information

You can make changes to user information.

You can change the username, the display name and the tenants and role on the respective tenant for a user.

You cannot change the password for a user.

You must be an administrator to perform this operation.

To edit the user-related information for a user, follow the steps given below.

1. Log in to Clarity.
2. Click Tenants and Users in the left panel.
3. Click the Users tab.
4. Select the check box for the user to edit.
5. Click Edit User on the toolbar seen above the list of users.
6. Make the required changes.
7. Click Save.

The changes are saved for the user.


---

# 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.platform9.com/managed-openstack/5.4/user-administration/user-admin-edit-user-info.md?ask=<question>&goal=<user_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.