If you are new to Git or Mercurial and want a thorough guide that covers setup through basic troubleshooting, check out our Bitbucket 101

Skip to end of metadata
Go to start of metadata

Recently, we announced that Bitbucket would be removing the ability to login using the 'Team' as an account. This article explains exactly what this means, why and how to get this done.

Background

Teams were introduced some time ago to allow people collaborate on code as a team. Teams were originally designed and intended to be administered by one or more members of the Administrators group, which was and is created automatically for all teams. While this was possible using an individual user account, there were limitations to the way profiles were displayed and accounts were managed. Now that we're ready to bring Atlassian account (and more new features) to Bitbucket, it is necessary to make a few changes to the way teams and user accounts function. Most of these changes were seamless for the vast majority of our users, however, the team conversion can be a complex process for some users.

That is where we are today; what follows will outline and explain exactly what steps to follow to ensure that you use an individual account, as part of an Administrators group, to manage your Team.

Log in as, or create, an administrator for your team

If you've received an email from us recently or see a message, like one of those in the following table, you'll need to follow this process. If you have not, there is nothing you need to do, you are using your Team as it was intended.

One of the following messages is shown to any user who is currently attempting to use the Team's id (or an associated email address) to log into Bitbucket.

Follow the instructions which are below the configuration you are presented with when you try to log in as a team.

If your team has administrators you will see thisIf your team has no administrators you will see this


 

If you see your own individual account in the list

Congratulations! You already have an Administrator account on this Team. Now do this:

  1. Click Log in.
  2. Be sure you log in using this administrator account in the future.
  3. Continue to FAQ.

If you do not see your account in the list

If you don't have log in credentials as an existing administrator you can request that one of the existing administrators of the team send you an invitation to join the team.

If you do not have an account associated with your (or this) team

You can do one of the following: 

  • Add a unique password and click Sign up. What we've done here is pull in the information from the team, including the team e-mail, added -admin (or some variant) to the name, and placed them into a signup form. Adding a password to this information will create a new Bitbucket individual account and automatically add this new account as an administrator to the team. This is the easiest way to get your own account, associate it with your team, and continue using the same e-mail to log into and manage your team.
  • Choose a different username, add a password, keep the email from the team. This will do the same thing as the previous option, but with a different username.

No matter which you choose the email address for the team will become the email for the newly created administrator account.

If you have an existing Bitbucket account you would like to make administrator of the team do the following:

  1. Complete the process above to create a temporary administrator account.
  2. Log in as the temporary administrator. 
  3. Click Teams>your team name.
  4. Click Manage team.
  5. Enter the username for the Bitbucket individual account you want to use to administer the team and click Add.
  6. Log out of Bitbucket.
  7. Accept the invitation to join the team you receive. 
  8. Log in using the newly created account. 

At this point you will have to decide to keep or delete the temporary administrator account created to unlock your team.



An important distinction on the difference between an account, login, and email address on your account. Many users use their email address as a login for their Bitbucket Team/user account. Be sure the username or email you are using to login is for a personal (individual) Bitbucket account and not one which is only associated with a team.

Git/Mercurial local configuration

Git/Mercurial local configuration

If you had to create a new individual account to log into Bitbucket. You might need to make some small modifications to the URL used to push/pull/clone, stored in your local repository's configuration file.

 Follow these instructions to modify your local Git or Mercurial

You can easily edit this in any text editor. You'll want to edit the 'USERNAME' portion as in the example below to be your new individual user id, as the team's login id will no longer work after 18 Feb. Do NOT edit any of the rest of the URL. Your repository path is based on the id of the owner of your repository, not the user who is authenticating to perform the push/pull/clone. 

For Git

In the "url = " line of the .git/config file, you'll want to edit the 'USERNAME' portion as in the example below to be your new individual user id.

For Mercurial (Hg)

In the "default = " line of the .hg/hgrc file, you'll want to edit the 'USERNAME' portion as in the example below to be your new individual user id.

If you manage your repository with SourceTree

  • Click Repository > Repository Settings
  • Then click edit on the pop-up.
  • Then edit the USERNAME portion as shown in the following screenshot

Frequently Asked Questions?

 

QuestionAnswerAdditional Details

If your team is connected using Google, Facebook, Twitter or Facebook

You will need to disconnect this association. To do this, do the following:

  1. Visit https://bitbucket.org/account/
  2. Choose Change password
  3. Ensure that you have a password set on Bitbucket.
    This may be a good time to update your existing password too!
  4. Then visit https://bitbucket.org/account/connected-accounts/
  5. Click the (X) next to allconnected accounts
  6. Then https://bitbucket.org/account/email/ and ensure that you've removed all your emails from the team as well
  7. Now you may continue to follow the guide near the top to setup your administrator account
 

What if I'm using another team to manage my team?

 You'll need to do the following

