FlowGround
Back to Business Mode

Audit Logging

An audit log is a tamper-evident record of security-relevant actions — logins, permission changes, data exports, deletions — kept specifically so that after something goes wrong, there's a trustworthy account of exactly what happened.

Audit logs record who did what, to which resource, and when — application logs (for debugging) and audit logs (for accountability) serve different purposes and shouldn't be conflated
A log an attacker can edit or delete after the fact isn't an audit trail — write-once, append-only storage is a core requirement
Logging the login attempt isn't enough; logging the permission change, the data export, and the account deletion is what actually reconstructs an incident
Retention matters: a breach is often discovered months after it happened, by which point a 30-day log rotation has already erased the evidence

Hands-on demo

Perform actions, then try to erase the trail

Every action below writes an entry automatically. Then try deleting one, as if you were a compromised admin covering your tracks.

Nothing logged yet — perform an action above.

Try it yourself

Try it yourself — run a scenario below, then flip this and replay it to see what changes.

Admin Changes a User's Role

A routine permission change is captured automatically.

Want this flow explained in detail as it plays?

app.flowground.dev/admin/team

Team members

NameSam T.
Current roleSupport
Admin
App
Audit Log
A routine role change made through the admin console.

Selected hop

Admin promotes a teammate to "Billing Admin"

Admin

A staff member with elevated permissions to manage accounts, roles, or platform settings.

App

The application's backend — enforces business rules and decides what every request is allowed to do.

What happens here

A routine role change made through the admin console.