> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/ad-server/admin/saas-admin-audit-logs.md).

# Audit Logs

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2F8VOSTcbckOJFOM9dTvQo%2Fsaas-admin-audit-logs_3.png?alt=media&amp;token=7a772088-7005-461e-93e7-ea73fbcc83fe" alt="Audit Logs table"><figcaption></figcaption></figure>

As a **Super Administrator** or **Administrator**, you can use the **Audit Logs** page to see the changes made on your Ad Server, such as edits to accounts, campaigns, sites and zones. Each entry shows what changed, who changed it, and when.

Go to **Admin > Audit Logs** to open it.

{% hint style="info" %}
Audit Logs is only available if it's enabled for your Ad Server. Please contact your EXADS representative to enable this feature.
{% endhint %}

## Audit Logs Table

Each row in the table is one logged action. The table shows the following columns:

* **User**: The username of the account in which the action was made.
* **Action**: The action that was made.
* **Resource ID**: The ID of the item the action was made on, such as an account, campaign or zone.
* **Date**: The date and time of the action.
* **User IP**: The IP address the action was made from.
* **Network User**: The Ad Server user who made the action while logged in as the account. This shows **N/A** when the account holder made the action themselves.
* **Source**: Where the action was made from.
* **Session**: The session ID of the action.

Other empty values are shown as **-**.

The table is sorted by **Date**, newest first. You can only sort by **Date**. Use the filters to narrow down the other columns.

## Filtering the Audit Logs

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FsmJHzwCMKjUmVMg4LbjL%2Fsaas-admin-audit-logs-filters_1.png?alt=media&amp;token=67adb4d1-0be7-4b26-a483-0e7ce2f171f8" alt="Audit Logs filters"><figcaption></figcaption></figure>

Use the date picker to choose the period to show. **Today** is selected by default.

Click **+ADD FILTER** to filter by:

* **Action**: Select one or more actions from the list.
* **Network User**: Select the Ad Server user who made the action.
* **Old Or New Value**: Enter a value from before or after the change.
* **Resource ID**: Enter the ID of the item the action was made on.
* **Session**: Enter a session ID.
* **Source**: Select where the action was made from.
* **User**: Enter the username of the account.
* **User IP**: Enter an IP address.

Click **APPLY** to filter the table. The table goes back to the first page.

Click **RESET FILTERS** to remove the filters. The date range stays as selected.

## Viewing the Details of an Action

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FIzklKcFJNeqVkh5LVxCM%2Fsaas-admin-audit-logs-detail_2.gif?alt=media&amp;token=3ea01695-301d-4a8c-9ea4-b70496129dbb" alt="Opening the Audit Logs Detail window"><figcaption></figcaption></figure>

Click the **Audit Logs Detail** icon to the left of an entry to see the full details. The **Audit Logs Detail** window shows the same columns as the table for that entry, followed by a table of every field that changed:

* **Field Name**: The field that changed.
* **Old Value**: The value before the change.
* **New Value**: The value after the change.


---

# 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.exads.com/ad-server/admin/saas-admin-audit-logs.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.