You'll need to do the following:

  1. Log out
  2. Log in as the team that is the administrator for your other team
  3. Follow the instructions above in "Teams with no administrator"
  4. Once you have setup an administrator for your first team, Log out again.
  5. Log in as the second Team
  6. Follow "If you have an individual account, but you don't see it".
    • Add your new individual user id to the second Team. The is the one you created to add to the first
  7. Now, log out again
  8. Log in as your new individual account.

Ensure you can administer all your teams from one account

After you log into your individual account, be sure you can see, and administer, both teams from your individual account by clicking Teams at the top of the Bitbucket page (see Whats next? for compete instructions). You should observe the team name for each team.

Continue to FAQ.

 

 

How do I 'manage' my team now?

After you log into Bitbucket:

  1. Click Teams>your team name.   
  2. Click Manage team, which will open the team management page where you can find all the settings for the team.

Teams and repos and groups

Manage groups

Where did my repositories go?

Most users will see their repositories right where they left them.

 

In a few rare cases, where the repositories created had no administrators group, you will have to do the following:

  1. Log into Bitbucket. 
  2. Select Teams>your team name.
    On the team overview page you will see a list of the repositories for this team.
  3. Go through each repository and add an administrator group with your personal Bitbucket account as a member of that group.

You should now be able to see the repositories in both your account view and the team view.

Repository privacy, permissions, and more

 

Manage groups

How do I create a repository for my Team now?

In the Create a new repository screen, simply select your team name from the Owner list. Which is the first field on the form.

 It looks like this

 

Create a repository
Do I need to move my repositories to my individual account?

No.

You can, and should, continue to use your repositories from the team account. This is one of the reason we created teams. As we improve how teams work to collaborate and integrate you'll want your repositories right where they are. In fact, you might even want to move repositories from your individual account to your team.

Change or transfer repository ownership
What about my SSH keys?Your SSH keys will continue to work for pushes, clones, and pulls after the 18 Feb cut off. However, if you are using this for your build process, may we suggest you try our Deploy keys feature.

Use the SSH protocol with Bitbucket

Use deployment keys

