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?
Hello everyone,
It has been a while since this question was posted and we receive many requests for help with Organization administration here, so for new people that may use this post as a reference to find a solution or ask for help, I will add here what you need to do in different situations when it comes Org admin.
1 - I’m an Org admin and I want to add a new teammate as Org admin as well.
As an Org Admin, you can add a new Org admin by going to:
a) admin.atlassian.com where you can see the list of all organizations that you are an admin.
Click on the desired organization > Settings > Administrators.
On this page, you can add and remove the admins.
b) From Jira or Confluence, click on the Cog icon > User management. You will land on the User’s page, then on the top, you will see the same menu “Settings” as mentioned on the steps above.
2 - The Org admin left the company and no one else has permission to remove and add a new admin.
a) The first thing you can do is to talk to your IT team to see if they can activate the email account again and reset the Atlassian account password, so you can log in as the previous admin and follow the steps mentioned on number 1.
b) If the account can’t be recovered:
3 - If I access admin.atlassian.com I don’t see any organization / I don’t see the Settings when I access the User management.
If you don’t see any option to access the settings, but you can access the User management, it means that you are a site administrator only, so you either need to request access to the Org admin or if they left your company, just follow the steps I mentioned.
Hope this answer helps you to find the solution you need.
Stay safe!
Kind regards,
Angélica
Hi Bhanu,
If you don't need SSO or two-step verification enforcement for the 800 users on the old Cloud site, you can place them in a non-billable authentication policy.
You can also refer to this documentation on configuring a non-billable default policy so that self-sign up users are not considered billable for Atlassian Access.
Hi Bhanu,
Atlassian Access only applies to users inside your domain(s) and have active accounts to access Atlassian products. But it applies to ALL Atlassian products - it can't be separated out to just handle Confluence or just Jira, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.