JSM Licenses pooled between sites in multi site org

[Mags K]

Hi, does anyone know if the billing structure described in the answer to this question still stand?

Solved: Multiple Jira sites and licences under one Atlassi...

This post is 5 years old. I am trying to understand if we have multiple sites in 1 organization, each site having its own JSM instance, is there a way to pool licenses at the org level instead of at the site level. 

For example, if site1.atlassian.net has 100 JSM licenses but only uses 70 and site2.atlassian.net has 200 licenses but only uses 110 could we move to a 200 licenses plan for the whole org and share the JSM licenses between sites? This is assuming there are no addins to this subscription.

[Philipp Sendek]

Hi @Mags K

so there are two parts to this question

1) A centrallized Org Administration that includes various sites. This is indeed reality today and whenever you create a new site in an organization, this is managed through the centralized org administration. 

2) Pooling licenses in your organization that are shared across different sites. This is one of the key features of Atlassian's Enterprise plan. So, for example:

You have an enterprise plan for 300 Jira Service Management users. You can now built as many sites for JSM as you like, determine the user tier (up to 300) for each of those and are only billed for the 300 licenses once. Same goes for Confluence or any other product. In addition to that, the Enterprise plan offers many more benefits that might make it attractive for you.
Other than that, a pooling of licenses and sharing the "seats" across sites isn't possible.

I hope that answered your questions.

Greetings
Philipp

[Mags K]

Really appreciate you taking the time to answer this @Philipp Sendek !

We have indeed decided to move to Enterprise for this and the analytics features. Just getting the project started now.

Thanks again