22 Comments

  1. Anonymous

    Here are a couple of comments on your docs:

    1. where is says 'Click View Administrators in the banner.', it no
    longer says that - it says "Set up Account" or something new now.

    2. I went through almost this exact same process several times previously.
    The thing that changed that I believe made it work for me this time is
    that I used a different id from my team id to sign in after I got the email
    invitation. That may be obvious to you guys that I need to not use the
    same id that the team is set to, but I did not even think about what my
    team id was - I just tried to use the same user id that I always use - and
    that I used when I originally set up my team.

    Anyway - I did make it through. thanks!

    1. Thanks for the feedback. I've made some adjustments to hopefully make this clearer.

  2. So, how do different team members make changes on the server? In other words, I create a repository using my individual user. I add content from my local installation and push the content. I then clone that repository on the development server, again using my individual account since team accounts are now gone. A team member clones the repo using their account, makes changes to the repository, pushes their changes and then wants to pull those changes to the development server, but the server asks them for MY password in order to do the pull. I guess we could constantly be changing the .git/config file, but that doesn't seem like a very good workflow. So, how do we make this work?

    1. As noted above in the FAQ, you keep the Team's repositories in the Team. The Team isn't going anywhere. We are only preventing you from logging in using the Team as a login id. Through Manage groups, each of your members of the Team have their own access to the repo, on the Team. They use their own login to access the repo. When logged in, each user sees their own clone URL. 

      Also noted in the FAQ above in the section labled "What about my Git/Mercurial local configuration? Does that change?", we provide instructions for how each individual member of a team should re-configure their local.

      Finally, for servers and deployments, this is the purpose of deployment keys and SSH keys. Setting up SSH on your server is the secure way to deploy without using a special 'deploy' user or the Team. We're not disabling the ability to have an SSH key in use on the Team for specifically this reason.

      If this doesn't cover all of your concerns, please come over to support.atlassian.com and open a ticket. We'll be happy to explain more in depth.

      1. Ah, yes, that all makes sense. Thank you for your quick response.

         

  3. How team's OAuth will work after changes are live?

    If you are permitting read/write access to private repos through your account, you are giving access to all your private repos as well, rather then the teams only.

    For that you needed to login as a team, which worked brilliantly as your repos were not shared.

    Now, I don't see how it can be achieved, or after you fully integrate Atlassian ID there will be some other way?

    Cheers. 

    1. For that you needed to login as a team

      Can you be more specific about which application(s) you are referring? For example, the DVCS Connector loads only the repositories from the account you specify when configuring. While it technically could access that user's data, it doesn't. 

      1. It was more about a general case for custom applications, but taking DVCS Connector as an example, the point that bothers me is that it could access user's data, because you have ensured it doesn't it might seem that it is alright, but really it leaves window for using those credentials to get access to users private repos.

        As another example I was testing Strider-CD, there is an integration with BitBucket which uses OAuth to request access, and later retrieve all repositories it has access to (quite common scenario and behaviour), a case where you want to share all teams repositories is more then common IMHO.

        But with this change, the only thing I can think of is creating a fake team member just to tackle those use cases.

        I don't know how many people use it for anything other then DVCS Connector, but it would be a shame to loose flexibility that OAuth provides for teams (sad).

        1. We're aware of this issue and are considering a different method to allow access to Team data over the API.

  4. I am part of the "small subset of users did not have an Administrator group on any of their repositories..." because I don't see any of my repos under the team account.

    Unfortunately this change coincided with our decision to move from Github to Bitbucket so I was importing many repositories. Due to my misunderstanding of things at the time, I believe I did this instead: 


    Do I need to move my repositories to my individual account?

    No! You can, and should, continue to use your repositories from the team account. This is the reason we created teams. See the section below on how to continue to access your repositories using your user id instead of the team id.


    So I believe I imported my repos to another individual account when I want them to be under the my team account. I see all my repos only under my newly created admin account. Unfortunately now I'm more confused than ever as to how to fix this. Any suggestions? Thanks.

    1. In the section above titled Where did my repositories go?! we explain that you should be able to see all of your repos from the Team's profile page. If you still aren't seeing them there, please come to support and we'll help clear up what happened.

      1. Just wanted to close the loop and let you know that I was able to re-read the section above and resolve my issue.

  5. Anonymous

    a) Can you make this process any more complicated or this page any more confusing?  My dev manager and I and spent two hours on this page and might have it figured out.  One issue is that nowhere does your warning banner say WHICH team is having the problem.  Is it my company's team, or is it the team that I apparently created, inadvertently, when creating a repository?

    b) How long does it take to get emails when you invite someone to add an account.  It's been an hour and I haven't gotten it yet (via gmail).

    1. Hello anon:

      a. The team is the account you have logged in to. A simple way to find out would be to click the User menu at the top -> Manage account. The URL in your address bar will show your currently logged in login id (username).

      b. This is instant. If you don't see an email, please check your spam filters/folders. Especially if you are behind a corporate email filter. Many emails seem to get trapped there.

      Finally, if we haven't made it clear, please tell us in support.atlassian.com. We want to improve our guides if they have left you astray!

  6. This is so horrible annoying!

    Why do I get this stupid banner, since weeks?

    It shows two administrator accounts and I am using only them to log in.

    "Set this up now" does nothing besides hiding and then sliding in the banner again.

    When I tried to add a comment here I had to login again even when I am already logged in on Bitbucket.

    It seems your account management has no idea what it's doing at all.

    Reading this article didn't help.

     

    1. Hi Günter,

      It sounds like one of your logins is actually a team. Please email support@bitbucket.org with the Team login id (not email) and your administrator's username (not email). We will help you get all sorted out.

  7. Anonymous

    Okay, this doesn't make sense .... our team account login is also the one attached to our Atlassian ID which has a subscription.  If I log in as my team administrator, that complains about how I have too many users, and I need to sign up for a plan.  The problem is, I can only create the repos on the original team account login ........ so ... what do I do?

    1. Atlassian ID is presently not in any way connected to Bitbucket. The Team changes we are working on will enable us to bring it to you later this year. If you have more questions, we're happy to help in support. Please come over with your Team's id (not email) and which email you use to log in. We'll help you sort the rest.

  8. Anonymous

    So what are we supposed to with accounts that are inaccessible because BitBucket OAuth no longer works to log in on another website using a team account?

     

    Old flow: Click `log in with BitBucket` on third-party site → log in on BitBucket → become authenticated with third-party.

    New flow: Click `log in with BitBucket` on third-party site → get error message from BitBucket upon trying to log in → third-party account now inaccessable.

    1. For the time being, you'll need to use an account associated with your team that has appropriate permissions. Any user account in the Administrators group should have access to all the repositories and functions that the team may have had previously. We do understand this may be an issue for some use-cases and will be addressing it again in future changes to teams.

  9. Anonymous

    Is there anyway to "unhook" the email used for the team account so it can be used for a normal account.  As the team administrator I cannot send an invite email to the user whose email is tied to the team account.  Is the only option for this user to use another email address?

    1. I believe you should see an symbol on the line for any email addresses associated with the team when it was originally created. You can click that x to remove the email and then send an invitation to the email address.

      1. Go to Teams>your_team
      2. Click Manage team
      3. Click Email addresses 
      4. Remove the addresses (or address) from the list.

      Some things to consider:

      • If there are several addresses, and the one you want to remove is listed as the primary address, you might have to remove the other addresses to enable the final address to be removed. 
      • Notifications for team members can be managed individually (Manage Inbox and email notifications) rather than as part of the team (using the team email addresses)
      • We no longer support adding email addresses to teams the way we did previously.

      I hope this helps.