Audit log of organisation changes

• For members and viewers, Sequential hides the Audit log tab, the Audit log item in the account menu and the Recent changes card. Sequential also refuses their requests for the log.
• The app shows the log of the organisation of the project that is selected in the project switcher. If you belong to several organisations, switch to a project in the other organisation to see its log.
• No one can edit or delete an entry. Entries do not expire. No setting controls how long Sequential keeps them.
• Sequential removes entries only when the organisation is deleted.

Everyday use makes no entry. These actions make no entry: watch a replay, run an Ask search, apply a saved filter, funnel or flow, give feedback on a verdict, or set a verdict on a finding.

Sequential records only changes that succeeded. A wrong password, a rejected save or a cancelled Loosen masking? confirmation makes no entry. Sequential never writes passwords, tokens or one-time codes into an entry.

Sequential does not record these:

• creating an account
• regenerating backup codes
• changing your profile name
• declining an invitation
• failed sign-in attempts

Account actions have no action code in this table.

Sequential also records account actions: sign-in, sign-out, password changes and resets, and two-factor codes. The two-factor codes include the code that turns on two-factor. Turning off two-factor and revoking sessions are account actions too.

Sequential files an account action under the organisation that the person's session had selected at that time. A new sign-in has no selected organisation yet, so sign-ins normally do not reach your log. An empty log still shows "Sign-ins, membership and project changes are recorded here."

Account actions other than sign-in, such as a password change or a sign-out, reach an organisation's log only in these cases. Earlier in that same sign-in, the person did one of these:

• created the organisation
• accepted an invitation to it
• used the project switcher to move into it from another organisation

Do not use the log as a sign-in history.

• Only owners and admins see the card.
• The card lists entries as sentences, as in the audit log. These are creation, detail saves, archive and restore, recording settings and rubric changes. An entry that has no sentence shows its action code.
• Changes to saved filters, funnels and flows do not show on the card. Find them in the audit log.

• Why some logs cannot be opened: the project switcher lists only live projects. An organisation can have only archived or deleted projects. If you also have live projects in another organisation, you cannot select that organisation. So you cannot open its log from the app.
• Project names: recording and rubric entries carry a version and details only. Key entries carry a project_id chip. It is the same id as in the address of that project's settings.
• Details saves: the chips show the values after the save, not before.
• Removals and cancellations: "removed a member" has only the member's id, in a memberIdOrEmail chip. "cancelled an invitation" has only an invitationId chip.

• Names come from your current member list. A person who left the organisation shows as a short id.
• If no person and no support staff made the change, the entry starts with "System".
• If Sequential support made the change, the entry starts with "Sequential support".
• The app shortens long ids in chips to 8 characters. To see the full value, hover over the chip.
• The count beside the title is the number of loaded entries. It shows a "+" while there are more.
• release.created has no sentence. The row shows "System", then the raw action code.
• release.created, the three project.saved_view_* codes, finding.dispatched, the three finding.draft_* codes, the two dispatch_target.* codes, organization.retention_cap_exempt_changed and project.retention_cap_exempt_changed show in the All actions menu only when a loaded entry uses them, as their code under Other. The other actions always show in the menu, in words. The menu always lists twelve billing actions under Billing: the two for support packs, and ten for paid packs. The menu also always lists five actions of claude.ai connections under Agents and tokens. It does not list oauth.consent_denied: Sequential records a Deny without an organisation, so no organisation's log shows it.

• access_token.created: project_id, name and scopes.
• access_token.revoked: project_id, name, scopes and kind. kind is pat for the tokens that you create, and oauth for a claude.ai connection. A revocation by Sequential support also has kind.
• oauth.consent_granted: client_id, redirect_host, project_id, grant_id, scopes, preset and step_up. step_up is totp_or_backup or not_enrolled.
• oauth.grant_revoked, oauth.refresh_reuse_detected and oauth.revoked_by_client: project_id, kind, reason and client_id. When the connected app ends only one of its access credentials, oauth.revoked_by_client also has token_kind.
• These entries never hold the token itself.
• release.created from a token: token_id, project_id, version, environment and commit_sha. The entry has no person as actor.
• finding.link_added: number, kind and url. From a token, also token_id, and the entry has no person as actor.
• finding.link_removed: number and url.
• finding.handed_off: number and via, and from a token also token_id. via tells how the finding was handed off: copy, issue, rest or mcp. The app shows via as a chip only on this action.
• finding.dispatched: number, kind (issue, prompt or webhook) and outcome, and failure when a webhook send failed.
• finding.draft_requested: number and token_id. finding.draft_approved: number, kind, outcome, and failure when a webhook send failed. finding.draft_declined: number. None of them holds the brief or an address.
• billing.pack_granted: pack, sessions and expires_at. billing.pack_revoked: pack.
• organization.retention_cap_exempt_changed and project.retention_cap_exempt_changed: retention_cap_exempt and previous, each true or false.
• dispatch_target.updated: project_id and enabled. dispatch_target.rotated: project_id and generation. Neither holds the webhook address or the secret.
• From a token, a finding entry starts with "System", for example "System linked a fix to F-12".
• project.saved_view_created, project.saved_view_updated and project.saved_view_deleted: kind, name and project_id, then before and after. kind is filter, funnel or flow. before and after hold the name, the conditions or steps and the version, as raw JSON. A save has no before and a delete has no after. So the log keeps the conditions of a deleted item, including any values in them.

See Findings and fixes.

• version: the settings version that this save created. The Session replay tab shows the current version and who saved it.
• diff: each setting that changed, as its path with the value before and after. For example: {"/replay/masking/mask_all_inputs":[true,false]}.
• loosened_masking: true if the save made recording less private. To save it, the person typed the project slug into the Loosen masking? sheet.
• loosening: what the person confirmed. For example: "inputs are no longer masked".

1. Open Settings → Audit log.
2. From All actions, choose Member invited. Each entry reads like "Ana invited bo@example.com as admin". A resent invitation adds another entry.
3. To see when people accepted, choose Member joined.
4. To see later role changes, choose Member role changed. For example: "Ana changed Bo's role to viewer".
5. To see cancelled invitations and removed members, choose Invitation cancelled or Member removed. These entries do not name the person. See Limits.

1. Open the project's Overview. In Recent changes, look for "changed the rubric" or "reset the rubric to default".
2. Click Audit log. From All actions, choose Rubric changed or Rubric reset to default. Entries read like "Ana changed the rubric to v4 (2 questions changed)".
3. To see which questions changed, read the summary chip. It lists the ids of the questions that were added, removed and reworded.

About the version and the count:

• The version in the entry matches the version in the "Customised · v4 · …" stamp on the project's Insights tab.
• The count is the number of questions added, removed or reworded. If you turn off a question, it counts as removed.
• If no questions were added, removed or reworded, the entry has no count.

As the rubric editor says, a rubric change applies to sessions judged after the change. Sequential does not re-judge old sessions in bulk. See Customise the rubric.

A new project gets one default key per source. A staging or development project also gets its first recording-settings version, v1. None of these has its own entry. Sequential records only project.created.

So a staging project's Session replay tab can show v1 and who saved it, with no project.config_changed entry to match.

• Watch shows different sessions this week. Did someone edit the rubric?
• PostHog events stopped. Did someone revoke the key, or archive the project?