> 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/groups.md). # Groups How to use groups on Ledger Enterprise to manage several people at once in governance Rules. **Role: Administrators.** A group is a named set of people. Use a group in a Rule instead of naming individuals. ## Why groups matter Without groups, every Rule names people directly. When somebody joins or leaves, you have to edit every Rule that mentions them. Each edit is a separate approval cycle. With groups, you edit the group once. Every Rule that uses it follows. > **Note:** For a Workspace with more than a handful of Rules, this is the difference between a ten-minute change and a day of approvals. ## Create a group 1. Open **Groups** and create a group. 2. Give it a name. 3. Add the people. 4. Submit, then review on your device. Creating a group is a **Request**. It needs the approvals your Workspace admin Rule demands. The group does not exist until those approvals complete. A group needs at least one member. There is no maximum. Name groups after the **role they play**, not the people in them. "Treasury Approvers" survives a change of staff. "Anna and Tom" does not. ## Edit or delete a group Edit a group to add or remove people. This is also a governed Request, so it needs approval before it takes effect. Once approved, the change applies everywhere the group is used. > **Important:** Before you remove somebody, check which approval steps their group appears in. Removing a person can leave a step with fewer people than its quorum requires. Every Request waiting on that step then stalls. > > Plan the timing too. A group edit needs its own approval cycle, so it is not an instant fix when somebody leaves at short notice. ## Groups and quorum **A person counts once per approval step, however many of that step's groups they belong to.** If a step names two groups with a quorum of 2, and the same person is in both groups, that person provides **one** approval, not two. The step needs somebody else as well. When you set a quorum, count the **distinct people** in the step, not the sum of the group sizes. ## Related * [**Policies**](/help-center-v2/guides/governance/policies.md) * [**Creating and editing Accounts**](/help-center-v2/guides/accounts/creating-and-editing-accounts.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/groups.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.