Skip to content

Audit events ​

Audit records answer who performed a sensitive action, where it happened, and when. They describe the action without storing the secret value involved.

Audit events in 0.1.9 ​

AreaEvents
Secretssecret.created, secret.updated, secret.deleted, secret.revealed, secret.imported, secret.exported, secret.runtime_accessed
Projectsproject.created, project.renamed, project.deleted, project.initialized
Environmentsenvironment.created, environment.renamed, environment.deleted
Runner tokenstoken.created, token.revoked
Authenticationlogin.succeeded, login.failed, logout.succeeded
Administrator & usersadmin.bootstrapped, admin.created, admin.updated, admin.deleted, admin.reauthenticated, admin.password_changed
AI service accountsservice_account.created, service_account.deleted, service_account.token_created, service_account.token_revoked
Backupsbackup.created, backup.downloaded, backup.uploaded, backup.restored, backup.deleted, master_key.downloaded, backup.restored_bootstrap

The API schema defines the event names used by this release.

Record contents ​

Root and admin can review user, AI account, and backup history in the Audit page.

An audit record may contain:

text
timestamp
actor
action
organization
project
environment
secret key
IP address
user agent

It must never contain the plaintext secret value, a usable authentication token, or a request body that carries credentials.

Example ​

text
2026-08-27 14:23
actor: alice@example.com
action: secret.updated
project: payment-service
environment: production
secret: DATABASE_URL

Retention, export, advanced filtering, and additional integrity guarantees remain roadmap work.

Open-source secrets management for developers.