> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/settings/audit.md).

# Audit

Every administrative action in codev — registering an org, changing a team, approving a release, accessing an integration, comparing artifacts — is recorded in an append-only audit log. The **Audit** page, under **Settings**, is where you review and export it, both for your own investigations and for compliance evidence.

<figure><img src="/files/WMAMJatchuWhRtpUBPSZ" alt="The Audit log"><figcaption><p>The Audit log — administrative events with their time, source, action, actor, and the entity they touched</p></figcaption></figure>

## What is recorded

Each event captures **when** it happened, the **source** area it came from (environment, integration, access, release, and so on), the **action**, the **actor** who performed it, the **repository** and **entity** it affected, and the request and metadata behind it. The log is append-only — records cannot be edited or deleted after the fact.

## Reviewing and filtering

Narrow the log by source, action, actor, repository, or entity, and by a date range, then page through the results. The audit spans the whole organisation, so activity across all your projects is in one place; filter by repository to focus on a single project.

## Exporting for compliance

**Export CSV** writes the filtered log out for SOX or SOC 2 evidence, an access review, or an incident investigation. For the deeper approval and release audit trail — who requested and approved each release — and for locking your production org and DevHub to your instance's IP address, see the sfp server [Audit Trails](https://docs.flxbl.io/sfp-server/security-and-compliance/audit-trails) documentation.

## Related

* [Flows: approvals and the audit trail](/flxbl/codev/flows/overview.md#pending-approvals)


---

# 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.flxbl.io/flxbl/codev/settings/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.