> For the complete documentation index, see [llms.txt](https://docs.dextrabot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dextrabot.com/copy-trade/copytrade/asset-management.md).

# Asset Management

#### 🔄 Token Management (Include / Exclude Tokens)

<figure><img src="https://3477217969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaWiG6XtemfC9IwxonZpa%2Fuploads%2FrdF5g0xR8I3mUK5OlYsz%2Fimage.png?alt=media&amp;token=8a40b745-0ce5-46d1-8d11-6c5029bf304d" alt=""><figcaption><p>Include / Exclude Tokens</p></figcaption></figure>

The **Include/Exclude Token Setting** allows you to filter which tokens you want to actively copy trades for.

**How it Works:**

1. By default, **all tokens are included** for copy trading.
2. If a **new token** is listed or traded by the source wallet, it is also **included by default**.
3. You can choose to **exclude specific tokens** manually at any time.
4. These settings are **source wallet specific** — so each trader you follow can have a separate token filter.
5. Once you include or exclude a token, the system will respect that rule **until you manually change it**.

This provides better control over risk and exposure, allowing you to avoid tokens you do not want exposure to, or focus only on trusted coins.


---

# 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.dextrabot.com/copy-trade/copytrade/asset-management.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.
