> 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/member.md). # Member #### Description Represents a member of a server (guild) in the system, combining user-specific details with server-specific attributes, such as nicknames and roles. This data type is used to manage and interact with users within the context of a server. #### Properties * **ID**: The unique identifier of the member. * **Name**: The display name of the member, which returns the member's nickname if set, otherwise the user's global name. * **Nickname**: The member's nickname within the server. This property may be null if no nickname is set. * **Avatar URL**: The URL to the member's avatar. If the member has a server-specific avatar, this URL will point to it; otherwise, it will default to the user's global avatar. * **Tag**: A mention tag that can be used to reference the member in messages (e.g., `<@memberID>`). * **Joined at**: The date and time when the member joined the server. * **User**: The underlying user object associated with this member. --- # 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/member.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.