Can't remove JSM licence from Org Admin
Asked by Richard Blundell:

I incorrectly asked this question in an old thread so am trying again here.

We have two Org Admins, neither of whom are Jira Service Management agents (or, really, Stakeholders or Customers). We're currently paying for a licence for these users and want to remove this licence from each of them. However, the UI won't allow this.

Here's the view for one of the users. Note that they have the JSM "User (agent)" role assigned:

![jsm1.png](https://community.atlassian.com/t5/image/serverpage/image-id/344189i015BC3F2893071FA/image-size/large?v=v2&px=999 "jsm1.png")

If I go to the ellipsis menu to try to change this, there is a padlock next to the "Remove product access" option at the bottom of the menu:

![jsm2.png](https://community.atlassian.com/t5/image/serverpage/image-id/344190i7E40CD6A20563405/image-size/large?v=v2&px=999 "jsm2.png")

If I hover over this menu option there's a tooltip that explicitly says I "Cannot remove product access for an organisation admin":

![jsm3.png](https://community.atlassian.com/t5/image/serverpage/image-id/344191iF16C1F78BB698EFA/image-size/large?v=v2&px=999 "jsm3.png")

If I click the dropdown for the user's roles and try to deselect "User (agent)"...

![jsm4.png](https://community.atlassian.com/t5/image/serverpage/image-id/344192iECAF00D25A81ED53/image-size/large?v=v2&px=999 "jsm4.png")

... it fails with a toast message:

![jsm5.png](https://community.atlassian.com/t5/image/serverpage/image-id/344193i0A78DCA4F18757FF/image-size/large?v=v2&px=999 "jsm5.png")

What am I doing wrong here? The linked thread, below, says we shouldn't have to allocate and pay for licences to these two people who don't use the product, but I can't remove the licence from them. We don't want to have to pay for user licences to a product those users will never use.

*\[My original question was in this thread for the previous question:*

*<https://community.atlassian.com/t5/Jira-Service-Management/Do-Org-Admins-have-to-be-Agents-in-JSM/qaq-p/2632980>\]*


Answers:
author: Kieren _SmolSoftware_
body: Hey [@Richard Blundell](/t5/user/viewprofilepage/user-id/4902569)

There are two roles are play in your question:

1. The JSM Agent role

2. The Org Admin role

Both roles are applied via one or more groups.

The JSM Agent role has a default group, probably called something like *jira-servicemanagement-users-nameofyoursite.*

The Org Admin role will have a default group called *site-admins* or*org-admins.*(I'll assume the group is called org-admins for the rest of this, but just replace the below instructions with whichever group exists in your groups directory...)

Out of the box, the org-admins group will have all the product roles applied to it, as well as all the admin roles. This means when you grant a user the Organization Admin role, that user is put into the org-admins group, they get the org admin role **AND** they get all the product roles.

![Screenshot 2024-08-28 at 6.46.03?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/344196i7FCE5038349128B1/image-size/large?v=v2&px=999 "Screenshot 2024-08-28 at 6.46.03?PM.png")

You can change this, so that when granting an Org Admin role, ONLY the org admin role is granted and no other product roles:

1. Navigate to your group list in admin.atlassian.com

2. Open your site-admins or org-admins group

3. Remove the product roles from the group

4. Remember, by removing product access from this group, ++**all**++ the users in the group will loose product access. So double check if there are any users that do actually need to keep their product access and add them into another group that grants the necessary product access, or manually grant it via the User Detail screen.

Hope that helps!

-Kieren  
Co-Founder @ Smol Software \| Ex-Atlassian

comments: author: Richard Blundell
body: Hi Kieren,

Thank you!

That has done it. We had seventeen groups, and the last-but-one group (named "site-admins", in our case) contained these two users, plus a bunch of suspended users (ex-colleagues), and this group had the "User (agent)" JSM role applied.

I would never have found that without your answer.

It wasn't clear (to me) from the user-centric area of the UI why it wasn't letting me remove those licences. The error showed a GUID instead of a group name, which wasn't helpful.

All fixed, and your helpful answer will hopefully also assist others in future.


author: Ollie Guan
body: Hi [@Richard Blundell](/t5/user/viewprofilepage/user-id/4902569) ,

As a workaround, you might temporarily change the organization admin role to another user, remove the JSM license, and then revert the admin role back.

While this isn't a perfect solution, it's worth a try.

comments: author: Kieren _SmolSoftware_
body: An addendum to my answer above, in relation to [@Ollie Guan](/t5/user/viewprofilepage/user-id/853638)'s answer

If the *org-admins* or *site-admins* group does not have the JSM Agent role on it (as I assumed it did in my answer), then Ollie's answer will work.

If my assumption above is correct however, then the agent role will just be reapplied to the user when you add the Org Admin permission back (since the Agent role is also attached to the same *org-admins* group)


author: Richard Blundell
body: Hi Ollie, a very sneaky workaround that. Crafty thinking, and much appreciated! I went with Kieren's answer, and it seems to have worked.


Tags: administration

cloud

jira-service-management

jira-service-management-cloud

licence

licensing