> For the complete documentation index, see [llms.txt](https://docs.flexy.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexy.bot/modules/discord/data-types/user.md).

# User

#### Description

Represents a user within the system, which can include information such as the user's name, unique identifier, and profile picture. This data type is used to manage and interact with individual users, whether for communication, identification, or personalization purposes.

#### Properties

* **ID**: The unique identifier of the user.
* **Name**: The username chosen by the user.
* **Avatar URL**: The URL to the user's profile picture. This property may be null if the user does not have a custom avatar.
* **Created at**: The date and time when the user's account was created.
* **Tag**: A mention tag that can be used to reference the user in messages (e.g., `<@userID>`).


---

# 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.flexy.bot/modules/discord/data-types/user.md?ask=<question>&goal=<endgoal>
```

`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.