Team Account Changes
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.
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 this||If 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:
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:
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:
At this point you will have to decide to keep or delete the temporary administrator account created to unlock your team.
Git/Mercurial local configuration
Frequently Asked Questions?
If your team is connected using Google, Facebook, Twitter or Facebook
You will need to disconnect this association. To do this, do the following:
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:
Continue to FAQ.
How do I 'manage' my team now?
After you log into Bitbucket:
|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:
|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?||
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.|
Was this helpful?
Thanks for your feedback!