Not receiving Bitbucket Cloud repository invites on primary email, but works with +alias

[Azhar Sheikh]

Hi everyone,

I’m facing an issue with repository invitations in Bitbucket Cloud and would appreciate any guidance.

My manager is trying to invite me to a repository where the rest of my team already has access. However, I am not receiving the invitation email on my primary email (azharuddin.sheikh@ksolves.com).

What’s unusual:
- If the same invite is sent to a variation like azharuddin.sheikh+ma@ksolves.com, I receive the email without any issues.
- This suggests that email delivery is working in general, but something is preventing emails from reaching my main address.
- I already have an Atlassian account associated with my primary email (used with Trello).

Things I’ve checked:
- Spam/junk folder — nothing there
- Alternate email (+alias) works, but primary does not

Questions:
- Could this be related to how my Atlassian account is configured?
- Is there any known issue with email delivery for primary vs alias addresses?
- Could this be due to an existing account state?
- Any steps I can take to troubleshoot or resolve this?

Thanks in advance!

[Arkadiusz Wroblewski]

Hello @Azhar Sheikh 

I’d be careful about sticking with that +alias as a permanent fix, because Bitbucket will treat it as a totally separate identity, which can lead to a real headache with permissions and SSH keys later on. Usually, when the primary email isn't getting the invite but an alias is, it's either because you're already in the system or your address has been suppressed.

First, have your workspace admin check the user directory to see if your primary email is already listed. If you’re already part of the workspace, Bitbucket often won't trigger a new invitation email even if the admin tries to send one; in that case, they just need to add you to the specific repository permissions instead of "inviting" you to the whole site again. You should also head over to id.atlassian.com and double-check that your "Product Invitations" are actually enabled under your email notification preferences.

If you're definitely not in the directory and your settings are correct, it’s likely that your primary email ended up on an internal suppression list due to a past bounce. Ask the admin to fully delete any pending invite for that address and send it fresh. This specific action often clears the suppression automatically.

If that still doesn't work after a fresh resend, you'll probably need to reach out to Atlassian Support to have them manually scrub your primary address from their backend bounce list.

[Azhar Sheikh]

Thanks for your reply, No I am not using +alias as permanent fix, I just added this to see if I am even getting notifications or not.

[Nikola Perisic]

Hi @Azhar Sheikh 

Your email was added to the supression list from the Atlassian's side. If you have a higher tier than Free, you can create a support ticket for them to remove you from that list. If not, I will create that request.

[Azhar Sheikh]

Thanks for the comment @Nikola Perisic I'd be more than happy if you would create request to remove me from "supression list".

[Nikola Perisic]

Done