> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/user-profile-manage.md).
# Managing your user profile
The **User Profile** page displays a summary of information about your Textual account.
From the user profile page, you can copy your organization identifier, configure a team name, and manage your Textual API keys. For more information about managing your Textual API keys, go to [Creating and revoking Textual API keys](/textual/tonic-textual-api/textual-api-keys.md).
## Displaying the User Profile page
To display the **User Profile** page:
1. Click the user icon at the bottom of the navigation menu.
2. In the user menu, click **User Profile**.
Textual user menu
## Copying your organization identifier
The profile summary includes the identifier of your organization in Textual.
To copy the identifier, click the copy icon.
## Adding a team name
From the **User Profile** page, you can specify a team name. For example, you might use the team name field to identify a specific department or project that you belong to.
To add a team name, type the name in the field.
---
# 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.tonic.ai/textual/user-profile-manage.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.
