Adding Regions for Cross-Region Accounts

    When a new user signs up for a region, a new Own account is created with an instance of the region they signed up for. The user who created the account becomes the Master Admin. With only one region in the Own account, it is currently a single-region Own account.

    In the diagram below, Alice has created an instance in the region useast2. She now has a single-region Own account. Alice is the Master Admin, and she has added users Bob, Charlie, and David.

    When another instance in another region is created by the Master Admin, the Own account becomes cross-region. A cross-region Own account has multiple regions that share at least one user.

    NOTE: Only Master Admins can create new regions in the same Own account. If another user in the Own account tries to create an instance in a new region, they will receive an email asking them to contact their Master Admin.

    Users can be added to a single region within a cross-region Own account (single-region users), or they can be added to multiple, or even all, regions within a cross-region Own account (cross-region users). Users are only able to see and access the regions they were added to.

    All the regions within a single Own account share the same security settings. Only the Master Admin users of the regions can change these settings. Changing these settings within one region changes them across all the regions in the same Own account. Therefore, Own recommends having the same user act as Master Admin in all regions in the same Own account.

    NOTE: Users cannot exist across different Own accounts. For the same user to exist in different regions, the regions must be under the same Own account.

    When an Own account becomes cross-region, users from the initial region can be invited to the new region without issue.

    In the diagram below, Alice has two regions in her Own account, one in the region useast2, and one in the region emea1. Since Alice is the Master Admin of both regions, they both exist in the same Own account, and it is cross-region. In useast2, she has added Bob and David, in emea1, she has added Charlie and David. Because David and Alice are in both regions, they are cross-region users within their Own account. 

    NOTE: Bob and Charlie are single-region users, therefore they can only access and see the regions they were added to.

    If a user who already exists in the first region and is not the Master Admin, attempts to create a new instance in a different region, they will receive a message telling them to contact their Master Admin. If the Master Admin role in the new region, in the same Own account must be given to a different user, then the Master Admin of the initial region must create the new instance in the new region. After they have created the new region, they can reassign the Master Admin role to another user. In this case, the regions will still exist in the same Own account, despite having different Master Admins in each region. Users from the initial region can still be invited to the new region without issue. The Master Admin of either region is able to make changes to the security settings that affect all the regions in the entire Own account.

    In the diagram below, Alice created the first instance in region useast2. She invited Bob and David as users. Alice then created another instance in region emea1, invited David to the instance in emea1, and then assigned him the Master Admin role in that region. The new instance in emea1 is also part of Alice’s Own account, which is now cross-region. However, David is the Master Admin of the instance in emea1 and only he (and Admin users in emea1) can invite users to that region, while Alice is still the Master Admin of the instance in useast2 and only she (and Admin users in useast2) can invite users to that region. David invited Bob and Charlie to emea1. Alice, David, and Bob are all cross-region users within their Own account.

    However, if a user who does not exist in the initial region creates another instance in a different region, there are no mutual users in between the initial region and the new one. This will result in a new Own account being created for the new region, and the Master Admin in the new region will not be able to invite users from the initial region to the new region.  

    NOTE: This situation should be avoided. If this was done in error, Own support must be contacted to merge the regions under the same Own account.

    In the diagram below, Alice created the instance in region useast2. She invited Bob as a user. Then David created another instance in region emea1 and invited Charlie as a user. Since David was not a user in Alice’s initial Own account, he has created a new Own account that is single-region. These two regions are not in the same Own account, so users from one region cannot be invited to the other. Alice will not be able to invite David or Charlie to her region, and David will not be able to invite Alice or Bob to his region.

     

    « Previous ArticleNext Article »