You need to set up the space permissions to allow "someone who can log in" to see the space, but not do anything else. Then, for people who should be able to write to the space, add them separately with more rights.
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)
I attended Atlassian Summit 2019 and learned a lot from the presenters, attendees and knowledgeable Atlassian product managers. The presentations I attended focused on applying Agile, pla...
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