Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Adding a Workspace in a Premium account - still adds a Free Workspace & asks if I want to upgrade ?

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

2 answers

1 vote
Caroline R
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 08, 2021

Hi, @Vivek Kaul!

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 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:

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

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,

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.

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

Like Cenna Skulsky likes this

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. 

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 06, 2022

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:

Kind regards,

0 votes
Caroline R
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 15, 2021

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,

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. 

Caroline R
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 23, 2021

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: 

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. 

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,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events