Would our organization be billed per user per workspace, or per user?

[Ryan Taylor]

We are a large organization and the workspace > project > repo organizational structure doesn't align well with our organization.

For example, we have multiple projects each with multiple repos within one of our business units. We would like to utilize Bitbucket Pipelines to share tokens and code across these projects, but not outside the business unit. If we maintain just one workspace for the org we're then forced to duplicate tokens / shared code across multiple projects.

Given that limitation, I think our only option would be to create multiple workspaces within our organization. However, some user's will be working in multiple workspaces.

Would our organization be billed per user per workspace, or per user?

----

What I would **really** like to see is more flexible grouping akin to GitLab's Groups so we could build a hierarchy that reflects our organizational structure better. I.e., 

• workspace > group > project1 > repo1, 
• workspace > group > project2 > repo
• workspace > group > project3 > repo

Group should have all the permissions and capabilities that today's workspaces and repos have (e.g. access tokens, create permissions, shared code, etc). Additionally, the repo slug must contain the workspace, group, and project to allow repos with the same name to exist across workspaces and groups.

If something like this is in the works, please let me know.

[Shwetha Suvarna]

Hey @Ryan Taylor ,

Welcome to Community…

In the instance of users working in multiple workspaces, the organization will be billed per user per workspace. A billable user is anyone who is a member of your Bitbucket workspace.

At the Moment, in Bitbucket, the users can use below features :

• Project permissions allow admins to grant access to all repositories, old and new, within a project without having to manage each repository individually, meaning any permissions set within a project will apply to all the repositories in that project.

• We can provide the relevant Groups with the required project permissions like Read, Write, Admin, etc.

• However, the access tokens are project-specific and not group-specific. We do not have a method for providing access tokens on a per-group basis.

• Also, Bitbucket repositories don't have a unique ID, hence the user is unable to create repositories with the same name even if they’re on different projects, because all repositories are accessed within the level of workspace. More details on feature request: BCLOUD-19706

I hope this helps.

Best Regards
Shwetha Suvarna

[Ryan Taylor]

It's good to have an answer as the official docs were not clear, however, this is not the answer I was hoping for. It limits our ability to work within the constraints of Bitbucket.

As another example, we have numerous projects in our workspace, projects A thru Z. Each project has multiple repositories. Projects A thru D need to share pipeline configuration and variables (secrets). However, we really don't want to share the pipeline and especially the secrets with projects E-Z. These belong to other business units in our organization.

Further our developers work across business units and many would need access to both workspaces, even though they belong to one organization.

I'm already following BCLOUD-19706. That's really different from this ask.

We need more options for organization our projects and shared configuration without charging extra for the same user within our Atlassian Organization. Either something between workspace and project or an "organization" type above workspace so workspaces can be used for organization.

[Shwetha Suvarna]

Hey  @Ryan Taylor 

Thank you for sharing the feedback. I understand that this is not the expected solution for the query.

As discussed on the page https://www.atlassian.com/blog/announcements/maximum-quantity-billing

• Atlassian Bills per user per site. 
• Atlassian organizations merely bring together the company’s users and apps under one umbrella.
• Thus, for now, we do not have a method to share billing data across two sites OR to share combined billing for users across different sites.

The best option at the moment is to provide Groups with all of Repos's capabilities, such as access tokens and shared codes.

We have raised a feature request, BCLOUD-23903, for this query. Please add your comments to the Feature request, providing direct feedback to the Atlassian team.

Best Regards
Shwetha Suvarna