Team Account Changes
This Knowledge Base article is written specifically for the Atlassian Cloud platform. Due to Functional differences in Atlassian Cloud, it is not applicable to Atlassian Server products.
Bitbucket has removed 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 to 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:
- Click Log in.
- Be sure you log in using this administrator account in the future.
- Continue to FAQ.
If you do not see your account in the list
If you don't have login 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:
- Complete the process above to create a temporary administrator account.
- Log in as the temporary administrator.
- Click Teams>your team name.
- Click Manage team.
- Enter the username for the Bitbucket individual account you want to use to administer the team and click Add.
- Log out of Bitbucket.
- Accept the invitation to join the team you receive.
- 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
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.
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.
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.
[remote "origin"] url = https://USERNAME@bitbucket.org/TEAM_ID/REPO_SLUG fetch = +refs/heads/*:refs/remotes/origin/*
In the "default = " line of the .hg/hgrcfile, you'll want to edit the 'USERNAME' portion as in the example below to be your new individual user id.For Mercurial (Hg)
[paths] default = https://USERNAME@bitbucket.org/TEAM_ID/REPO_SLUG
Click Repository > Repository SettingsIf you manage your repository with SourceTree
- Then click edit on the pop-up.
- Then edit the USERNAME portion as shown in the following screenshot
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:
- Visit https://bitbucket.org/account/
- Choose Change password
- Ensure that you have a password set on Bitbucket.
This may be a good time to update your existing password too!
- Then visit https://bitbucket.org/account/connected-accounts/
- Click the (X) next to all connected accounts
- Then https://bitbucket.org/account/email/ and ensure that you've removed all your emails from the team as well
- 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:
- Log out
- Log in as the team that is the administrator for your other team
- Follow the instructions above in "Teams with no administrator"
- Once you have set up an administrator for your first team, Log out again.
- Log in as the second Team
- 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
- Now, log out again
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 What's 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:
- Click Teams>your team name.
- Click Manage team, which will open the team management page where you can find all the settings for the team.
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:
- Log into Bitbucket.
- Select Teams>your team name.
On the team overview page you will see a list of the repositories for this team.
- 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.
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.
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 reasons 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.
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.