Workspace- and project-level signed commit enforcement will allow admins to require valid, verifiable signatures across repositories in their scope. Bitbucket will reject commits that are unsigned or whose where signatures cannot be validated, helping teams apply their security policy consistently at scale. This is a Premium feature and is only available to workspaces on Premium monthly and annual plans.
We’re excited to share an important security capability rolling out in Bitbucket Cloud. Bitbucket is building stronger ways for administrators to protect source code by enforcing signed commits across an entire workspace or project, and by automatically signing commits created in the Bitbucket app. This was built on top of already available functionality to support GPG and SSH signatures announced previously.
What’s included
- Enforcement at scale: Workspace and project administrators will be able to require signed commits across all repositories in their scope. With hierarchical enforcement from a higher to lower level inheritance.
- SSH and GPG support: Bitbucket will validate supported commit signatures and reject commits when a signature is missing or cannot be verified.
- System-signed commits: Bitbucket will be able to automatically sign commits made through the Bitbucket UI or API. The signature will be associated with the Bitbucket system account, while the commit author remains the person who performed the action.
- Traceability: Administrators can maintain a more reliable audit trail for code changes and strengthen compliance evidence. Configuration changes are captured in the Atlassian Administration Audit logs (Atlassian Guard subscription required).
How this works
System-signed commits and enforcing signed-commits are separate settings, giving administrators control over how they secure commits created by Bitbucket and commits pushed by contributors. When enforcement is enabled at a workspace or project level, it is inherited by lower levels so the policy cannot be bypassed in an individual repository. If enforcement is later disabled at the higher level, lower-level settings can be configured again and retain their previous state.
Workspace admins can configure both settings from Workspace Settings

and Project Settings

Once enabled, all repositories within the project or a workspace will require a valid signature.
If the enforcement is enabled for the workspace, lower level enforcement at the project or repository level cannot be disabled.

To learn more, visit our help documentation.
Why this matters
For organizations that need dependable controls over their source code, enforcing signed commits will help prevent unsigned or unverifiable changes from entering protected repositories. It supports stronger protection against impersonation and makes the provenance of code easier to verify during security reviews and audits.

