Read the audit log and the AI audit

For admins, managers and data protection leads for the audit log. The AI audit is for admins. Both ask you to confirm it is you.

Steps

1. Open Admin, then Audit log. Confirm it is you if asked.
2. Set how many entries to show with the limit box and apply it.
3. Read the table: when, who (Actor), their role, the Action, the Target, the row and the person affected.
4. Open a diff to see which parts changed.
5. Read the line at the top. It says when records began to be tagged to your organisation.
6. For AI, open AI audit. Filter by Feature and read Model and Status for each use.

If it goes wrong

• If you are sent to confirm it is you, do so and you return here.
• If an entry is missing, it may be older than the line at the top, which says when records were first tagged.
• If the log cannot be read, the page shows the error. Reload and tell your admin if it persists.

What the audit log shows

The most recent changes across your organisation. It lists who did what, to which row, and what changed. It never shows a change made before records were tagged to your organisation.

Why you must confirm it is you

The log can show before-and-after detail of sensitive records. That needs a sign-in from the last five minutes.

The AI audit

Every use of an AI feature is listed with the feature, the model, who used it, the outcome and the size of the request. It also records what was removed before anything was sent.

Use it to check that AI is used only where you expect.

Using the logs well

Look for the unusual: a change at an odd hour, many reads of one record, or an unexpected person.

How it links together

Almost everything in Daymello writes to the audit log: edits, exports, restrictions and sign-offs. The activity page shows a lighter day-by-day view of the same events.

See the guides on what happened across the service, on subject access requests and on retention.