I want to be removed from netgo-dys.atlassian.net but I don’t have permission

[Cafer Aydin]

Hello Atlassian Support,

I am a user listed under the group `jira-users-netgo-dys` on the site `netgo-dys.atlassian.net`.

My account (zng.caferaydin@gmail.com) is shown under the group, but I do not have the necessary permissions to remove myself or manage my own access.

I am no longer involved in this Jira instance and would like to be fully removed from:
- the group `jira-users-netgo-dys`
- the Jira site `netgo-dys.atlassian.net`

Please disconnect my Atlassian account from this site. I do not want to have any further association with it.

Thank you for your support.

Cafer Aydın

[Walter Buggenhout]

Hi @Cafer Aydin and welcome to the Community!

It is correct that you cannot remove yourself from a site. Nor can we, since we do not have access to the site. You would need to reach out to the administrators / owners of that site to remove you from those groups and shut down your product access as well. They should be at the team / organisation the site is associated with.

Hope this helps.

[Cafer Aydin]

Hi,

Thank you for your response.

Unfortunately, no one on our team currently has admin access to the Jira site `netgo-dys.atlassian.net`. The person who initially had admin access can no longer log in, and all current users — including myself — lack permissions to manage group access or shut down product access.

This site is now orphaned, with no available administrator. Can you escalate this to the Atlassian support team responsible for handling abandoned or orphaned Jira Cloud instances?

Please assist in removing my account (zng.caferaydin@gmail.com) from this site or deactivating the Jira product associated with it.

[Walter Buggenhout]

I already did reach out, @Cafer Aydin - normal response times here on Community can be up to 2 business days. Usually faster, telling from experience, but it's Saturday right now.

With the additional information, however, it almost seems as if your site is no longer being used or has fallen without an admin. Those are quite different scenarios. If the site is still being used, the site owners / users should really work with Atlassian support to reinstate an admin there somehow (and make sure it is no longer depending on a single person going forward). If the site is no longer being used, it seems like a better plan to get it cancelled. Doing so will automatically remove your association with it as well. Again, in the scenario you describe this will require working with Atlassian by people who are clearly associated with the site domain.