Skip to content

Audit Log

Every change in можно. is recorded: who changed what and when. The audit log stores the full history of changes to flags, segments, API keys, and settings.

What Gets Logged

ResourceEvents
FlagsCreation, strategy changes, targeting changes, renaming, archival, restoration, deletion
SegmentsCreation, rule changes, renaming, deletion
API keysCreation, regeneration, revocation, deletion
EnvironmentsCreation, renaming, deletion
ProjectSettings changes, renaming
UsersInvitation, role change, deletion

Viewing the Audit Log

Dashboard

The Audit section is accessible from the main menu.

Each entry contains:

FieldDescriptionExample
Date and timeWhen the change occurred (UTC)2026-06-21 13:41:05
UserWho made the changeadmin@example.com
ResourceWhat was changedFlag new-checkout
ActionType of changeStrategy updated
DetailsAdditional event informationKey: new-checkout

Filtering the Audit Log

By Time

Arbitrary date range filtering is available.

By User

Shows every action by a specific administrator or developer.

By Resource

Full change history of a single flag — from creation to archival.

By Action Type

Creation, update, deletion, archival, authentication.

Combining Filters

Show all flag changes made by a developer in the last week — combine time, user, resource, and action filters.

Audit Log Storage

можно. stores the audit log in PostgreSQL. Entries are never modified — the audit log is an append-only store.

ParameterDefaultDescription
MOZHNO_AUDIT_RETENTION_DAYS365How long audit entries are kept

Entries older than this are automatically purged once per day.

Integrity

  • Entries are never edited after creation
  • Entries cannot be deleted via the dashboard (direct SQL only)
  • Each entry has a unique ID and microsecond-precision timestamp

Integration with External Systems

Configure a webhook for an event (e.g. flag.updated) to receive notifications on changes.

Next Steps

Released under the BSL 1.1 License.