> For the complete documentation index, see [llms.txt](https://docs.thoth.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thoth.id/web-app/dashboard.md).

# My Names

Every name you manage, with its role and expiry, in one list.

**My names** lists every name your wallet **manages**. Open it from **My names** in the top bar (or the account menu on a phone), or go to **/dashboard**.

If your wallet isn't connected, the page asks you to connect instead of showing the list.

![My names with one name, owned and managed by this wallet and marked with a star as the primary name](https://2559695096-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8NQqK3W76Bj7LGhFgkFC%2Fuploads%2Fgit-blob-f8cc5007b2a78a5b586e6a744a5c32ddd07b6387%2Fmy-names.jpg?alt=media)

## The list

The header shows how many names your address manages, and a **Register a name** button that takes you to search.

Each row is one name. Click a row to open the name's [page](/web-app/domain-page.md).

| Column      | Meaning                                                                                                        |
| ----------- | -------------------------------------------------------------------------------------------------------------- |
| **Name**    | The name and its avatar. A **star** marks your [primary name](/web-app/domain-page/addresses.md#primary-name). |
| **Role**    | **Owner and manager**, or **Manager** if someone else owns it                                                  |
| **Expires** | The expiry date and how long is left, for example *in 2 years*                                                 |

The expiry turns **yellow** in the last 30 days and **red** once the name has expired. From 30 days before expiry, and through the renewal window, the row gets a **Renew** button. See [Renew a Name](/web-app/renew.md).

When at least one name needs renewing, a warning at the top says how many, and when an expired name will become available to anyone.

With 5 or more names, a **Filter your names** box appears above the list.

If you don't manage any name yet, the page says *You don't have a .htr name yet* and offers **Find a name**.

## Changes in progress

The list follows your transactions:

* A registration that's still confirming shows as a dimmed row, **Registering** with a timer.
* A name with a change in flight shows a pill such as **Renewal pending** or **Avatar pending**.

Both disappear on their own when the transaction confirms. If it fails, the row goes back to how it was, and the bell keeps the reason.

## Manager, not owner

The list shows names where you are the **manager**. On a name you registered yourself you're both, so it makes no difference.

They can differ: if you transfer ownership of a name but stay its manager, it keeps appearing here. If you hand the manager role to somebody else, it disappears from your list even if you still own it. See [Ownership](/web-app/domain-page/ownership.md) for what each role can do.


---

# 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.thoth.id/web-app/dashboard.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.