Created with AI.
The audit log shows who changed what and when. It uses storage, so it should be enabled with care.
This is the master switch. Without it, nothing happens even if individual tables are marked for revision.
Don't enable everything. Choose what matters: ownership, status, amount, and personal data. Enabling everything uses a lot of storage and creates a log that no one can navigate.
Audit data can be retained for a specific number of years or until it is manually deleted. Set a retention period that meets your requirements, rather than allowing it to grow indefinitely.
Make a change and find it again in the log. Ten minutes here will reveal whether the field selection actually worked.
The revision history is available for each entry and collectively under the environment settings. Show both to those who will use it.
Audit data counts toward the storage quota and can grow quickly. Check usage after one month and adjust the scope.
Ask a question or share what helped you.

Published 3/28/2025
We work continuously to improve information security (ISO 27001), quality (ISO 9001), and environmental management (ISO 14001), and are therefore proud to have successfully completed a new audit of our certifications in these areas.
Read morePublished 8/30/2024
Over the past few years, hybrid workplaces have become the norm for many. Along with this shift, both IT functionality and security needs have changed. Here are some useful tips from our Head of IT and Security on how organizations should approach securing their IT in a hybrid world.
Read moreDo you have a question or experience to share?
Be the first to contribute.