Audit

When something changes — a deploy goes out, a member's role is updated, a secret is rotated — you'll sometimes need to know exactly who did it and when. The Audit view is that record: a time-ordered log of the significant actions taken across your project.

Annotated screenshot of the Audit view: a chronological list of entries, each with an actor (name/avatar), an action ("Deployed production", "Added member", "Updated secret"), and a timestamp, with a filter bar above. Callout: "Who did what, when — in one searchable timeline."

What gets recorded

The log captures the significant actions taken in your project — the kinds of changes that matter for safety and accountability, such as deployments and changes to your project's setup. Each entry tells you who (the person or, in automated cases, the system), what they did, and when.

Finding what you need

Entries are newest-first, and you can filter the timeline to narrow in — by the kind of action or the person who took it. So "who pushed to production on Tuesday?" or "what has this teammate changed?" is a quick answer, not an investigation.

The audit log is your answer to "what just changed?" — and your paper trail when you need to show what happened, in order, after the fact.

Why it matters

• Accountability. Every meaningful change is attributed to someone.
• Debugging. A surprising change in behavior often lines up with an entry here — start with "what changed and when."
• Trust. When you work as a team, everyone can see the history rather than relying on memory.

Where to go next

• Logs — runtime logs from your functions, for tracing behavior.
• Deployments — the deploy and rollback history in detail.
• Members — who's on your team and what they can do.