Force managed account personal workspaces to be private?

[Ben L]

We have a BB Cloud with managed users (i.e. managed by the Organisation and Organisation Admin(s)).

We want to require these personal workspaces to be private; is there any way to enforce such a policy? Alternatively, can we disable them?

(our actual problem is that staff have occasionally accidentally created repos in their personal workspace without realising they are public)

[Caroline R · Accepted solution]

Hi, @Ben L, thank you for reaching out to Atlassian Community.

Currently, it’s not possible to enforce this policy. The information available on a personal workspace is specific to the user and hence a second person cannot access it, even the org admin of this account. 

However, we do understand your business case, so we already have 2 feature requests to our dev team to give more control over accounts under a specific domain, as you can see here:

• Corporations need complete control over accounts with their domain

• Provide Organization Admins with granular control over managed Bitbucket accounts

One of the Bitbucket PMs has informed in one of the feature requests above that our engineering team is actively working on improving the project settings and project permissions model with Bitbucket. They expect the improvements to be complete this year and this should address many of the issues related to this subject. 

I would suggest that you add your vote there (by selecting the Vote for this issue link) as the number of votes helps the development team and product managers better understand the demand for new features. 

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy here and any updates will be posted in the feature request. 

Kind regards,
Caroline