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.