I can understand the starting point, but I don't like the way Atlassian default the privileges to "anyone who can log in". It's fine for open access stuff, but a large amount of the users of their software do have legitimate reasons to close some of the access, and the by the time they realise they need to do it, spaces and projects with copies of the default "open" access have proliferated, making it a bit of a nightmare to revise. You only need to deal with this once, but it's still a pain. (I had to do it for a 1000 project Jira once. That was "fun")
I am afraid you'll need to review every single space that might be using the "can log in" group to allow access (generally, that's confluence-users)
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs