> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/guides/governance/portfolios.md).

# Portfolios

How to group Accounts into Portfolios on Ledger Enterprise, and give people read-only visibility of them.

**Role: Master Administrators only.**

A Portfolio groups Accounts together. Use Portfolios to organize a Workspace by client, fund, desk, or entity.

> **Note:** Only Master Administrators can create or edit Portfolios. Other Administrators can see them but cannot change them. If you need a Portfolio changed, ask a Master Administrator.

> **Important:** A Portfolio does **not** control what anyone can do. It organizes Accounts and grants read-only visibility. Governance stays with Policies and Account Rules. See [**Policies**](/help-center-v2/guides/governance/policies.md).

## What a Portfolio gives you

|                                              |        |
| -------------------------------------------- | ------ |
| Groups Accounts under a name                 | Yes    |
| Grants read-only access to those Accounts    | Yes    |
| Controls who can send, approve, or configure | **No** |

Read-only users see the Accounts in the Portfolio. They cannot act on them.

This is useful for people who need to watch rather than operate: a finance team reconciling balances, a client relationship manager, an auditor.

## Create a Portfolio

1. Open **Portfolios** and select **Create portfolio**.
2. Enter a name. It must be unique in the Workspace, up to 120 characters.
3. Select the Accounts.
4. Select the read-only users, if any.
5. Submit.

Portfolios apply immediately. Unlike Policies and Whitelists, creating one is **not** a governed Request, so it needs no approval and no device.

> **Note:** Because there is no approval step, a Portfolio change takes effect as soon as you save it. Check the read-only user list before you submit.

### Token Accounts

When you add an Account that has token Accounts beneath it, you can include those too. The form tells you how many there are.

Decide deliberately. A Portfolio meant for balance reporting usually wants the token Accounts. A Portfolio meant to group main Accounts by client may not.

## Edit or delete a Portfolio

Edit a Portfolio to change its name, its Accounts, or its read-only users.

Deleting a Portfolio removes it from every Account and user linked to it. **The Accounts themselves are not affected**, and nothing is lost from them. Only the grouping and the read-only visibility go away.

> **Warning:** Deleting a Portfolio removes read-only access for everyone who had it through that Portfolio. They lose sight of those Accounts immediately. There is no approval step to catch a mistake.

## Related

* [**Policies**](/help-center-v2/guides/governance/policies.md)
* [**Finding Accounts and balances**](/help-center-v2/guides/accounts/finding-accounts-and-balances.md)
* [**How governance works**](/help-center-v2/concepts/how-governance-works.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 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://help.enterprise.ledger.com/help-center-v2/guides/governance/portfolios.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.