Skip to main content
Denari Portals is the two-way channel between your firm and your clients. Your firm publishes documents, asks for the ones it’s waiting on, and reviews what comes back. Your client signs in to a small, branded page, downloads what you’ve shared, and uploads what you’ve asked for.
Your firm needs to have the Denari Portals component enabled in order to use it. If you can’t see Portals in the product switcher and have questions, please contact the Denari or IT admin at your firm.

The two sides

Portals is built on top of Denari Documents. Your library stays the source of truth; a portal is a curated window onto it, and anything a client uploads arrives in your intake queue for review rather than landing in the library directly.

The one thing to understand first

A portal belongs to a client entity, not to a client group. You never create a portal — it is created for you the first time you publish a document to that entity, and it drops off the list when the last document is unpublished. Giving a person access is a separate step: you invite them by email, which grants that address access to that entity’s portal. Publishing a document and inviting a person are two different actions, and you need both before anyone can see anything. Select Portals from the product switcher in the top left to see every portal your firm has published to. The Portals list, with one row per client entity showing its name and how many documents are published to it.

The workflow, end to end

1

Get the document into Documents

Upload it, or let it arrive through intake. See Where documents land.
2

Set its client entity

On the Attributes tab, set the client entity. This is what decides which portal the document can reach. See Edit attributes.
3

Publish it

Right-click the document and choose Publish to client. Confirm the entity, optionally add a note the client will see, and click Publish. See Publish a document.
4

Invite the client by email

On the portal page, type their email under Invite a client by email and click Send invite. There are no passwords — the invite creates their account, and every visit after that emails them a fresh sign-in code. See Invite a client.
5

Ask for what you need

Click New request to add an item to the client’s Waiting on you list, or apply a saved checklist. See Document requests.
6

Review what comes back

An upload flips the request to Submitted and lands in your intake queue. Accept it with Mark received, or Send back… with a reason.
7

Check what the client sees

See what the client sees on the portal page renders the client’s exact view. See The portal view.
A portal page gathers all of it in one place — the documents you’ve published, the invite box, and what you’re waiting on. A client portal page showing published documents with a note to the client, an invite-by-email box, and the Document requests section below.

Learn it next

How portals work

Why portals hang off client entities, and what follows from that.

Invite a client

The one step everything else depends on.

Publish a document

Send a file out, with an optional note.

Document requests

Ask for a document and review what comes back.

Request templates

Save a checklist once, apply it to every client.

What the client sees

The page they land on, end to end.

Multiple portals

Multi-entity clients, and one person across several.

The portal view

The list, the portal page, and the preview.

Track what's published

Find published documents from the library.

Access & permissions

Who can publish, who can see a portal, what’s guarded.
Publishing is fast and reversible, but it is still the moment a document crosses to the client. Check the entity name in the publish dialog before you confirm — it names exactly whose portal the document is about to enter.