> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-2-system-administrator-manual/menu_-_administration__user_management/administrate_existing_users.md).
# Administrate existing users
To administrate an existing user, select the “Administrate users” tab on top of right part of the window.
The list of all the system users will be shown in the left part of the window.
Select “Show inactivated users” checkbox in the left bottom corner to include inactive users in the list.
Select a user you want to modify from the list. The user’s detail will be displayed in the right part of the window.
## User details modification
User Henry Moray was selected in the example.
Make the changes, click “Update user” and sign.
## User’s password change
It may be necessary to modify user’s password. A typical reason for it is when the account is blocked due to multiple login attempts using an incorrect password.
To change the user password use “Change password” button, that will open the dialog shown below.
Enter the new password, click OK and sign.
After the change, the user with a modified password will be forced to change the password again at the first login.
---
# 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://help.boomerang3.com/boomerang-2-system-administrator-manual/menu_-_administration__user_management/administrate_existing_users.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.