> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/integration/user-profiles.md). # User Profiles - [What is User Profile](https://docs.authgear.com/integration/user-profiles/user-profile.md) - [Access User Profiles](https://docs.authgear.com/integration/user-profiles/access-user-profiles.md): Learn how to access User Profiles - [Update User Profiles](https://docs.authgear.com/integration/user-profiles/update-user-profiles.md): Guide on the different ways you can modify the profiles of the users of your application. - [Profile Custom Attributes](https://docs.authgear.com/integration/user-profiles/profile-custom-attributes.md): Learn how to add custom attributes to user profiles and manage existing custom attributes - [Update user profile on sign-up using Hooks](https://docs.authgear.com/integration/user-profiles/update-user-profile-on-sign-up-using-hooks.md): Learn how to update a User profile's custom attributes on sign-up using Hooks - [Add custom fields to a JWT Access Token or ID Token](https://docs.authgear.com/integration/user-profiles/add-custom-fields-to-a-jwt-access-token.md): Learn how to add custom attributes to a JWT Access Token or ID Token using Authgear --- # 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.authgear.com/integration/user-profiles.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.