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

# Review completed compliance assessments

> Use Compliance Menu History to find completed instances, compare their details, and export the loaded results.

**Audience:** Company users and MSP staff with access to the relevant Compliance records. Your MSP controls Company access and shared assessments.

## Open Check History

1. Open **Compliance**.
2. Select **Compliance Menu > History**.
3. Check the selected company or aggregate view.
4. Filter the table by the available Company, Check, Entity, Run, Status, Completed By, Notes, or Date fields.
5. Select a check title to open its details.

This page lists completed assessment instances across runs. It is separate from the **History** tab inside a check, which compares other completed instances of that particular check for the company.

## Understand the columns

| Column           | Meaning                                                                             |
| ---------------- | ----------------------------------------------------------------------------------- |
| **Company**      | Company associated with the assessment.                                             |
| **Check**        | Requirement assessed; a flag or paperclip can indicate additional context or files. |
| **Entity**       | The assessed company, location, or device.                                          |
| **Run**          | Assessment run containing the instance.                                             |
| **Status**       | Recorded status label. Completed assessments can have unsuccessful results.         |
| **Completed By** | Completing user when recorded; the display can fall back to the last updating user. |
| **Notes**        | Available note preview. Permitted MSP writers can also see internal notes.          |
| **Date**         | Last-updated timestamp for the assessment, not necessarily its completion date.     |

Hover a note preview when available to read more, or open the assessment for context. A paperclip indicates a file count; it does not include the file contents in the table.

## Account for the history limit

This page initially loads **up to 100 completed assessments**, ordered by most recently updated. Table filters, sorting, company selection, and local pagination operate on those loaded records; they do not automatically retrieve every older assessment.

A company can therefore show few or no rows even when older history exists outside the loaded set. If you cannot find an older instance, open the relevant check’s [History panel](/user-guides/compliance/read-evidence-and-history#review-earlier-completed-assessments), or ask your MSP to locate it. Do not use this page’s row count as a lifetime total.

## Read a completed instance

The detail dialog opened from this page is marked as a historical record and disables assessment field and note editing. Review the run, target, status, public findings, and available evidence. Close it to return to the list.

This is a recorded completed instance, not a reconstruction of every change over time. Do not infer that a past result still describes the current environment. Review the latest assessment separately.

## Export the loaded history

1. Check the current company scope and table filters.
2. Select **Export CSV** in the table toolbar.
3. Open the downloaded file and verify its date range and records.

The CSV includes the filtered records from the loaded history set, across its local table pages. It does not fetch assessments beyond the initial 100-record limit. It contains company, check, entity, run, status, completing or updating user, last-updated date, priority, flag, public notes, and file count. The History exporter adds private notes only for the permitted internal writer view.

The export uses a fixed field set rather than the table’s visible columns. Notes become plain text. Attached files must be downloaded separately from the assessment.

## Troubleshoot an empty page

Check filters, company scope, and the 100-record limit first. A load failure can also produce an empty table. Reload and ask your MSP to investigate if an expected completed instance is missing. An empty table is not proof that no assessments have been completed.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does Check History show every assessment ever completed?">
    No. The initial result is limited to the 100 most recently updated completed instances. Local filters and pagination do not fetch older records.
  </Accordion>

  <Accordion title="Why is an older company assessment missing after I select the company?">
    Company filtering is applied to the loaded result set. The older assessment can be outside that set. Check the relevant assessment’s History panel or ask your MSP.
  </Accordion>

  <Accordion title="Is Date the date the check was completed?">
    This table displays and filters the last-updated timestamp. It is not necessarily the completion timestamp.
  </Accordion>

  <Accordion title="Does Completed By always identify the person who completed it?">
    When a completing user is unavailable, the display can fall back to the last updating user. Verify the underlying record before using the display as audit evidence.
  </Accordion>

  <Accordion title="Does the CSV contain all older history?">
    No. It exports filtered records from the loaded set, limited by the initial 100 records. It does not perform an all-history download.
  </Accordion>

  <Accordion title="Is this the same as the History tab inside a check?">
    No. This page lists completed instances across checks and runs. The check’s History panel compares completed instances of the same check for the company.
  </Accordion>
</AccordionGroup>