Set email preferences

This page is specific to Bitbucket Cloud users who don't access Bitbucket using an Atlassian account. If you aren't sure whether you have one, go to your avatar in the top-right corner. If you see a Manage account option, you have an Atlassian account. In that case, go to the Set email aliases page instead.

Bitbucket Cloud lets you associate multiple email addresses with an account. These email addresses work site-wide. So, if your local DVCS username/email configuration uses any address on this list, Bitbucket automatically associates those with your account. Other Bitbucket users can find your account by any registered email address when searching for accounts or users.

You designate one address is the primary account address. Bitbucket sends email notifications to this address. You can change your primary address by clicking set as primary on any of your confirmed email addresses. This page contains the following topics:

Google as your primary email

If you've been logging into Bitbucket with your Google email address, and it wasn't your Bitbucket primary email address, it'll now be your primary. In the future, you'll only be able to log into Bitbucket with your primary email address, so we've updated your Google email address on your Email adresses page to primary.

If you don't want your Google account to be your primary account, you can change it back by clicking set as primary next to the address you want on the Email addresses page. However, once you've done this, you'll no longer be able to log in to your account using Google because your primary email and your Google account won't match.

Email addresses and commits

To map your username to a commit, push, and other activities, Bitbucket Cloud requires that the email address you commit with matches a validated email address on an account. On your local system, where you commit, both Git and Mercurial allow you to configure a global username/email and a repository specific username/email. If you do not specify a repository specific username/email values, both systems use the global default. So, for example, if your Bitbucket account has a validated email address of, you need to make sure your repository configuration is set for that username. Also, make sure you have set your global username/email address configuration to a validated email address.

If the global default is not configured or if you have not validated your email address, the committer appears as unknown for your Bitbucket activities. Also, if you have multiple Bitbucket accounts, you may mistakenly commit your code under an email address that maps to an account name you did not intend. To have the existing commits on a repository map to a different account, you can use  Username aliases for the repository in question. Aliases are per-repository. To set up an alias for a repository, you must have admin rights on it.

For information on configuring your local repository or configuring aliases, see Set your username for Bitbucket Cloud actions.

Confirming email addresses

When you register a new email address with your account, Bitbucket sends you an email containing a confirmation link. Until you confirm that address, Bitbucket cannot display your account name with your commits properly and other users cannot find you by that email address. Otherwise, Bitbucket performs as it normally would. If you have not confirmed your email address, a banner appears across the top of Bitbucket when log in:

If you've misplaced or your confirmation has expired, do the following:

  1. Select avatar > Bitbucket settings. 
    The Manage page appears. 
  2. Select Email addresses.
  3. Click the resend confirmation link next to the address.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport