> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/workspaces.md). # Workspaces Understand custody, capital, settings, and workspace scope. ## Workspaces A workspace is where your capital lives. It is a Safe smart account, connected to your custodian. Every transaction Brava prepares executes from it, and none of them execute without your custodian's signature. Brava holds no keys. ### Why the workspace exists The workspace is the boundary between your custodian and Brava, and it exists so that boundary has a precise location. Your custodian's vault holds your capital and your keys. Brava needs an account it can plan transactions *from* — one whose positions it can read, whose balances it can size against, and whose history it can report on. The workspace is that account. It is controlled by your custodian, not by Brava. This also gives you a unit of separation. Permissions, strategies, capital and history all belong to the workspace. An organisation running operating capital and reserves under different authorities runs two workspaces, and the separation is structural rather than a matter of care. ### The workspace address A workspace has one address, and it is the same address on every chain it operates on. This is a property of how Safe accounts are deployed, not a coincidence, and it is useful: capital on Base and capital on Arbitrum sit at the same address, so reconciling across chains does not mean tracking several identities. In transaction details, the workspace is named rather than left as a raw address, with the address alongside it. ### Connecting a custodian Brava supports **Utila** and **Fireblocks**. Each has its own step-by-step guide. Whichever you use, the shape is the same: the custodian's vault funds the workspace and receives its withdrawals, and the custodian retains signing authority throughout. Brava is granted the ability to prepare transactions and nothing else. ### The three states of capital Capital in a workspace is always in one of three states, and the Portfolio screen shows the split: **Cash holdings.** In the workspace, deployed nowhere. This is what allocations spend and where redemptions return. It earns nothing. **Capital allocated.** Working inside strategies. **Capital in transit.** Between chains, mid-bridge. Cross-chain allocations pass through this state for a few minutes while the bridge settles. Knowing these three accounts for capital that appears to have vanished. Funds that have left your custody wallet but are not in a strategy are cash holdings; funds that are in neither are almost certainly in transit. ### Running more than one There is no limit, and most organisations end up with several: by mandate, by client, by authority, or by risk appetite. What does not carry across workspaces: * **Capital.** There is no transfer between workspaces inside Brava. Moving capital between them means withdrawing to your custody wallet and depositing into the other. * **Permissions.** A person may be an Owner of one and a Viewer of another. * **Strategies and history.** Both are scoped to the workspace that made them. Switching workspaces in the header changes all of the above at once, including what you are permitted to do. ### Settings Workspace settings cover the name, the connected custodian, team members and their permissions, and notification preferences. Changing settings does not move capital. Removing a member removes their access and nothing else. --- # 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://docs.brava.finance/platform/workspaces.md?ask=&goal= ``` `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.