β‘οΈπ New Event Exclusion Setting πβ‘οΈ
π Hey Community! Elana here today from the Audit Log team with some super exciting news: starting November 3, 2025 PST , organization admins will have the power to control App Activity Logs with a new 'Event exclusion' setting in Audit log!
What does this mean?
Previously, Audit log automatically stored third-party Confluence and Jira app API requests for all Cloud Enterprise and Atlassian Guard Premium customers. With the new Event exclusion setting, organization admins will now have the ability to decide whether they want to store these logs. Starting December 1, 2025, these two logs will be disabled by default for all organizations. Organization admins can enable/disable either of these log types in the new βEvent exclusionβ setting tab.
How does it work?
-
A new toggle will be available in the Audit Log settings under the βEvent exclusionβ tab starting November 3, 2025.
-
Organization admins can configure these settings at any time after this date.
-
On December 1, the default off setting will be enforced. For any organization admin who does not configure their settings by this date, the default will be set to βoffβ and these two logs will not be stored.
-
These logs will start being collected automatically as soon as the setting is enabled.
When will this be available?
The new Event exclusion setting will be available to all Cloud Enterprise and Atlassian Guard Premium customers starting November 3, 2025. This new default βoffβ setting will be enforced starting December 1, 2025, and will affect UI, Webhook, and API Audit log usage.
We want to hear from you!
Weβd love your feedback, so please feel free to reach out to eagarwal2@atlassian.com or drop a comment on this post to schedule time to chat π
