> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/managing-account/generate-and-use-audit-log-reports.md).

# Generate and use audit log reports

How to generate and use audit log reports in Snyk API & Web

{% hint style="info" %}
**Snyk is rolling out a new navigation.** The steps on this page describe the classic interface. If your view looks different, visit [Navigate the Snyk Web UI](https://docs.snyk.io/navigate-the-snyk-web-ui#where-things-moved) to map these options to the new interface.
{% endhint %}

## Generate and use audit log reports

Generate audit log reports and understand their content.

Audit logs record user activity in Snyk API & Web, which lets you reproduce the timeline of events that users originated. This is useful for identifying and analyzing behaviors or issues and taking the necessary actions.

This article is divided into the following sections:

* Generate the audit log report.
* Understand the information in the audit log report.
* Mapping of object model values and business names.

### Generate the audit log report

To analyze the audit log, first generate the report:

1. Open the **Settings** dropdown on the bottom-left corner of the navigation bar and select **Audit Log**.
2. Fill in the criteria of the report. You can download the list of actions performed by a single user or by all users in a specific period. When you are done, click **Export**.

### Understand the information in the audit log report

Events listed in the report describe which action was done, on which object, when, and by whom. Update actions also include information about the fields that changed and the old and new values.

The report is in CSV format and you can open it in any application that handles spreadsheets.

Snyk sorts the events by date, starting with the oldest event, and displays all event details in columns:

* **user\_email** - Email of the user that originated the event.
* **date** - Date and time of the event, in ISO 8601 UTC format.
* **action** - Action of the event, which can be:
  * create - Snyk created a new object.
  * update - Snyk updated an existing object.
  * delete - Snyk deleted an existing object.
* **object\_model** - Type of object. Visit the next section for more information.
* **object\_id** - Identifier of the object.
* **field** - In update actions, this shows the name of the property or parameter for which the value changed.
* **old\_value** - In update actions, this shows the value before the change.
* **new\_value** - In update actions, this shows the new value of the property or parameter.

### Mapping of object model values and business names

The following table contains the mapping of the **object\_model** values to the business names:

| Object\_model value       | Business Name       |
| ------------------------- | ------------------- |
| vulndb \| scope           | Target              |
| domains \| domain         | Domain              |
| vulndb \| assessment      | Scan                |
| vulndb \| asset           | Extra Host          |
| vulndb \| asset sequences | Navigation Sequence |
| vulndb \| finding         | Finding             |


---

# 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://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-api-web/managing-account/generate-and-use-audit-log-reports.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.