What to check first
Use a test repository to confirm which changes require a reviewer and ensure another workspace administrator can restore access.
KeySigner setups
- Test a Bitbucket Cloud browser sign-in code →KeySigner on iPhone or Mac with Sign-in codes
KeySigner setup requirements →
Provider availability
Blocking merges when checks fail. Requires Bitbucket Cloud Premium. Check provider requirements →
Provider walkthroughs
- Check who can merge a code changeFind the review decision for a specific revision and check what allows it to land in Bitbucket Cloud, Azure Repos, Gerrit or SourceHut.
- Replace retired credentials for Bitbucket, npm, and PyPIFind out which credentials stopped working, what replaces them, and how to check repository access or package publishing before changing a live workflow.
What it covers
Protecting a maintainer account does not change permissions already given to build credentials.
Troubleshooting
Is a signed change rejected when you push it?
Check the signed-commit requirement on the exact repository and verify that Bitbucket can associate the signature on the rejected commit with a known key. If Bitbucket rejects the credential before you reach that check, note that app passwords stopped working for Git over HTTPS and API requests on July 28, 2026.
Replace retired credentials for Bitbucket, npm, and PyPI →
Check Bitbucket status for reports on Bitbucket Cloud.
Documentation and support
Bitbucket documentation
Check requirements for signed commits