LedgerOS
Open LedgerOS
Knowledge HubClients & contactsClient groups
Clients & contacts

Client groups

Tie related entities together so a family or a business group behaves as one relationship.

4 min readUpdated July 24, 2026

A group joins several client records into one relationship. The Henderson family with three entities and a trust is one group; a holding company with four operating subsidiaries is another.

Groups exist because work, documents, and requests routinely span entities, while the records themselves have to stay separate for filing.

Where to find it

ClientsGroups

Create a group

From the Groups page

  1. Click New group.
  2. Enter a Group name — for example, Henderson Group.
  3. Choose a Type.
  4. Create it. You'll add entities on the next screen.

From a client you're already looking at

Use Add to group on the client. You can pick an existing group or create one on the spot, and the client you started from becomes the group's primary entity.

Group types

Three types: Family, Business group, and Mixed.

Pick the one that describes the relationship. A married couple with a rental LLC is Mixed; four subsidiaries under a holdco are a Business group. The type is descriptive — it's there so that a group's nature is obvious at a glance and so groups can be told apart in filters.

Adding entities

Once a group exists, add clients to it from the group's own page. Each member keeps its own record, its own jobs, and its own documents. The group is a layer over the top, not a merge.

When you set a group up, LedgerOS derives a starting roster of contacts across the member entities so you don't rebuild the same list of people by hand. You then confirm which contacts should be visible at group level.

Contacts and notifications

Groups have their own Contacts & notifications settings, which is where a lot of the value sits. You decide who at the group level hears about what, so a matriarch who wants to know when anything in the family is complete gets told once rather than four times, and a subsidiary's controller doesn't get copied on the parent's filings.

Completion notices are configurable per group rather than being all-or-nothing.

Notes and limits

  • A client can belong to a group without losing anything — nothing about the individual record changes.
  • Groups don't merge billing, documents, or jobs. They coordinate them.
  • The primary entity is a pointer to the main record, not a parent that owns the others.
  • Deleting a group doesn't delete its members.
Was this article helpful?
Related articles