Feature
Product Update: Environment-Scoped Audit Logs and Tag Attribution
Audit logs now show which environment each action occurred in, tags are attributed to who added them, and settings navigation has been restored.
Summary
Audit logs now show which environment each action occurred in, tags are attributed to who added them, and settings navigation has been restored.
Environment-Scoped Audit Logs
The audit log now includes the environment where each action took place. You can see at a glance whether a deployment, token change, or configuration update happened in development, staging, or production — without having to cross-reference separately.
- Audit log entries show the specific environment context for each event
- Makes it easier to investigate incidents by filtering to the environment where something went wrong
- Helps teams with multi-environment setups maintain clearer accountability
Tag Attribution
When tags are added to applications or versions, the audit log now records who added them. This gives teams a clearer picture of how labels and categorizations evolve over time.
- Know exactly who tagged a version or application and when
- Useful for compliance and review workflows where label changes need to be traceable
What This Means for Teams
- Teams managing multiple environments can now trace actions to their exact environment context in the audit log
- Tag changes are now part of the audit trail, adding accountability to how your applications are labeled and categorized
- Navigation to settings and project pages is reliably consistent again