How do I remove an organization admin?

[Kristian Kauper]

The user who created our organization originally, who has now left the company, is an organization and site admin. When I try to "Revoke site accesss", I get the error "Unable to revoke site access". If I go into the details of the user and try to remove the "Site administrator role", I get the error "Error changing role".

How can I revoke all access for this user?

[Angélica Luz · Accepted solution]

Hello @tyrone kimble,

Thank you for reaching out to Atlassian Community!

Removing a domain from an organization won't remove the users from the site, they will still have access to everything, the only difference is that, while you don't verify the email again, they will have the ability to change their full name, email address, for example. 

I can see that one domain ends with .com and another one with .net, so since they are different, if you remove the domain .net for example, it won't affect the people from the domain that ends with .com and vice versa. 

Also, as I mentioned, the accounts won't be deleted from the site, they will still appear as duplicated, so a site administrator will have to delete the accounts or set as inactive.

Users will receive a notification informing that their account is not managed anymore and then when verifying it again on another organization, they will know that the account is managed again. 

• Verify a domain for your organization

Remove a verified domain

When you remove a domain from your list of verified domains, the users with that domain are no longer managed and won't appear on your Managed account page.

To remove a verified domain, click Remove next to the domain and verify that you want to remove it. We'll email users with that domain to let them know that their account is no longer managed.

If you have any other questions regarding this matter, please let us know.

Regards,
Angélica

[tyrone kimble]

Thank you...

[Charles Gage]

Hello - We are considering moving over to "Atlassian Access."  Currently, we have two verified domains that oversee two organizations.

We realize the best approach is to sweep everything under one Organization and that's what we eventually intend to do.  However, for our testing/setup procedures, we are concerned that the moment we turn on Atlassian Access over one new Organization, that will immediately incur the $4.00/pp/pm charge for Atlassian Access for all our users in all our instances (primarily two instances).

We would rather take our one instance that we are setting up and have it under Atlassian Access for setup/testing reasons.  BUT, we need to (I guess) remove the "verified domain" from our Managed Accounts and allow it to be used by Atlassian Access.  This is to help us setup SSO and get that resolved.

Then, we would include our original organization under the NEW Organization, thus triggering Atlassian Access and the costs associated with the rest of the staff.

So, I guess my questions are:

1.  Am I making this too difficult?
2.  What is the impact to the existing Organization of removing a verified domain from that organization and then allowing Atlassian Access to grab it for another Organization?

I appreciate your help!

Chuck Gage