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

# Customer portal

> Understand how approved findings and reports reach the customer portal as versioned snapshots.

export function VisibilityNote({children}) {
  return <Callout type="info">
      <strong>Visibility note:</strong> {children}
    </Callout>;
}

export function ReportAccessNote({children}) {
  return <Callout type="info">
      <strong>Report access:</strong> {children}
    </Callout>;
}

# Customer portal

The **Customer Portal** is the read-only delivery surface for approved content. It lives at `/portal`, outside the main dashboard sidebar.

Use the portal when you need to confirm what customers can actually read after your team publishes approved findings, report sections, or full reports.

<VisibilityNote>
  Portal visibility is scoped to your account and assigned engagements. You only see published snapshots that apply to engagements you can access.
</VisibilityNote>

## How publishing reaches the portal

Dashboard users prepare content in the report workspace and on finding detail pages. Publishing creates immutable snapshots; draft workspace edits do not appear in the portal until you publish again.

```mermaid theme={null}
flowchart LR
  A[Draft in workspace] --> B[Review and approval]
  B --> C[Publish snapshot]
  C --> D[Customer portal]
```

<ReportAccessNote>
  Publishing requires report- or finding-approval permissions. Review threads must be resolved and reviewer approvals must be in place before report publication is enabled.
</ReportAccessNote>

## Portal home

On `/portal`, you see engagement cards for work that has at least one published item. Each card shows:

* customer name
* engagement title
* count of published items

Select a card to open the engagement’s portal package view.

## What customers see

Published portal content is snapshot-based. Customers review approved findings and report material without seeing in-progress draft edits from the workspace.

## Related guides

* [Reports](/dashboard/reports)
* [Findings and endpoints](/dashboard/findings-endpoints)
* [Review and publish to the portal](/workflows/review-and-publish-to-portal)
