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

# My Wallets

The **My Wallets** section gathers all wallets from every Destination (Groups, RayBots, Discord channels, Dedicated bots) into a single unified dashboard.\
Here you can manage, filter, and review your entire tracking setup in one place.

**Here you can:**

* ✨ **Filter wallets** by Destination, Chain, Status, Settings overrides, and Tags.
* 🔄 **Refresh balances** across supported networks.
* ⏱ **View the last activity** of each wallet.
* ✏️ **Edit names, statuses, and settings** for any wallet directly.
* 🔄 **Change Destination** — move one or multiple wallets from one bot or group to another.

{% hint style="info" %}
When using **Change Destination**, selected wallets are transferred to the new destination and automatically removed from the previous one.
{% endhint %}

> *🎥 Video example — Full walkthrough of the My Wallets dashboard in under 2 minutes*

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/ok87yj4ixp>" %}


---

# 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.raybot.app/start/web-app/web/my-wallets.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.