Request to Add Additional Seats with Separate Billing and Independent Setup

[wedness]

Currently, we are on the Standard Plan with 100 seats allocated, of which only 85 are in use. Our existing billing is set up to charge directly to our Japan entity (JP) in Japanese Yen (JPY).

We would like to add 9 more seats without impacting the current JP usage, billing, or setup in any way. Specifically, we have the following requirements:

• The additional 9 seats should be completely independent and not connected to the existing project/space/workspace in any way (i.e., fully separate projects/spaces).
• Billing for these new seats should be handled separately: using a different billing address and a different currency (not JPY).

This way, the original JP billing and usage remain unchanged and unaffected.

Additionally, as an optional question: If it is possible to achieve the above within the same account (rather than creating an entirely new account), could you please confirm the following?

• Would users be able to freely switch between the two spaces/workspaces?
• Would the features and functionality in the new space be exactly the same as in the existing one?

Please let me know if this setup is feasible under our current plan, what the next steps would be, any associated costs, and whether it requires creating a separate account or can be managed within the existing one.

[John Funk]

Hi Wedness,

It is possible to create a new Jira Cloud site and then clone the configurations from one site to the other one using a tool like Revyz Configuration Manager for Jira. And since it is a new and different site, it would be billed completely separate.

[Trudy Claspill]

Hello @wedness 

Welcome to the Atlassian community.

You said you have allocated 100 seats to your Jira subscription. Are you paying annually for 100 seats rather than paying monthly for the number of seats actually used?

If you are paying annually for 100 seats, then adding 9 more users (when only 85 are currently granted access) would not affect your billing as you would still be under 100 total seats used.

If you want to pay for those 9 users separately and don't want them to have access to the existing Jira projects/spaces then you would have to set up a separate Jira subscription for those 9 users to access. That is the only way to pay for them in a different manner.

If you set up a separate Jira subscription for those 9 users and did not give them access to the original Jira site (used by the 85 users) then those 9 users would not be able to access the original site. If you want them to be able to access that original site you would have to grant them access to the original site, and then they would consume 9 of your 100 licenses for that site. If you have third party apps on the existing site and you want the 9 users to have the same apps you would have to install those apps on the second site and pay for those apps a second time. None of the configurations or functionality from the first site would be available to the 9 users on the second site unless you took additional steps to manually recreate the functionality/configurations or used a tool such as was suggested by @John Funk