You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Our Jira admin recently retired and I have been tasked with taking over. Honestly, this just slipped through the cracks when she left and I forgot to go through it with her. I'm hoping you can help me out so that I don't have to bother her about it.
There are several Groups that I don't think we need any longer. I can't find them being used, but I also don't want to just delete a Group that may be "system" vital. I'll just list them below and I'd welcome anyone with feedback.
balsamiq-mockups-editors
_licensed-bamboo
_licensed-confluence
_licensed-fecru
_licensed-jira
_no-one-at-all
Obviously the Jira and Confluence ones raise an eyebrow, but I have other accounts that I believe to be more current...site-admins, administrators, users, confluence-admins-..., confluence-users-...
Hi @Robb Stohlman,
Welcome to Atlassian Community!
Those groups are leftovers from when Cloud was known as OnDemand and were used to prevent password reset for the system administrators. These are no longer used so you can remove them if you like.
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.