Skip to main content
Because a portal belongs to a client entity, a client group with three entities has up to three portals, and they never mix. What you usually want is one person who can see more than one of them.

​
One person, several businesses

This is the common case, and the answer is simply to invite them more than once.
1

Open the first entity's portal

Invite the person by email as normal. See Invite a client.
2

Open the next entity's portal

Invite the same email address again.
3

Repeat for each entity they need

Access accumulates — each invite adds an entity rather than replacing the last.
4

Confirm in Admin › Clients

All of their entities appear as badges on one row, under Portal access.
They still have one login. When they sign in they see a single page covering every entity they’ve been granted, with chips across the top to filter to one business at a time.
Re-inviting an existing client is safe and never sends a duplicate email — you’ll see Client already had access rather than Invitation sent. It also restores access for someone whose access was previously revoked.

​
Standing up a client group’s portals

To cover every entity of a multi-entity client:
1

Filter Documents to the client group

Press ⌘K and pick the group. See Search.
2

Group by client entity

Each entity’s documents fall under its own header.
3

Publish from each group in turn

The first publish to an entity creates its portal.
4

Check from the group header

An entity group header’s ... menu has Open client portal, so you can check without leaving the tree.
Confirm coverage from the portals list rather than from memory. Any entity missing from it has no portal yet.

​
One document in more than one portal

Useful for something that genuinely belongs to several entities — a group-level engagement letter, say. Denari only publishes a document to an entity it’s tagged to, so this takes two steps:
1

Tag the document to every entity it belongs to

On the Attributes tab, attach each relevant client entity. A document tagged to a single entity can only reach that entity’s portal, so the tagging has to come first. See Edit attributes.
2

Publish once per entity

Publish to client now opens a picker listing exactly those entities. Pick one, publish, then run it again and pick the next.
Each publish adds the document to one more portal; none replace each other, and publishing to the same portal twice does nothing.

​
Removing access

  • To take a document out of one portal, unpublish it there — the ✕ on its row. See Publish a document.
  • To close a portal entirely, unpublish every document in it. The portal drops off the list; the entity, the client group, and every document are untouched.