Important Changes Are Coming to Teams

By on January 14, 2014

Starting February 18, 2014, Bitbucket will remove the ability for individuals to log into a team with a username/email and password. We are taking this action so that we can bring you Atlassian ID later this year. Atlassian ID is single sign-on across all our OnDemand services such as Bitbucket, JIRA, HipChat and Confluence, one of the most popular feature requests on Bitbucket!

What does this mean to you

Other housekeeping

As part of this change, any team that has no groups or individual members has been converted to an individual account. This is a very small subset of users who will notice absolutely no change in their daily work.

Help I’ve lost my way

Don’t worry! We’ve put together a complete guide in the Bitbucket Knowledge Base to help you out. If you’re still lost, the Bitbucket’s support team is here to help you troubleshoot any problems or questions you may have with this migration. Simply file a support ticket and you’ll be good to go.

  • Michael Lenaghan

    There’s an email address associated with the team. I’d like to associate it with a new user account, and make that new user account the administrator. Possible?

    • Anonymous

      Of course!
      Delete your email from the team account.
      Invite that email to join as an admin.
      Log out.
      Follow the invite link and create a new account using the newly freed email.

      • Michael Lenaghan

        I did that, but when I try to create the new account it tells me that the email address is in use. I’ll wait a bit (maybe it takes a while for the system to forget the old email?) and then I’ll try again.

        • Anonymous

          If you keep getting the email message, please come over to support.atlassian.com and raise an issue. We may have to help you fix it.

          • pdoyle99

            Exact same thing happened to me. Delete email and then invited that email. Now I can netiher create an account with that email or login to the team account with it.

          • pdoyle99

            And I just logged in with my username instead of my email and things seem fine. An obvious solution but not one that registered until now.

          • Anonymous

            To get around that:
            Log out.
            Click the link in the invite.
            Follow the link for “Need an account? Sign up to accept this invitation.”
            Create a new account to become the admin.

  • Rui Fernando Hayashi

    Is it going to be possible to create a user that has access to all repositories of a team regardless of their individual access management? I use the team credentials to access the bitbucket api, and that makes me sure that I can get data from all repositories of that team.

  • Ministryotech

    Will this prevent you logging on using a team name to just the BitBucket site or to the repositories themselves? This is going to be an immense headache for me if you can no longer use the team login for repos as I run multiple teams and the team logins are used server side as part of the deployment process.

  • Anonymous

    Please, please, please add SAML based authentication. I don’t think you realize how far behind you are in not offering this. Companies like OneLogin, Okta, and Ping Identity are moving fast in getting companies setup for SSO in the enterprise, and SAML auth is clearly the leader here. Without supporting SAML as an auth solution you will not be keeping up with enterprise security and identity management solutions.

  • aaronmfraser

    I dont see anything about mutli-factor auth. Is this in the roadmap?