> 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/administration/governance/portfolios.md). # Portfolios How to group Accounts into Portfolios on Ledger Enterprise, and give Operators 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/administration/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 are Operators. A Portfolio gives them read access to its Accounts, and nothing more. It does not remove rights: an Operator named in the Rules of an Account can still act on that Account. 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 among active Portfolios, with up to 45 ASCII characters. 3. Select the Accounts. 4. Select the **Read-only users**, if any. Only active Operators who are not suspended are listed. 5. Select **Create portfolio**. Portfolios apply immediately. A Portfolio change is **not** a governed Request, so it needs no approval and no device. Policies and Whitelists, in contrast, go through Requests. Through the API, a Portfolio name can have up to 120 characters. > **Note:** Because there is no approval step, a Portfolio change takes effect as soon as you save it. Check the read-only users before you select **Create portfolio** or **Save changes**. ### 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. Select **Save changes** to apply the edit. Master Administrators can also link Portfolios from other places: * On the Accounts list, the **Link portfolios** action on an Account row. * On the **Account info** tab of an active Account, **Link portfolio** or **Edit portfolios**. * On the Users list, the **Link portfolios** action on an Operator row. * In the Account creation form, the **Portfolios** field. This field cannot be changed when you edit the Account. The first three open the same **Link portfolios** dialog, for one Account or one Operator: * The field shows the Portfolios that the Account or Operator belongs to now. * Add Portfolios to the field, or remove them from it. One edit can do both. * **Save** applies all the changes at once. It is available only after a change. * **Cancel** discards the changes. If the Portfolio you need does not exist, select **Create a new one** in the dialog. It opens the Portfolio creation form. **Delete portfolio** asks for confirmation. The Portfolio then becomes inactive, and it no longer appears in the Portfolios list. It is removed 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 access it granted go away. > **Warning:** A deleted Portfolio removes the read access it granted, immediately. Access from the Rules of an Account or from another Portfolio stays. There is no approval step to catch a mistake. ## Related * [**Policies**](/help-center-v2/administration/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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.enterprise.ledger.com/help-center-v2/administration/governance/portfolios.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.