The central record of mutations, how to filter it, and how support sessions and entity links are represented.

Activity and audit trail

Activity is the answer to “what changed, who changed it, and when?” Every successful mutating API request is recorded centrally, so a connector or screen does not get to opt out of the audit trail accidentally.

Two useful scopes

• This project shows every member's activity for the selected project when you hold view-all-activity.

• Mine follows the signed-in operator across projects.

Search and action filters are applied to the feed, and timestamps show both a readable age and the exact wall-clock time. Entity references are links where the target still exists, letting you move from an audit row to the project, resource, connection, job, pipeline or other object it describes.

The record includes the route-shaped action, entity type and identifier, project when applicable, actor and timestamp. Organization-wide changes correctly have no project rather than being attached to whichever project happened to be selected in the browser.

Support and automated activity

An action performed during a platform support impersonation session names both the support session and the operator identity being acted as. Scheduled collectors and assessments use a fixed system actor rather than pretending a person initiated them.

The feed is evidence, not an undo log. Use it to establish what happened before deciding how to repair or reverse the provider-side result.