Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ Currently, the integration between Codacy and Bitbucket Cloud has the following
- **Repositories that are moved between teams are not automatically transferred between Organizations on Codacy.** You must manually delete these repositories from their source Organization and add them to their new Organization.
- **Codacy only sends commit and pull request notification emails to the authors of the commits and pull requests.**
- **Codacy doesn't analyze pull requests submitted from forked repositories.**
- **Atlassian asks you to grant Codacy access every time you log in to Codacy with Bitbucket.** This is a change on Atlassian's side that Codacy can't turn off. See [why Bitbucket asks you to grant Codacy access every time you log in](../troubleshooting/why-does-bitbucket-ask-me-to-grant-codacy-access-every-time-i-log-in.md).

## See also

Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
description: Atlassian shows its permissions page every time you log in to Codacy with Bitbucket. Learn why, and how to tell Atlassian it affects your team.
---

# Why does Bitbucket ask me to grant Codacy access every time I log in?

When you log in to Codacy with Bitbucket, Atlassian shows a page asking you to grant Codacy access to your account. Since late July 2026, this page appears on every login, even if you granted access before.

This is a change on Atlassian's side, and Codacy can't turn it off. Atlassian now handles Bitbucket logins through its own identity platform, which asks for consent on every authorization. Other apps that log in with Bitbucket show the same behavior.

To keep using Codacy, and to help get this fixed:

1. Review the permissions and accept them to continue. Codacy requests the same permissions on every login. See [which permissions Codacy needs from Bitbucket](../../getting-started/which-permissions-does-codacy-need-from-my-account.md#bitbucket-cloud).

1. Let Atlassian know this affects your team. Reports from affected customers show Atlassian how widespread the problem is:

- Reply to the [report on the Atlassian Developer Community](https://community.developer.atlassian.com/t/bitbucket-cloud-oauth-consent-screen-shown-on-every-authorization-consent-no-longer-remembered/102357).
- If your company has an Atlassian subscription, [contact Atlassian Support](https://support.atlassian.com/contact/) and say that the Bitbucket Cloud OAuth consent screen is shown on every authorization since late July 2026.

Codacy has reported this to Atlassian (request BBS-257159). If you contact Atlassian Support, mention this request so Atlassian can link your report to it.

If you have other problems logging in to Codacy with Bitbucket, please contact us at <mailto:support@codacy.com>.
1 change: 1 addition & 0 deletions mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -754,6 +754,7 @@ nav:
- faq/troubleshooting/we-no-longer-have-access-to-this-repository.md
- faq/troubleshooting/why-is-my-file-over-150-kb-missing.md
- faq/troubleshooting/error-line-endings.md
- faq/troubleshooting/why-does-bitbucket-ask-me-to-grant-codacy-access-every-time-i-log-in.md
- special-thanks.md
- Developer tools:
- Codacy dev tools: "developer-tools/index.md"
Expand Down
Loading