Bitbucket Cloud audit log events
Audit logs are available to Bitbucket customers when you subscribe to Atlassian Guard. If you do not already have an Atlassian Guard subscription, you can follow the steps to get started with an Guard evaluation to start a free 30-day trial.
Customers will also need to link their Bitbucket workspace(s) to their Atlassian organization in order to enable the audit logging. To link your Bitbucket workspace and enable audit logging, follow the steps in the Add a new product to your organization documentation.
The Bitbucket Cloud audit log tracks key activities that occur within a workspace. These activities can be used to diagnose problems or answer questions related to workspace, project, and repository administration and configuration changes, as well as to managed user details.
Audit log events will be rolled out incrementally, which means that not all events below will be available at this time. However, this list encapsulates what Bitbucket is working towards.
The following table provides a list of events categorized by container.
Category | Event |
|---|---|
Workspace | Workspace created |
Workspace deleted | |
Workspace id changed | |
Workspace name changed | |
Workspace privacy changed | |
Allowed private content in workspace | |
Disallowed private content in workspace | |
User invited to workspace | |
User accepted invite to workspace | |
User added to workspace | |
User removed from workspace | |
User added to group | |
User removed from group | |
Group created in workspace | |
Group deleted in workspace | |
Group workspace member permissions changed | |
Group repository access permissions changed | |
Group access to repository changed | |
Removed group access to repository | |
Workspace 2SV requirement enabled | |
Workspace 2SV requirement disabled | |
Workspace IP allowlisting enabled | |
Workspace IP allowlisting disabled | |
Workspace IP allowlisted addresses changed | |
Repository transferred from workspace | |
Repository transferred to workspace | |
Project created | |
Project deleted | |
Project updated | |
Project key changed | |
Project name changed | |
Project privacy changed | |
Project Access key added | |
Project Access key removed | |
Development branch changed | |
Production branch changed | |
Default merge strategy changed | |
Default reviewers changed | |
Repository added to project | |
Repository created | |
Repository deleted | |
Repository updated | |
Repository name changed | |
Repository privacy changed | |
Main branch changed | |
User access to repository changed | |
User access to repository removed | |
Repository Access key added | |
Repository Access key removed | |
Username alias added | |
Username alias removed | |
Branch restrictions added | |
Branch restrictions removed | |
Branch write access changed | |
Branch merge access changed | |
Inherited project settings for branching model enabled | |
Inherited project settings for branching model disabled | |
Default merge strategy changed | |
Webhook added | |
Webhook removed | |
Repository link added | |
Commit message issue key requirement enabled | |
Commit message issue key requirement disabled | |
Default reviewers changed | |
Default pull request description changed | |
Default tasks changed | |
Files excluded from pull request diff changed | |
Slack notification rule added | |
Slack notification rule removed | |
User | Username changed |
User account deleted | |
User account access granted to an application | |
User account access to an application revoked | |
App password added | |
App password removed | |
SSH key added | |
SSH key removed | |
2SV enabled | |
2SV disabled | |
Security key added | |
Security key removed | |
Recovery codes viewed | |
Profile settings changed |
If you are encountering issues following this documentation - please raise a support ticket or a community support ticket for further assistance.