> For the complete documentation index, see [llms.txt](https://knowledgebase.qommentary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.qommentary.com/qommentary-writeback/advanced/audit-trails/enable-audit-trails-for-database.md).
# Database audit trailing
To enable audit logs for databases you need to create a new table for auditing and then enable audit logs option at the extension level.
### Create a new table for auditing
Before using audit logs, you need to create a new table in your database to store the logs. The structure of this table must be the same as the writeback table with 3 additional columns: ActionAt, ActionBy and ActionType.
| Column | Type | Description |
| -------------- | -------- | ---------------------------------------------------------------- |
| **ActionAt** | datetime | Date and time when the action was performed |
| **ActionBy** | string | Which user performed the action (UserDirectory\UserId) |
| **ActionType** | string | What action was performed ( C = create, U = update, D= delete ) |
### Enable audit logs in the extension
1\. Open the properties panel and click on the Data Connections section
{% hint style="warning" %}
You need to set up a connection before enabling logs
{% endhint %}
2\. Go to the *Enable audit logs* option
3\. Click on the switch control to enable audit logs
4\. Enter the name of the log table (e.g. Customers\_log)
