Internal JIRA users, administrators, site admins, jira-servicedesk-users, jira administrators
If I delete internal jira users administrators, and jira administrators would something go wrong in JIRA?
If these are default groups, what is the difference between jira-adminsitratros, site-admins, administrators, internal jira users, and jira service desk users groups?
If all of these groups are not default groups, please list the groups that are default groups that come with JIRA and explain the difference between them.
hi @Fahad Akhtar there are groups that come by default with your installation and I'll attempt to explain them as best I can.
Let's take a look at Product access administration. You might have the same setttings as below
If we go over the 3 groups under Jira Software Product access we read administrators, jira-software-users and site-admins. This means that by adding a user to any of these groups they will count to a product paid license. The jira-software-users has a "default access group" label signalling that new users will get added automatically to that group. This will happen through invite dialog box or signups or other methods available in the product. If you remove the group you'll have to select a new default group for new users.
The administrators and site-admins groups are used to differentiate higher tier permissions and access to modify instance settings like e-mail, groups, payment methods.
Please remember that if a user is in 2 or more groups under the same product they still count towards only one license.
I strongly encourage to keep the minimal group setup that comes with Jira products out of the box. Here is a likely scenario of why you would want to use the 3 groups.
In the jira-software-users you have everyday users who interact and work on the product but have little need for something else. In the administrators group you will have people with the right to change workflows and settings that impact multiple people, usually this group is smaller than the first. Lastly you have the site-admins who may just update biling details or some technical parameters used throughout the site like validating DKIM keys for domain aliasing.
You could potentially run everything with 1 group (site-admins).
Hope this helps and clarifies why the groups are there and how they help.
Adding on to Radu's answer above, as long as you have other groups that serve the same roles, you could theoretically delete the preset ones. You could also just remove all users from them (except your local admin account for safety)
Why would you want to though? Is there a issue with having them, even if you have no members in them?
Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events