> For the complete documentation index, see [llms.txt](https://docs.vena.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vena.finance/for-users/manage-position.md).
# Manage your position
The dapp's **Dashboard** is the central view for monitoring and adjusting an open position.
## Dashboard
The top of the dashboard summarises the whole position in three values:
* **Net worth** — total value of supplies minus debts.
* **Net APY** — the aggregate rate across all open positions, netting supply yield against borrow cost.
* **Health Factor** — the live safety margin on any borrow position.
Below, two panels:
* **Your Supplies** — each supplied asset with Balance, APY, a **Collateral** toggle, and **Supply** / **Withdraw** buttons per row.
* **Your Borrows** — each borrowed asset with Debt, APY, and **Borrow** / **Repay** buttons per row.
Action buttons open a modal; the dashboard does not expand rows inline.
## Monitoring your health factor
The health factor is visible at the top of the dashboard at all times. It updates in real time as prices move, as debts accrue interest, and as the user supplies, borrows, repays, or withdraws.
As the health factor falls:
* **Above 1.5** is a comfortable buffer. Normal market moves typically don't threaten it.
* **Between 1.0 and 1.5** is a warning zone. A further drop in collateral price or rise in debt price can push the position into liquidation. Top up collateral or partially repay debt.
* **At or below 1.0** is liquidatable. Liquidators may close the position at any moment.
Vena does not push notifications. Users can set alerts with off-chain tools — portfolio trackers or custom scripts reading health factor from the protocol's data provider.
## Adjusting collateral
Three actions move the health factor:
* **Supply more of an existing collateral asset.** Raises collateral value, raises health factor.
* **Repay part of the debt.** Lowers debt, raises health factor.
* **Toggle an asset off as collateral.** Removes its collateral contribution, lowers health factor. The dapp blocks the toggle if it would push the health factor below 1.
Withdrawing a supplied asset that's in use as collateral has the same effect as toggling it off, for the withdrawn portion.
## E-Mode
E-Mode is enabled at launch. It lets a position unlock higher LTV by restricting collateral and debt to a set of assets with correlated prices — for example, a group of stablecoins.
At mainnet, one E-Mode category is active: **Stablecoins**. The launch use case is supplying sUSDnr as collateral to borrow USDnr.
Each reserve page shows an **E-Mode Info** section for assets that belong to a category. The category is enabled from the dashboard:
1. On the dashboard, enable E-Mode.
2. Select the category that matches the position.
3. Confirm the transaction.
While in a given E-Mode category, a position can only borrow assets within that category, and only the category's collateral assets count toward the health factor. Switching categories or disabling E-Mode requires the current position to remain healthy under the new (lower) LTV.
## Adding or removing assets
A position can hold multiple supplies and multiple borrows at once. To add:
* **Add a supply**: use the **Supply** flow for a new asset.
* **Add a borrow**: use the **Borrow** flow for a new asset, subject to available credit.
To remove a supply, withdraw it. To remove a borrow, repay it in full.
---
# 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.vena.finance/for-users/manage-position.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.
