> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/audit-and-compliance/running-an-audit.md).

# Running an Audit

## ![](https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2F0pk52bJqKVUJPTPVPhiw%2FSummary2-Small-Icon.svg?alt=media\&token=74913d54-0cfd-4703-aa56-af396629dc59) Overview

An audit runs automatically every four hours for each organization assigned to Audit & Compliance, and you can run a manual audit at any time. This article shows you how to run a manual audit for a single organization.

{% hint style="warning" %}

#### Deleted Components

An audit job reports only **Soft Deleted** components (those moved to the Recycle Bin) as deleted. Once a component is **Permanently Deleted**, it no longer appears in the component list.
{% endhint %}

## Run an Audit

{% stepper %}
{% step %}

### Select Organization

1. Click **Organizations** from the left sidebar menu.
2. In the table, click the organization you want to audit.

   <div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2FIIUZl43BI9wYj5Ij8xSA%2FRunningAnAudit-S01-01.png?alt=media&amp;token=809430b5-397c-4b4b-868c-ef2b54c66470" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Run Audit

1. Click **Run Audit** in the upper right of the page.

   <div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2Fhjy1Rmqu6UUgdSNj7aXV%2FRunningAnAudit-S02-01.png?alt=media&amp;token=becf8163-38c9-4c7e-bd26-065abb859744" alt="" width="563"><figcaption></figcaption></figure></div>
2. Once the audit starts, it appears in the **Activities** tab with its job status.

   <div align="left"><figure><img src="https://3321997875-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxpieUdPB8n4L2gG8EYRy%2Fuploads%2FqSvsx6L40sPMfEfvUt72%2FRunningAnAudit-S02-02.png?alt=media&amp;token=ba14bbb7-0772-49b5-af72-ca1492ba38e8" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
To cancel an audit, click **Abort** next to the job status.
{% endhint %}
{% endstep %}

{% step %}

### Review Components

Once the audit is complete, you can view the updated status of each component. See the following article for instructions.

* [Viewing Component Audit Status](/audit-and-compliance/viewing-component-audit-status.md)
  {% endstep %}
  {% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flosum.com/audit-and-compliance/running-an-audit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
