> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/assessment-history.md).

# Assessment History

**Assessment history** lists the assessment snapshots retained for your standards. Open a snapshot to inspect its controls and rule validations exactly as they were recorded. A snapshot is separate from the latest calculated score.

Open it from **Workspaces** → **Compliance** → **Assessment history** in the sidebar.

{% hint style="warning" %}
You need a role that can view compliance standards.
{% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FmOoujPEwwSX08eeST8oo%2Fv2-compliance-history.png?alt=media&amp;token=f0772837-868c-4c3d-8349-563e494361d5" alt="Assessment snapshots list"><figcaption><p>Assessment history</p></figcaption></figure>

## Assessment Snapshots

Each snapshot shows the standard, when it was retained and the **Retained snapshot score**.

| Filter        | Description                                         |
| ------------- | --------------------------------------------------- |
| **Standards** | One or more standards, or **All standards**.        |
| Time range    | **All retained history**, or a snapshot time range. |

**Save filters** stores the filters under a name. To create a snapshot, use **Create assessment snapshot** or **Retain snapshot** in [Standards & Frameworks](broken://pages/2ded2e2e308bc0fe50fc7a95b55dad213487f979).

## Inspect a Snapshot

Select **Inspect snapshot →** to open it.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fjt8hZ8kCC7ZaCCgA5hda%2Fv2-compliance-snapshot.png?alt=media&amp;token=1cda89fe-196d-4f2d-8c17-e2e87afff489" alt="A retained snapshot with its score and control hierarchy"><figcaption><p>Retained snapshot</p></figcaption></figure>

| Tile                            | Description                                                                           |
| ------------------------------- | ------------------------------------------------------------------------------------- |
| **Recorded score**              | The score at snapshot time.                                                           |
| **Controls**                    | Controls in the standard and how many apply to this organization.                     |
| **Controls with mapped rules**  | Controls with mapped rules. Others need manual assessment or have no automated check. |
| **Failed validations retained** | Application and rule results that failed.                                             |

**Control hierarchy** lists the criteria and controls with their recorded scores. Open a control to see its description, mapped rules and failing applications. Use **Expand all** and **Collapse all** to navigate, **Export controls** to download the hierarchy, and **Printable report** for a printable copy. **Current standard** opens the standard as it is now.

{% hint style="info" %}
Every value in a snapshot is as recorded at the time. Only failed validations are retained, so an application missing from a control's list was not necessarily evaluated; its absence is not proof of compliance.
{% endhint %}

## Next Steps

* [Standards & Frameworks](broken://pages/2ded2e2e308bc0fe50fc7a95b55dad213487f979): retain a new snapshot.
* [Treatment Plans](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/treatment-plans.md): follow the plans for failing risks.
* [Compliance](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance.md): see all Compliance screens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/compliance/assessment-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
