Shared Jira Environment

Question

How can we identify if we are "sharing" or part of a corporate Jira environment or are we standalone instance ?

Our URL is cruisepal.atlassian.net and we are part of the MariApps company.

Are our billing, metered counts, rovo credits, security, data protection, defined by us (cruisePAL) or do we inherit some or all of our companies settings ?

Matthew Sinclair · Accepted Answer

Your Instance is broken down like this

Org → Site (cruisepal.atlassina.net) → App (Jira/Jira Service Management/Confluence/etc)

So your site may be cruisepal.atlassina.net - but your org may contain more than one site.

Sites share user accounts via directory - and those user accounts are granted seats by the Site-Admin/Org-Admin's discretion.

The sites however are isolated (per app) - they don't share anything unless

A: They are linked via connector

B: The user has "Browse permission" of said resources on both sides of the "connector"

That connector provides a way to "Reference" / link content with a pretty embed - limited in function.

Rovo also always defaults/presumes to not cross the Site wall in terms of it's context - every time I've had to explicitly give it permission/directive to go look at the sandbox or something. It tends to be reluctant to leave the site.

Bottom line - you can only see what your allowed to see.

Also in terms of billing - that depends on entirely which billing system your under (legacy vs new) and how your org is laid out - only your Org Administrator/Billing Administrator will have that knowledge - or will get access to what/where/who.

Subject gets very - complicated very quickly so sorry if its limited.

The rabbit hole starts here - and coincidentally is a part of the ACP-520 Exam materials:

https://support.atlassian.com/organization-administration/resources/

Best case - you are your own org with your own resource pool - Org Administrator will know for sure.

Worst case (but not the worst) - you share your site with other sites in the org.

My org has 15-20 sites - each with its own "subdomain".atlassian.net

We have a shared pool of Credits/Steps/Meters outside specific sites with premium apps like Jira Product Discovery that isn't apart of the Teamwork/Service collections.

But some of our sites are - not entirely unified - so it gets a little messy.

Arkadiusz Wroblewski · Accepted Answer

Hi @David Lehman

Ask your organization admin to check Atlassian Administration → Apps → Sites to see which organization owns your site.

Rovo credits are pooled at the organization level, while billing arrangements and security policies depend on your configuration.

Cheers,

Arek🤠🧙‍♂️

Ciro · Accepted Answer

Hello,

The answers above cover the structure, so here's your second question point by point. It comes down to which organization owns your site.

If the site sits in the MariApps organization:

* Rovo credits: shared. All of an organization's allowances go into a single pool, so your usage and theirs draw from the same total.
* Security: if the company has verified its domain and claimed your accounts, its admins can enforce things like password policy, idle session length and two-step verification on them.
* Billing: admins of the organization see billing details for the apps created in it.

If cruisePAL has its own organization, those are yours to set.

Metered usage and data protection are the two I couldn't confirm from the docs, so I'd ask that same admin. They can also tell you whether your accounts are managed.