Clearer audit activity in the console

Audit logs only help if you can read what just happened. Console audit views now present recent authentication and administration activity with clearer summaries, clearer action descriptions, and time-range controls that are easier to explore.

This is the longer note behind the June 20 changelog entry.

How it works

The change is presentation and navigation, not a new event catalog:

• Summaries show the activity at a glance instead of a raw payload first
• Action descriptions name what was recorded in language that matches the console action
• Time-range exploration lets you narrow to the window you care about, then expand

Environment logs still cover identity activity; organization logs still cover organization-level changes. Filter and field behavior is in Audit logs.

Set it up

No migration. In the Authdog console, open Audit:

1. Select the project and environment (or the organization stream).
2. Set a narrow time range around the incident or change you are inspecting.
3. Read the summary and action description before opening the JSON payload.

Start from a known user or action, then widen the range. Older events keep the text they were written with.

Trust boundaries

Audit records what the control plane already did. A clearer label does not grant access and does not prove an action never happened if you are looking at the wrong environment or time range. Keep organization and environment streams separate.

Do not treat this UI pass as the later event-category expansion. Category catalogs can grow in later releases; this note is the readable activity view.

Try it

Open Audit and inspect a recent sign-in or admin change. Query details are in Audit logs. The original release note is in the changelog.