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
@sam saas Admin API keys are scoped to a single organization (they can be used by multiple users since they are owned by the organization, not any individual user).
That said, most administrators only administer a single organization, since an organization is typically mapped to a company, and most people only work for a single company 🙂
What's driving your requirement to use a single API key for multiple organizations?
Hi @Dave Meyer
Thanks for clarifying the scope of the Admin Key !
I was checking the APIs available for orgs when I came across this: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-orgs/#api-orgs-get
And I also get the same response as @Prince Nyeche has mentioned in the reply above for the get orgs endpoint. That was the reason why I wanted to check if there is a possibility of having multiple organisations mapped to single Admin API key and the get orgs endpoint would be used to get all orgs (based on the API token) as it mentions.
Can you please help me understand what response should we be expecting from this API, as currently it returns an empty response with 200 status code?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Prince Nyeche @sam saas Thanks both for your clarifications, I understand the confusion now. I think the error is that this shouldn't be listed as a public API in our documentation – the only place I'm aware of where we present the data that this API endpoint returns is when you land directly on admin.atlassian.com and are presenting with the list of orgs you administer.
When you create the org API token, we also provide your orgId value. You can see that every other API in the group except for that one takes an orgId in the path.
I created a bug report here: https://jira.atlassian.com/browse/ACCESS-966
Also just a quick note: usage of this API doesn't strictly require an Atlassian Access subscription, only some of the endpoints that return data from Access features (like the audit log endpoint).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Dave Meyer for the clarification and the open bug ticket, that's very helpful.
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.
Hi @sam saas
The Docs mentioned "0 or more values of Org are returned" with that API. I don't particularly think the Org Id matters when creating the API. It just denotes where the API was generated. However I noticed that it returns an empty list instead with a 200 Status code. Which to me means that the API may not be working properly as I have Atlassian Access in only 1 of my Org.
So to answer your question, the API once generated should work across all Org that you are on as an Org Admin. I don't think that it matters on what Org the API is generated on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Prince Nyeche can you double-check whether you're using a personal API token (tied to your Atlassian account) or an Admin API key (which is associated to an organization and must be created by an organization admin).
You're correct that a personal API token should work across all products you have access to, but an Admin API key is scoped to a single organization.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dave Meyer
Yes, I'm using the Org Admin API generated from here, and not the Personal API token from id.atlassian.com. Likewise API works if I'm using other endpoints, however this is the result I get when I use this endpoint to get Orgs
{"data":[],"links":{"self":"https://api.atlassian.com/admin/v1/orgs"},"meta":null}So i'm not certain why it will show an empty list or maybe something else is wrong somewhere.
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.