> For the complete documentation index, see [llms.txt](https://lenfi.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://lenfi.gitbook.io/docs/lenfi-v1-protocol/lenfi-p2p-aada-v1/how-to-use-the-platform/menu/dashboard.md).

# Dashboard

<figure><img src="/files/YEJwXdpgKFBJXL42td4d" alt=""><figcaption></figcaption></figure>

The **Dashboard** tab is where users can see their loans and loan requests. All interactions are listed in spreadsheet style with several subcategories:

**Pending** - Only visible if there are pending transactions that are not on-chain yet.

**Deposits** - Here you can find the current status of your loans. You can claim your interest and loan or liquidate it.

**Loans -** The Loans tab shows a list of all user's loan requests. You can repay active loans or cancel loan requests that haven't been funded yet.

**Liquidated Loans -** The following tab displays all liquidated loans. You can find and withdraw collateral due for a claim.

**Archive** - The **Archive** tab keeps historical data about all loans and interactions with the Aada dApp.


---

# 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://lenfi.gitbook.io/docs/lenfi-v1-protocol/lenfi-p2p-aada-v1/how-to-use-the-platform/menu/dashboard.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.
