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

# Audit logs

As your team grows and more teammates start using your applications on a daily basis, it's important to keep track of changes made or errors received to help you troubleshoot. That's when audit logs come in handy.

{% hint style="success" %}
Audit logs are available to users with an **Admin** role.
{% endhint %}

You can access them by clicking on your workspace name and selecting **Audit logs** in the menu. Audit logs can be filtered by a certain time period, environment, app, or user. You can also select a specific **log level**:

* Log
* Warn
* Error

If you need to load the latest logs, you can just click the *Refresh logs* button. You don't have to reload the page or set the filters.

The following events are tracked in the Audit logs:

{% tabs %}
{% tab title="User" %}

* Log in
* Sign up
* Log out
* Entered wrong password
* Entered wrong MFA
* Requested password reset
* Completed password reset
* Roles assigned
* Invited
* Removed
* Permission denied
  {% endtab %}

{% tab title="Role" %}

* Created
* Updated
* Removed
* (System) updated
  {% endtab %}

{% tab title="App" %}

* Create
* Open (failed attempts included)
* Deploy
* Publicity changed
* Page view
* Delete
  {% endtab %}

{% tab title="Datasource" %}

* Connect
* Update
* Delete
* Request
  {% endtab %}

{% tab title="Builder" %}

* Open
* Exit
* Version overwritten
* History snapshot restored
  {% endtab %}

{% tab title="Action" %}

* Success
* Error
* Request performance metrics
  {% endtab %}

{% tab title="Git" %}

* Connect
* Import
* Disconnect
* Default branch updated
* SSH keys generated
* Branches synced
* Branch created
* Branch deleted
* Commit
* Pull
* Force pull
  {% endtab %}
  {% endtabs %}

{% tabs %}
{% tab title="Automation" %}

* Error
* Success
* Created
* Updated
* Deleted
  {% endtab %}

{% tab title="Database" %}

* Create table
* Delete table
* Duplicate table
* Update table
  {% endtab %}

{% tab title="Admin" %}

* Viewed audit logs
* Password reset link generated
* Password reset requested
* MFA reset
* Reset failed login attempts
* MFA settings updated
  {% endtab %}
  {% endtabs %}

{% hint style="success" %}
In the **Enterprise** version, you have the ability to log request payloads. This feature enables you to track the data sent to databases and APIs. To activate this feature, set the `UI_BAKERY_AUDIT_LOGS_LOG_PAYLOAD` variable to `true`.
{% endhint %}

{% @arcade/embed flowId="x88jMjS8k8hpFLczbfjY" url="<https://app.arcade.software/share/x88jMjS8k8hpFLczbfjY>" %}


---

# 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.uibakery.io/concepts/workspace-management/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.