Audit log

Updated

The audit log records who changed what in your projects and your account: members and roles, API tokens, branches and merges, imports, settings, sign-ins and more. Every entry says who did it, what they did and when. Entries can't be edited or deleted, and they are kept for as long as your plan says.

Where to find it

ViewWhere in the appWho can see it
Project audit logProject Settings → Management → Audit logProject admins and owners
Security activityProfile → SecurityYou, for your own account
Recent activityThe project's Analytics pageProject admins and owners

The project audit log is the full view: a table of every entry for the project with filters and, on Professional and Agency, CSV export. Other members who open it see a note to ask a project admin or owner for access.

Security activity lists the sign-ins and changes to your own account, with the time and IP address of each, newest first.

Recent activity on the Analytics page shows the latest project entries at a glance, without IP addresses or details.

Workspace changes – members invited, removed or given a new role, invitations accepted or declined, a workspace deleted – are recorded for the workspace. In the app you see the ones that involve a project: when a project is added to or removed from a workspace, that entry appears in the project's log.

What is recorded

The log covers access and security, and actions on a project as a whole or on its integrations. Edits to a single translation are not in the audit log – each label's History shows those.

AreaRecorded actions
MembersA member invited, their role changed, a member removed.
API tokensA token created, updated or revoked – including the tokens the GitHub App manages.
Branches and mergesA branch created, deleted or merged, with the source, target and how many keys changed. A merge approved despite a blocking quality gate, with the written reason.
LabelsLabels imported (format and counts), deleted in bulk, or exported from the app.
ProjectProject settings changed (which settings, not their contents), languages added or removed, the project deleted.
WebhooksA webhook created, updated or deleted.
GitA Git repository connected or disconnected.
GitHubA repository linked to the GitHub App, its connection changed, or unlinked.
DeliveryA delivery distribution created, changed or deleted; a release published or rolled back; an automatic publish that failed.
Quality checksA quality finding ignored, with its reason when one was given, or no longer ignored.
ScreenshotsA screenshot capture run finished, a screenshot deleted.
WorkspaceA project added to or removed from a workspace (shown in that project's log). Workspace members invited, removed or given a new role, invitations accepted or declined and a deleted workspace are recorded for the workspace.
Sign-in and securityYour account, in Security activity: account created, signed in, failed sign-in attempts, account locked after failed sign-ins, two-factor authentication turned on or off, password changed or reset.
BillingYour account, in Security activity: plan changed, team seats changed, delivery request blocks changed.

What each entry shows

ColumnWhat it holds
TimeWhen it happened.
ActorWho did it: a person (by name), an API token, the GitHub App, or Translatize itself for automatic actions.
ActionWhat happened, in words – for example "Branch merged".
TargetWhat it happened to: a member, a token, a branch, a distribution and so on.
DetailsA few facts about the change, such as the new role or the merge target.
IP addressWhere the request came from, when there was one.

The log never stores passwords, API token values or the text of your translations. It says what happened, not what a label says.

Filters

Above the project audit log you can narrow the list by:

  • Area – one of the areas in the table above, such as Branches and merges or API tokens;
  • Action starts with – an action name or the start of one, for example branch.merge;
  • Actor ID – everything one person or one API token did;
  • From and To – a date range, both days included.

Entries are listed newest first; Load more at the bottom fetches older ones.

Retention

PlanEntries kept forCSV export
Free30 days–
Starter90 days–
Professional180 daysYes
Agency365 daysYes

Retention follows the plan of the account that pays for the project – the project owner, or the workspace owner for a project in a workspace. Entries about your own account follow your own plan.

Each entry's retention is set when it is written. After an upgrade, new entries are kept for the longer period; entries written before keep the period they started with. Once an entry's time is up, it is removed automatically.

CSV export

On Professional and Agency, Export CSV on the project audit log downloads the entries that match your current filters, newest first. The file has one row per entry with the time, action, actor, target, project and workspace, IP address, browser or client, and the details. It opens directly in a spreadsheet, accents and all.

On Free and Starter, the button shows a note that export is part of Professional and Agency, with a link to the plans. Viewing and filtering the log work on every plan.

Entries can't be changed

The audit log is append-only. Nobody can edit or delete an entry – not project owners, not workspace owners, not API tokens. Entries leave the log only when their retention period ends.

Overrides are always on the record
An admin or owner can merge past a blocking quality gate only by writing a reason. The reason and their name go into the audit log, so every override can be traced later.