Enabling SSO for Bitbucket
Asked by akshay sharma:

Hi,

We have different teams in organization using bitbucket. They all have different Bitbucket licensed accounts and managed separately. Team members are invited/ added to the corresponding repos by sending email invite to their official email addresses.

For example

Bitbucket account 1 : someaccount1@someorg.com

Bitbucket account 2: someaccount1@someorg.com

Bitbucket account 3: someaccount1@someorg.com

Bitbucket account 4: someaccount4@someorg.com

We want to enable SSO for only two of the above accounts, let's say (someaccount1@someorg.com, someaccount2@someorg.com) and keep rest of these account's login mechanism using official email ID and password. We do not wish to club these accounts together and each of them has separate admin.

In Atlassian Access we need to specify and verify the domain (someorg.com). Will enabling the SSO affect all the accounts mentioned above. Or SSO will be enabled to a particular account(s) for which we will change the settings. Also if we want to enable SSO for two of the above accounts, how can we do that as admin of these accounts are different and Atlassian access is added at particular account level.

Please advice.

Thanks


Answers:
author: Caroline R
body: Hi, [@akshay sharma](/t5/user/viewprofilepage/user-id/4206991), thank you for reaching out to Atlassian Community.

If your organization is managed with Atlassian Access, you can set 2 different authentication policies for your organization, one that **enforces SSO** for these 2 users, and another that doesn't enforce the SSO for the other users, like this:

![Screen Shot 2022-09-16 at 12.07.05 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/216415i29EF3EF5D53D9A01/image-size/large?v=v2&px=999 "Screen Shot 2022-09-16 at 12.07.05 PM.png")

An Organization admin can change the [authentication policy](https://support.atlassian.com/security-and-access-policies/docs/understand-authentication-policies/) for these accounts. In order to do that, they can follow the next steps:

1. Go to [admin.atlassian.com](http://admin.atlassian.com/). Select your organization if you have more than one.

2. Select **Security** \> **Authentication policies**.

3. Select **Add policy** to create a new one.

I hope this helps, but please feel free to share any additional questions or concerns regarding this case.

Kind regards,  
Caroline

comments: author: akshay sharma
body: Hi [@Caroline R](/t5/user/viewprofilepage/user-id/3934006),

We do not have Atlassian Access setup as of now, we were trying to set it up. While doing so, we realized that we have a separate "n" number of Bitbucket licensed accounts (different owners/ admins) managed separately.

If I buy an Atlassian access account it will be applicable to the said account and not others, despite the other accounts using corporate email ID as their username.

Please correct me if I am wrong in understanding this.


author: Caroline R
body: Hi [@akshay sharma](/t5/user/viewprofilepage/user-id/4206991),

The Atlassian Access will be applied to the accounts under your verified domain. So if you have users on your Bitbucket workspace that are not under this domain, they won't be affected by Atlassian Access.

You can read more about this subscription here:

* [Understand Atlassian Access](https://support.atlassian.com/security-and-access-policies/docs/understand-atlassian-access/)

Let me know if you have any further questions.

Kind regards,  
Caroline


Tags: bitbucket-cloud

cloud