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

# Platform Compliance

> Compliance automation dashboard showing regulatory check statuses with trigger and consent summary views.

The Compliance screen displays the regulatory compliance dashboard at the route `/settings/compliance`.

## Overview

The screen renders `ComplianceWidget` cards from `useComplianceDashboard`, each showing a compliance check area with its latest status (pass/warning/fail/unknown) and a relative timestamp. A consent status summary from `useConsentStatusSummary` is also displayed. Users can manually trigger compliance checks via `useTriggerComplianceChecks`. The page uses `useComplianceTheme` for white-label compliance theming and includes a `ContrastFallbackIndicator`. Sub-pages for PHI classifications (`/settings/compliance/classifications`) and compliance evidence (`/settings/compliance/evidence`) require additional permissions.

## Who it's for

Required permission: `pf.compliance.dashboard.view`

## Before you start

* You must hold the `pf.compliance.dashboard.view` permission.

## Steps

<Steps>
  <Step title="Open Compliance">Navigate to Settings → Compliance.</Step>
  <Step title="Review compliance check status">View each compliance area card showing pass/warning/fail/unknown status and last-checked time.</Step>
  <Step title="Trigger a compliance check">Click the trigger action to run compliance checks on demand.</Step>
  <Step title="Review consent summary">Check the consent status summary displayed on the dashboard.</Step>
  <Step title="Navigate to sub-pages">Access PHI Classifications (`/settings/compliance/classifications`) or Evidence (`/settings/compliance/evidence`) for deeper detail (requires additional permissions).</Step>
</Steps>

## Key concepts

* Compliance check status values: `pass`, `warning`, `fail`, `unknown`
* `useComplianceTheme` — applies white-label compliance visual override
* PHI Classifications sub-page requires `pf.compliance.phi.classify`
* Evidence sub-page requires `pf.compliance.evidence.generate`

## Related

<Columns cols={2}>
  <Card title="Platform Foundation" icon="layer-group" href="/pf/overview">
    Platform Foundation overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index">
    Documentation coverage and governance.
  </Card>
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/platform.tsx
  * src/platform/compliance/pages/ComplianceDashboardPage.tsx
</Accordion>