> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/users/user-details.md).

# User Details

When you click an individual user, it will display general information about them like the name and phone number associated with their account, the current app version that they're using, the device they're using the app on, the date that they joined the current system, etc. On the upper right-hand side of the screen, you also have the option to [ban ](https://documentation.movatic.co/admin-site/users/banning-a-user)a user by clicking the **Ban** button, which prevents them from being able to start rentals in the current system.

**User Memberships** displays what specific memberships a user is associated with that belong to this system, with the option to manually [add memberships](https://documentation.movatic.co/admin-site/memberships/creating-a-membership) for them.<br>

<figure><img src="https://3693766063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxId4PbGGTlBib03KztrO%2Fuploads%2Fv8NHolpaRRyqCRQ83Lmr%2Fimage.png?alt=media&amp;token=830d45fc-7824-4330-86b0-94bb8bb812e5" alt=""><figcaption><p>Example of User Information</p></figcaption></figure>

##


---

# 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://documentation.movatic.co/admin-site/users/user-details.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.
