> ## Documentation Index
> Fetch the complete documentation index at: https://docs.denari.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Track what's published

> Tell at a glance which documents have reached a client, from inside the Documents library.

Portals is only half a workflow if you can't answer "has the client seen this?" without leaving [Documents](/documents/getting-started). Three pieces of portal state live in the library for exactly that.

## The published marker

A document published to any portal carries a small people icon next to its filename, tooltipped **Published to client**. It appears in the document tree and in [search results](/documents/search), so you get the answer wherever you found the document.

The marker means *published somewhere*. To find out which portal, use **Open client portal** below.

## The Published to client filter

Press **F** in the documents list and pick **Published to client**:

| Filter | Shows |
| - | - |
| **Published** | Documents currently in at least one portal |
| **Not published** | Documents in no portal at all |

Picking the same option again clears it. Like every other filter it stacks, which is what makes it useful:

* `⌘K` a client group, then **Published** — everything that client can currently see.
* `⌘K` a client group, **Year 2024**, then **Not published** — this year's work that hasn't gone out yet.
* **Service Line: Tax** plus **Published** — a firm-wide view of what tax has released.

<Tip>
  Filters live in the page URL, so the "not yet sent to the client" view is
  worth saving as a [view](/documents/library) and reopening each week rather
  than rebuilding by hand.
</Tip>

## Open client portal

Two shortcuts jump from the library straight to a portal.

**From a document.** Right-click it, or use its `...` menu, and choose **Open client portal**. If the document resolves to exactly one client entity you land on that portal; if it resolves to none or several, Denari can't tell which you mean and drops you on the portals list.

**From an entity group header.** With the tree grouped by client entity, each group header's `...` menu has **Open client portal** — unambiguous, so it always lands.

<Tip>
  The group header route is the reliable one. If a document's **Open client
  portal** keeps landing you on the list, group by client entity and go from the
  header instead.
</Tip>

## Reading it from the other side

The [portals list](/portals/portal-view) shows each entity with its published document count. Comparing that against the same entity filtered to **Published** in Documents is the quickest way to confirm a batch went out in full.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.