Tesria

Audit

The audit log is Tesria’s record of who changed what, and when: roles and rights, settings, invites, publishing, deleted spaces, backups and restores, sign-ins, and more. Come here to answer “who turned this on?”, or after an alert, to see what else an account did.

To open it, choose Admin, Audit (Admin is in the top bar; in a narrower window it is under More, and on a phone in the ☰ menu).

It is not pictured here, because every entry names real people.

Reading it

The tab shows the latest 50 entries, newest first. Each one has:

  • What happened, by its internal name, such as user.role_changed, user.status_changed, user.totp_disabled, settings.updated, invite.created, space.published, space.access_recovered or permissions.changed.

  • Who did it, or system for something Tesria did by itself.

  • When.

  • The details as recorded, such as which account changed and its new role.

Entries about a space or page you are not allowed to see are left out, because their details can name the page.

Why you can trust it

Every entry is linked to the one before it by a hash, a kind of fingerprint of its contents, so an entry that is altered or removed breaks the chain. Verify now on the Security tab checks the whole chain, and Tesria checks it once a day by itself, raising a critical alert if it is broken.

Every entry is also written to the application’s log (docker compose logs app on the server), where someone who can change the database cannot reach it.

A restore takes the audit log back too, like everything else in the wiki. Tesria knows a restore happened, and does not treat the shorter log as tampering.


Applies to

Tesria 0.5 and later

Updated

September 24, 2026

Changes

Revised.