Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Confluence Space Access

Currently a space in Confluence could allow anonymous read access (open to the public without authentication) and/or to specific users/user groups (via authentication). We've run into a use case where the content in the space is proprietary and we would like only authenticated users to be able to read instead of the general public. Will Atlassian implement a way for logged in users to have space/site access and view content that is not anonymous?


Yi Zhang
Information Technology Services
University of Connecticut


Um, I'm not sure "will Atlassian do this" is a good question.   As Confluence has been able to do this, since, if memory serves, 2004.

The really simple way to do it is:

  • Put public stuff in spaces that you allow anonymous access to
  • Put stuff for authenticated users into spaces that do not allow anonymous access

You can try looking at page restrictions

  • Put 2 root pages with anonymous access to all
    • One where every has page access
    • The other where only authenticated user groups have access
  • Nest pages accordingly


Its not recommended though because people forget and put things under the wrong root


Actually, it is very strongly recommended as the best way to mix "public access to some stuff" with "restricted access to the rest"

I'm sorry for the confusion. What I'm looking for is read-only access to a space for all our users who can authenticate through our ID system. Currently read-only access requires a Confluence license and we can't possibly purchase licenses for all faculty, staff and students to read proprietary content. 

Yes, if you're creating accounts and requiring people to log in, then they will use a licence up.  That's the definition of a licence usage - "someone who can log in".

If you enable anonymous access, then you can set up spaces so that people who have not logged in (and hence do not use a licence) can see the content.

So, the answer is "stop authenticating your people who don't need to log in" and make some of your spaces anonymously accessible (read only) to them.

Like the customer portal in Jira Service Management, any active user from our LDAP directory could log into the customer portal and submit a ticket without consuming a license. Can something similar be done on the Confluence side so that a site can be restricted to all active users who can authenticate through our ID system to only read the content without a license? The use case here is that a space has proprietary content that it's OK for our active users to read but not the general public.


If you want someone to see Confluence, you have to grant them access to see it.  This means they have to be Confluence users (which is "can log into Confluence" or via their Jira Customer account for a knowledge base), or you can grant anonymous access so they do not log int.

You need to make up your mind whether these people are Confluence users or not.  If they are, they need a licence.


If you're on Cloud, you could achieve that using our app Scroll Viewport for Confluence.

You can publish your Space as a Viewport site and setup authenticated access so that only people with a certain token are able to view the space.

Would that work?


Log in or Sign up to comment

Atlassian Community Events