Reassigning Global Admin rights and removing access to a specific user for FREE
Asked by JohnSmizz:

Hi!

TL;DR: I'm looking to elevate myself to Global Admin and remove a specific colleague, and ensure that I there is only one copy of this Space.

By way of background, this confluence is being used by an assistant and myself, but it looks like I may need to downsize to no assistant / I want to make sure I am the sole owner of the only repo - ie it's not copied or cloned.

When we started off, this colleague created a Confluence space, which we moved into my space, and we are now updating/maintaining. I believe it's my Space because it references me as a Creator under Settings, and if I navigate to the top right button and click "My Space" it links me to the Space we use. Having said that, the URL continues to refer to the "old space" that was in fact created by my colleague! This explains my goal above, where i want to "ensure" that there is no second "clone" of this Space if/when we remove the other contributor.

The second question is related to \*How to remove a contributor\* in your Space? If I say "upgrade" it suggests I speak to my space Admin (which I believe I am).

I \*worry\* I may have misunderstood the difference between Spaces and Sites, and that I actually am operating on a Space within my colleague's SITE that I think is "mine" but in reality this is all still part of the original/old/wrong SITE.  

How do I reassign SITE ownership to myself, if that's possible at all? My colleague will agree, as she wants the ultimate owner, ie me, to have access/ownership.


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Yes, you might be getting confused by site and space (but it's not a surprise, these are not simple or particularly intuitive systems!).

* At the very top level, there's your organisation or company (although "organisation" has another meaning within Jira service management, so I'll just use company from now on). Atlassian sees companies them as their customers, because they're buying Cloud services from them.
* A company can have many sites. My lot have hundreds now, if you ever get referred to a URL that is <https://avst->\<something\>.atlassian.net, then it's almost certainly one of ours.
* A site can contain several Atlassian systems, but only one of each. Avst-42 has a Jira, Confluence and a Bitbucket, AVST-24 contains just a Jira, and so on.
* Next layer down - Jira and Bitbucket are sub-divided into projects, Confluence into spaces.

The best thing to do is work out what you do and don't have access to. First, look at the URLs everyone are using. Do they all start with the same words? e.g. https://**yourplace** .atlassian.net - if **yourplace** is the only one in use, then you have a single site.

Then pop over to my.atlassian.com - this will tell you what sites you are listed as the billing or technical contact on. You'll need to make sure you are one (or both) on all the sites you want to be running in the future.

On the second question, a contributor is someone who has authored a page or commented, but I suspect you're talking about users in general. You can check the "space permissions" to see who can do what in your space. But you will need to be a space admin to get there (and edit it)


author: Trudy Claspill
body: Hello [@JohnSmizz](/t5/user/viewprofilepage/user-id/1161268)

The Site is specified by the URL you are accessing and is something like:

```
https://<something>.atlassian.net
```

A Site can include multiple Atlassian projects. The Confluence product within that site is accessed by the URL:

```
https://<something>.atlassian.net/wiki
```

A Space exists within a Confluence product instance. You typically see the space key in the URL, like this:

```
https://<something>.atlassian.net/wiki/spaces/FIRSTSPACE/overview
```

"FIRSTSPACE" is the space key for a space in the Confluence product in the site \<something\>.atlassian.net

Lastly, Sites are grouped into Organizations. If you are an admin for the Site or the Organization you will have access to the URL

```
https://admin.atlassian.com
```

There are different levels of access to be addressed. There is

* Organization Admin
* Site Admin
* Confluence Admin
* Space Admin

Another element that comes into play with levels of access and permissions is whether or not you are using Confluence product for free or are paying for a subscription. Do you know which is the case for you?

comments: author: JohnSmizz
body: A) firstly thanks very much for the hierarchical explanation. Everything is starting to make A LOT more sense now

B) were only 3 people so weve been operating in the / under the free product.


author: Trudy Claspill
body: This page talks about the levels of permissions specific to the Confluence product:

<https://support.atlassian.com/confluence-cloud/docs/what-are-confluence-cloud-permissions-and-restrictions/>

This page provides information about managing permissions in Confluence, calling out the differences in the free plan.

<https://support.atlassian.com/confluence-cloud/docs/manage-permissions-in-the-free-edition-of-confluence-cloud/>

This post talks about the differences between Organization Admins, Site Admins, and Product Admins:

<https://community.atlassian.com/t5/Jira-questions/What-is-different-between-org-admin-site-admin-and-product-admin/qaq-p/1707926>

Now that you have a better understanding of the hierarchy, can you re-ask your question so that we better understand what you are trying to do?


author: JohnSmizz
body: Hi!

So thanks to the context provided by you, I think I can communicate a bit more effectively about my situation and my goals.

I want to make sure that the organization admin rights remain with me for the space that we are all currently using. A few confusions arise: Firstly, my current understanding is that if I am using the "Free" plan, each user registration and creation of a space, will implicitly also create a Site and and Organization that sit above the created space.

For my objective of making sure I remain the sole owner of the organization under which the Confluence space operates that we use daily, my assistant set me up as a org admin via admin.atlassian.net, and removed themself. This means that I think I've achieved what I initially set out to do, but understanding the concepts and differences between organizations, sites, products, spaces was key to this, so thank you!


author: Trudy Claspill
body: > each user registration and creation of a space, will implicitly also create a Site and and Organization that sit above the created space.

Incorrect.

A user can be invited to your Site or can request access to and be granted access to your Site.

```
https://<something>.atlassian.net
```

Once that user has access to your Site, the user can be granted Product Access to the Confluence product in your Site.

Any number of Spaces can be created within the one Confluence product under your Site, under your Organization.

A Space can be created **only** within an existing Confluence product, which must already exist under a Site and Organization. Therefore creating a Space does not "also" create a Site and Organization.

Any person can initiate their own Free Confluence instance. If they do that then that would create a new Organization and a new Site which would be entirely separate from your Organization and Site.


Tags: cloud

confluence-cloud