Portfolio

View your workspace’s capital, performance, and activity.

Portfolio

Everything your workspace holds, in one view. This is the screen you land on.

New name. This was the Dashboard. "Portfolio" now means the whole workspace. A single set of holdings is a Strategy.

What this screen is for

A strategy tells you how one set of positions is doing. Portfolio tells you where all of your capital is — deployed, idle, or moving — and lets you bring capital in and out of the workspace.

If you are answering "how is that position performing", go to the strategy. If you are answering "where is my money", you are on the right screen.

Balance, and its three parts

Balance is everything the workspace holds, wherever it sits. Beneath it, that figure is split three ways, and the split is the useful part:

Cash holdings — in the workspace, deployed nowhere. This is what an allocation spends. Capital sits here after a deposit and after a redemption, and earns nothing while it does.

Capital allocated — working inside your strategies.

Capital in transit — capital that has left one chain and not yet arrived on another. A cross-chain allocation passes through this state while the bridge settles, typically for a few minutes. It is neither cash nor allocated, and it is not lost.

Cash holdings expands to show which stablecoin sits on which chain. An allocation spends from a specific token on a specific chain, so a workspace with plenty of cash overall can still be unable to fund a particular allocation without bridging.

Gross APY and earnings

Gross APY is the blended rate across everything allocated, weighted by size. Expand it for the components. It is gross — it does not net off the cost of getting in or out.

Earnings shows total, today, and month to date.

Earnings are built from indexed history, a daily record Brava accumulates after the fact. Balance is read live from the chain; earnings are not. A workspace funded this week has no history to compute from and will show an em dash.

Empty is not broken. If your balance is correct and earnings are blank, the position is fine and the record is young.

The rest of the screen

Breakdown — exposure by project, chain, token or category.

Allocation flow — where capital has moved and where it has settled.

APY movement and Performance — how the rate and the value have moved over time. Both are built from indexed history and share its warm-up.

Rewards — unclaimed rewards, with claim and export.

Strategies, Holdings and Transactions — the same records as their own screens, scoped to this workspace.

Moving capital in and out

Actions opens two tabs.

Action	What moves
Deposit	Your custody wallet into the workspace
Withdraw	The workspace back to your custody wallet

These cross the boundary between your custodian and Brava. That is what makes them different from allocating and redeeming, which move capital already inside the workspace and live on a strategy.

Both state the amount, the wallet at each end, and the transaction fee before you commit. Both require your custodian's signature.

A deposit does not deploy anything. It arrives as cash holdings. Putting it to work is a separate, explicit act on a strategy.

Choosing a token

The token picker shows what is available and where. For a deposit that is your custody wallet's balance; for a withdrawal it is the workspace's cash holdings. Tokens you hold none of are listed but cannot be selected.

Pending agent actions

Where an agent has prepared a transaction, it appears here and waits.

An agent proposes. It does not sign. Nothing moves until you approve it and your custodian signs it. A pending action is a plan with your name against it, and it stays a plan until you act.

Switching workspaces

The workspace selector sits in the header.

Capital, strategies, permissions and history belong to the workspace, not to you. Switching changes all of it — including what you are permitted to do, since roles are granted per workspace.

When data is unavailable

Where Brava cannot read your on-chain positions, affected figures show as unavailable rather than as zero, and actions that depend on them are disabled.

This is deliberate. A balance Brava cannot verify is not reported as a number, and Brava will not prepare a transaction sized against figures it does not trust.