> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/setup-configuration/account-settings/resource-audit-log.md).

# Resource Audit Log

### Overview <a href="#toc_1" id="toc_1"></a>

The Resource Audit Log records a history of changes to your data catalog, so you can answer questions like *"when did the owner of this table change?"* or *"when did this resource first show up in our catalog?"* It's searchable and filterable from a single page in Account Settings.

### Prerequisites <a href="#toc_2" id="toc_2"></a>

* Your account must have the Audit Log feature enabled by Euno.
* Viewing the Audit Log requires the **View Resource Audit Log** permission, assigned to the **Account Admin** persona by default.

### Where to find it <a href="#toc_3" id="toc_3"></a>

Navigate to **Account Settings → Audit Log**.

### What's tracked <a href="#toc_4" id="toc_4"></a>

Every catalog change recorded by the Audit Log falls into one of three event types:

| Event type            | What it captures                                                                                                                                                                    |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Fixed tag**         | A user manually edits a fix tag value on a resource.                                                                                                                                |
| **Built-in property** | An observer ingests a new value for one of Euno's built-in catalog properties (for example, owner or description) that differs from the previously stored value.                    |
| **Lifecycle**         | A resource is added to the catalog for the first time (**Created**) or removed from it (**Deleted**). Repeated observations of an unchanged resource don't produce additional rows. |

{% hint style="warning" %}
History starts from the day the Audit Log is enabled for your account. Changes made before that date are not retroactively logged — including resources that already existed in your catalog, which are not logged as newly "Created."
{% endhint %}

Each row shows the resource's URI and type, the property that changed (where applicable), the actor responsible (a user, or the observer that ingested the change), the timestamp, and the new value. Euno does not store the prior value directly, so only the new value is shown.

### Searching the log <a href="#toc_5" id="toc_5"></a>

1. Enter at least one filter — **URI**, **Property**, **Event type**, **Resource type** (multi-select), and/or **Actor** (comma-separated for multiple) — the search requires at least one of these.
2. Set a **Start time** and **End time**. The window defaults to the last 7 days and can be widened up to 365 days (or your account's configured retention, if different).
3. Click **Search**.

Results appear in a table with these columns: **Time**, **Event** (the event type), **Actor**, **Property**, **Type** (resource type), **URI**, and **New Value**. Use **Previous** / **Next** to page through results (50 rows per page); the total number of matching rows is shown above the table.

### Retention <a href="#toc_6" id="toc_6"></a>

The catalog history's retention period is customized per account. If you are unsure about the duration, contact your account manager for additional information .

Searches cannot span a longer range than your account's configured retention.


---

# 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.euno.ai/setup-configuration/account-settings/resource-audit-log.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.