Security and compliance
Show who changed what
Joomiz records every apply, registration, provisioner change and run release with the person's ID, their role and the target. Read the trail with joomiz audit or on the dashboard Audit page.
With Joomiz
-
Read the trail
joomiz auditprints the newest events first. Filter by action, application, run, outcome or time. An operator can also filter by user ID.$ joomiz audit joomiz audit --from 2026-10-28T19:18:00Z --action run.abandoned TIME ACTION OUTCOME KIND SUBJECT 2026-10-28T19:20:16.016Z run.abandoned performed person 5d0f... -
Follow one run
Filter by run to see the events around it. A refused apply is recorded too, with its reason.
$ joomiz audit --run <id> joomiz audit --run 74c4e9a7-beb9-4557-bcdb-c5ccc2d730f4 TIME ACTION OUTCOME KIND SUBJECT 2026-10-28T19:20:16.016Z run.abandoned performed person 5d0f... 2026-10-28T19:20:14.490Z apply.requested performed person e2b8... -
Let teams see their own events
A person with the role
owner:<team>reads only the events of the team's applications. The ID of an operator shows as(hidden). -
Set retention and erase on request
Events are kept for
joomiz.audit.retention, from 90 to 3650 days. A second operator can erase a person's ID. The events stay and show(erased).
What you get
- One trail that names the person, the role, the action and the target.
- An answer to "who applied this?" in one command.
- A trail that respects an erasure request and a retention limit.
The rules that still hold
- An event is written with its action. If the write fails, the action is not done.
- An owner reads only its own applications and never sees an operator's ID.
- An operator cannot erase their own ID. The erasure is recorded too.
Read more in the docs
Related use cases
Talk to us
Tell us about your platform and the services your teams ship.