Remove user from an organization as a non-Jira Admin?

[Jared Grywacheski]

Few bits of information needed for this issue:

One of our users at our University created their own JSM org (We'll call this university-team.atlassian.net) this org is not related to our license whatsoever but happens to have our University name in the URL

Another one of our users, when trying to set up the mobile app, accidentally joined university-team.atlassian.net thinking it was our University's license of Jira. 

Now the user would like to be removed from university-team.atlassian.net but the user that created it, the Admin, is not responding. It's quite possible they abandoned it. 

The user has no way of removing themselves and since it's not part of our license our Jira Admins have no way of removing them either. 

I would assume Atlassian support could remove the user but the user or myself, not being Jira Admins, cannot open a support case with Atlassian ourselves. 

What can we do to have him removed? 

[Trudy Claspill]

Hello @Jared Grywacheski 

Jumping in on this thread...

Your post tags indicate you have a Premium subscription. Is that accurate?

If so, I think Valerie's information about Discovered Products does not apply.

With an Enterprise subscription you can have an Atlassian Cloud Organization under which you have multiple Sites. Each site can have its own URL and its own copies of the Atlassian Cloud products.

In the case of an Enterprise subscription when you have also claimed domains, if a person using an email address from your claimed email domain sets up a new subscription to a Jira product and as part of that creates a new Atlassian Cloud Organization, then that product would show up in the Discovered Products section in https://admin.atlassian.com when you are viewing your Atlassian Cloud Organization. 

In that case an Organization Admin from your Organization can grant themselves Organization Admin rights to the site created by that user.

If you have an Enterprise subscription, but the user who created the site did not use an email that is in your claimed domains, then the site will not turn up in your Discovered Products.

If you are, in fact, using a Premium subscription then you will not have the option to have multiple sites under your Atlassian Cloud Organization nor to see Discovered Products and take ownership.

When creating a site the subscriber can choose any name they want that has not been used. Unless you have the name trademarked there is not much you can do to force the name to be changed.

Now, if you are in a situation where you don't have Discovered Products as a feature, or the site does not show up in your Discovered Products, the only option available to the user that accessed the site is to contact the site owner to ask to be removed from it.

1. It is not possible at this time for a user to self-remove from a site. (That would be counter productive to companies that require their employees to use Jira.)
2. Atlassian will not manage the site's users except as part of helping the site owner resolve an issue as, again, that could be counter productive from the perspective of the site owner.

If the site products are under a Free subscription, and the owner has "abandoned" it, and users do not login to it for 120, then the products will be deactivated by Atlassian and start a process of ultimately being deleted. With the deletion of the product, your user would no longer have to worry about trying to get dis-invited to the product.

If the products are under a paid subscription, as long as the payments are made the site and products will remain accessible and Atlassian will not delete it. If there is a lapse in payment for a paid product, then there is a process for Atlassian to suspend the product, then deactivate the product, then eventually delete the product.

[Trudy Claspill]

Hello @Jared Grywacheski 

Did the information provided by us help you resolve your issue? If so, please consider clicking on the Accept Answer button to mark your Question as Solved.

If you have addition questions on this topic, let us know.

[Valerie Knapp]

Hi @Jared Grywacheski , thanks for your post. 

If I've understand correctly, it sounds like what you are describing is a what's referred to as a Discovered Product. 

What can happen in the cloud, which is different to server or data center where you have distinct users, is that, because your user in cloud is your email address, people who create their own instance, using their work email, are creating shadow IT (the ITIL term) or a Discovered Product. 

Someone who is an org admin in your main organisation should have the power to add themselves to the Discovered Product as an admin and request that it be deleted, if it's redundant. 

Please check out the documentation for this here https://support.atlassian.com/organization-administration/docs/review-discovered-products/ .

If you are still stuck or have other questions, please let us know. 

Best wishes

[Jared Grywacheski]

This does look like it may be what happened. 

Is it possible that the URL for the "discovered product" the user created not be related to the URL of our main org at all? 

ie. 
Their URL is uoa-team.atlassian.net

and ours is atlassianu.atlassian.net