> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/developer-reference/database/audit-logs.md).

# Audit Logs

Audit Logs allow the user to easily and rapidly know what happened during system configuration. This accelerates the maintenance and troubleshooting of TelcoBridges systems.

### Availability

Audit Log is available since Toolpack 2.7.

### Features

All the actions made on the TelcoBridges Web Portal are logged in the database.

Each audit log contains:

* The time of the action
* The user who did the action
* The kind of action done
* The old and new values of the modified resource

To help the user identify issues faster, the *package and configuration activations* are highlighted in green. This provides instant recognition of any changes since the last applied configuration.

### Configuration

* [Toolpack v3.0:Audit Logs](https://tmediadocs.telcobridges.com/other-pages/system-settings-overview/tmedia-tdev-and-tsig-web-portal-3-0-system-settings#audit-logs)

<details>

<summary>Older versions: 2.10 and lower</summary>

* [Toolpack v2.10:Audit Logs](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-system-settings#audit-logs)
* [Toolpack v2.9:Audit Logs](https://tmediadocs.telcobridges.com/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-system-settings#audit-logs)
* Toolpack v2.8 and earlier: documentation is no longer published. Contact [technical support](https://tmediadocs.telcobridges.com/operations-and-support/support/contacting-telcobridges-technical-support) if you need it.

</details>


---

# 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://tmediadocs.telcobridges.com/telecom-references/developer-reference/database/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.