Audit log

Once more than one person has access to your Flow instance, "who redeployed production at 2am" stops being a hypothetical question. The audit log is where you go to actually answer it, a plain, reverse-chronological record of the meaningful things people did.

What it shows

Each entry is who did it (by email), what they did, what it was done to, and when. There's no filtering or search box, it's a straightforward list of the most recent entries, which is usually exactly what you want when you're trying to reconstruct what just happened rather than mining old history.

Actions that get logged include things like:

• Creating a project, or granting or revoking someone's access to one.
• Redeploying, reloading, rebuilding, rolling back, stopping, starting, or deleting a service, along with changes to its provider or build settings.
• Creating, deleting, or manually running a schedule.
• Inviting, removing, or changing the role of a team member.
• Adding a node.

Worth being upfront about: this isn't a log of literally everything. Routine things like editing environment variables or connecting a Git provider aren't currently captured here, the log is aimed at the actions with the biggest blast radius, deployments, access, and team membership, rather than every possible click in the dashboard.

Who can see it

Only org owners and admins, it isn't visible to members at all. That's consistent with everything else about roles in Flow, see Team and permissions, the audit log is itself something only the people already trusted with broad access get to read.