Adding a Workspace in a Premium account - still adds a Free Workspace & asks if I want to upgrade ?
Asked by Vivek Kaul:

When i add a new Workspace in my Premium account it creates the Workspace as a Free \& asks for upgrade. If i upgrade - will it add the Workspace in the same Premium Account? I need multiple Workspaces in the same account to separate various Teams/Groups from having access to all projects yet have Admin permissions to their own Workspace to create Projects \& Repos


Answers:
author: Caroline R
body: Hi, [@Vivek Kaul](/t5/user/viewprofilepage/user-id/1130288)!

When you upgrade the plan on a Bitbucket account, you do it to a specific workspace. So, if you create a new workspace, it will be under a free plan, this is the expected behavior.

However, you can [create different groups](https://support.atlassian.com/bitbucket-cloud/docs/organize-groups-for-your-repositories/) with specific access to the repositories and to manage the workspace. This way, the users under these groups will only be able to access the repositories that the group has access to and manage the workspace if the group has this type of access.

In summary, this is how the license works:

* The license is set on the workspace you upgraded.

* All the repositories inside this workspace will be under this plan.

* Once you give a user access to a private repository, they count as a user on your billing plan.

* You can create groups to manage the access that the users will have in this workspace.

We do have a feature request to add the possibility to have per person billing instead of per workspace billing, as you can check here:

* [Add the possibility to have per person billing instead of per workspace billing](https://jira.atlassian.com/browse/BCLOUD-20385)

If you are not familiar with our Feature Request Policy, you can read more about it here:

* [Implementation of New Features Policy](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html)

You can add yourself as a watcher (by selecting the **Start watching this issue** link in the feature request) if you'd like to get notified via email on any updates. You can also select the **Vote for this issue** link to indicate that you would like to have this feature available.

I hope this helps, but do let me know if you have any questions.

Kind regards,  
Caroline

comments: author: Vivek Kaul
body: Thanks Caroline - my feeling is perhaps we need an "Account" entity which allows multiple Workspaces with separate sets of Users/Groups \& Projects to be added within - for the bigger enterprise accounts.


author: Shaik Idris
body: +1


author: Cultured Kids
body: Yes, I am a bit distraught here. I just upgraded my account and assumed it would cover all workspaces. So, it will not?


author: Cenna Skulsky
body: Here as well. I thought upgrading to premium would include all Workspaces. Also, I am a bit confused about how guest billing is calculated - seems super complicated.


author: Theodora Boudale
body: Hi everyone,

In Bitbucket Cloud, each workspace has its own billing plan. Upgrading the billing plan of a certain workspace will not affect the billing plan of any other workspace.

If you have multiple workspaces and the same users have access to these workspaces, you can look into:

* [transferring the repositories to one workspace](https://support.atlassian.com/bitbucket-cloud/docs/transfer-repository-ownership/)
* upgrading the billing plan of that workspace
* [manage permissions in the repositories of the workspace with user groups](https://support.atlassian.com/bitbucket-cloud/docs/organize-workspace-members-into-groups/)

Kind regards,  
Theodora


author: Caroline R
body: Hi, Vivek!

Currently, having a Bitbucket account will allow you to create an unlimited number of workspaces. However, each workspace is a separate instance, like a Jira Cloud instance. So each instance is billed separately.

Nevertheless, you can create multiple groups and projects under this workspace to keep things organized. The users won't be able to see private repositories that they don't have access to.

If you need any assistance in managing these accesses, please feel free to contact us.

Kind regards,  
Caroline

comments: author: Vivek Kaul
body: Yes - which is why the "Account" entity is kind of redundant right now - a "Workspace" incorporates an Account - without any differences. The Workspaces created "under an Account" currently may belong to separate Accounts (in fact are generally separate Accounts).

What i am suggesting is that a Workspace created under an Account have the same Billing details by default.


author: Caroline R
body: Dear Vivek,

Thank you for your feedback. I have made some updates to the feature request that I previously shared with you, and I believe that what you are asking is now covered here:

* <https://jira.atlassian.com/browse/BCLOUD-20385>

I spoke with our senior engineers and I'm afraid that this is not likely to be implemented, not in the near future at least. However, if there is more demand in the future, our team may reconsider it.

I would therefore suggest that you add your vote to that feature request, as the number of votes helps our development team better understand the demand for new features.  
I would also like to share with you that currently, what is being worked on by our development team is **Project settings** and **Permissions**, which should facilitate the management of repos and access in a single workspace:

* <https://jira.atlassian.com/browse/BCLOUD-13202>

I believe it would be a good alternative for what you are planning, instead of multiple workspaces (have different projects and configure settings and permissions per project). So, you can keep an eye on this feature request as well.

You are more than welcome to leave any feedback in the feature request, for our product managers to take into account.

If you have any other questions, please feel free to let me know.

Kind regards,  
Caroline


Tags: bitbucket-cloud

cloud