I created a statuspage and it seems to have created a new organization. Is that expected?
Asked by Monte Kalisch:

I am trying to set up a statuspage for one of our apps. When I went to create it, either I did something wrong or the default behavior is to create it in an entirely new organization. Is .. that expected? I didn't really want to have to manage multiple organizations just for the statuspage and can't find any way to move it to a different organization. I created a support ticket but they haven't responded.

I want to activate the statuspage but don't want to do that if it's set up incorrect (in the wrong org).


Answers:
author: Talar Pavlovic
body: Hi there Monte,

Thanks for writing into Community, I'm Talar from the Atlassian Statuspage support team, happy to help!

There are two main options to move the Statuspage into the same Atlassian Organisation as your other Atlassian Apps. Before I detail them, some background info that will be helpful:

* All Atlassian Products live within an Atlassian Site
  * Each Atlassian Site can have 1 of each product. Ie it can have
    * 1 x Jira Software
    * 1 x Statuspage Organisation
    * 1 x Opsgenie
    * 1 x Confluence etc etc
* All Atlassian Sites live with an Atlassian Organisation
  * Each Atlassian Organisation can have multiple Atlassian Sites within it
  * Each of these sites can have different Administrators and Users
* Each Site should have 1 or more Site Admins
* Each Org should have 1 or more Org Admins

We generally advise customers to run 2 sites in their Atlassian org, one for their main, and one for their Statuspage product unless they are on the new "centralised user management" structure.

* The reasoning behind this is "Trusted Users". This is a user role that has access to ALL products in a site (intentional by design). Customers have often used this for people meant to be accessing both Jira \& Confluence products.
* However - Statuspage is very vigilant in license enforcement - if you have 10 licenses and 10 people assigned to Statuspage, then we won't let you add people to groups if that group has access to Statuspage.  
  Trusted Users have access to ALL products and therefore count as using a Statuspage license even though they're not intended to be using the product and this cannot be avoided.
* Additionally - we often see that the users for a Statuspage Product (Comms Managers) are very different from the administrators of Jira / Confluence and it's easier to logically separate them into different sites.
* For fluid user experience - we recommend users focus on using <https://start.atlassian.com> as their starting point - this will allow them to access their products regardless of what atlassian.net site their products are in.

#### **Having said all of the above - What are the move options I hear you ask?** {#toc-hId-289422002}

**Option 1 - Different Sites, One Organisation (available for all customers):**

If you'd like to have the Atlassian Site that holds your Statuspage under the same Atlassian Organisation as your other apps, this can be done as a self-serve exercise. Please follow the steps detailed: <https://support.atlassian.com/organization-administration/docs/transfer-products-to-another-organization/>

**Option 2 - Same Site for all (requires additional checks to confirm if this can be achieved)**

If you'd like to have Statuspage under the same Atlassian Site as the rest of your Atlassian Apps, you will need support to confirm this is possible for your site, and also to make the moves for you.

Monte, I've replied to your support ticket so we can work through your options there.

Kind regards,  
Talar


Tags: cloud