> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-guide/operate/overview.md).
# Overview
Read the state of an account in one screen: balance, protected roles, top holdings and anything waiting on you.
**Where:** Account → Overview
Overview is the landing page of every account. Needs attention (1) lists what is still unconfigured or waiting on someone.
## The cards
### Total balance
The native balance of the account on its network, with the **Smart account address** underneath. Two shortcuts sit on the card:
* **Receive** opens the [Receive assets](/platform-guide/operate/assets.md#receive-assets) drawer with a QR code and a copy button.
* **Send** opens [New request](/platform-guide/operate/new-request.md) with the Transfer type already chosen.
A new account shows "No balance yet. Receive assets to fund this account." Fund it from any wallet on the same network before you try a transfer.
### Contract security
The three protected roles and the time lock, read live from the chain: **Owner**, **Recovery**, **Time-lock** and **Broadcasters**. The card header summarises the state:
| Header | Meaning |
| ------------------------- | -------------------------------------------------------------------------- |
| **Security configured** | Owner, recovery, time lock and at least one broadcaster are all set. |
| **Recovery not set** | No recovery address. The account has no fallback if the owner key is lost. |
| **Setup needs attention** | Something else is missing or inconsistent. |
**View security** opens [Policies → Security](/platform-guide/policies/security.md), where an owner can fix it.
### Holdings
The top five assets by balance with an inline **Send** on each row. **View all** opens [Assets](/platform-guide/operate/assets.md). Token rows only appear for allowlisted tokens.
### Needs attention
Open requests on this account. Each row opens the request in [Approvals](/platform-guide/operate/approvals.md). When nothing is open the card reads "All caught up" or "No open requests on this account."
## Setup gap messages
While an account is still being configured, Overview shows counters such as:
* "N actions need registration"
* "N role items incomplete"
* "N setup items need attention"
Each one ends with **Fix in Administration**, which takes you to the relevant Policies or On-chain access page. These messages are only actionable by the owner. If you are a member, tell your admin what you see; the [Help](/platform-guide/help.md) page lists the same items as a checklist with a setup percentage.
A freshly deployed account is a **Vault**: it can receive, but nothing can leave it yet. That is a finished state, not an error. See [what a new account already has](/platform-guide/policies/actions.md#what-a-new-account-already-has).
## What you see without a wallet
Everything on Overview is readable with no wallet connected. **Receive** works too. **Send** and the rows in **Needs attention** need a connected wallet with the right role, and the footer says "Connect a wallet to sign. Reads still work."
## Related
* [Deploy an account](/platform-guide/accounts/deploy.md)
---
# 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.bloxchain.app/platform-guide/operate/overview.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.
