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

# Asset Management

The **Portfolio** dashboard provides a unified view of your entire liquidity engine. From here, you can monitor performance, collect earnings, and adjust your active deployment.

## Dashboard Metrics

Once connected, your portfolio tracks several key indicators:

| Header             | Metric                                                   |
| ------------------ | -------------------------------------------------------- |
| **Total Value**    | The current USD value of all pooled assets.              |
| **Unclaimed Fees** | Revenue generated from trading activity in your pools.   |
| **Status**         | Indicates if your V3 positions are currently "In Range." |

## Management Actions

{% stepper %}
{% step %}

### Fee Collection

Revenue is not automatically reinvested in V3 positions. You must manually claim your accumulated fees from the Portfolio interface.
{% endstep %}

{% step %}

### Range Rebalancing

If a position becomes **Inactive** (Out of Range), it will stop earning fees. To resume earning:

* Remove the liquidity from the inactive position.
* Deploy into a new range centered around the current market price.
  {% endstep %}

{% step %}

### Liquidity Withdrawal

You can exit any position at any time. When you remove liquidity, you will receive your tokens proportional to the current pool ratio, plus all accrued fees.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Gas Efficiency:** Because Flux is built on Fluent, managing positions and claiming fees is high-speed and cost-effective, allowing for more frequent rebalancing strategies.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fluxflow.gitbook.io/docs/tutorials/asset-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.