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

# Compliance views

> See framework coverage and produce audit evidence from the dashboard.

The **Compliance** area of the dashboard shows how your code checks map to the
compliance frameworks your organization is held to, and is where you produce
evidence for an audit.

## Framework coverage

The compliance views show, for each active framework, which controls your checks
cover and where you have gaps. This is the same mapping described in
[Compliance overview](/compliance/overview): policies map to controls, controls roll
up into frameworks.

The frameworks available to you depend on your plan and your organization's
configuration.

## Export evidence

When it's time for an audit, export structured evidence rather than screenshots:

<CardGroup cols={2}>
  <Card title="OSCAL export" icon="file-shield" href="/compliance/oscal-export">
    Export NIST OSCAL documents for auditors and GRC tools.
  </Card>

  <Card title="SBOM export" icon="boxes-stacked" href="/compliance/sbom-export">
    Generate a CycloneDX or SPDX Software Bill of Materials.
  </Card>
</CardGroup>

## Combine overlapping frameworks

If you're held to more than one framework, **PolicyMerge** shows where their
controls overlap so you can assess once and satisfy several. See
[PolicyMerge](/navigation/policymerge).

## Next steps

<CardGroup cols={2}>
  <Card title="Compliance overview" icon="clipboard-check" href="/compliance/overview">
    How frameworks, controls, and policies fit together.
  </Card>

  <Card title="PolicyMerge" icon="layer-group" href="/navigation/policymerge">
    Read the overlap view.
  </Card>
</CardGroup>