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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to make public just a single page from private space?

I want to share only a single page from my private space with someone who does not have a Confluence account (just for viewing).

How should I configure the access / permissions settings to share only this single page in:
- Global Permissions
- Space Permissions
- Page Restrictions

I found information about sharing the entire space, but I do not know how to do it for a single page. Of course, I do not want to show other pages publicly in my private space.
Any hints?

3 answers

2 accepted

6 votes
Answer accepted

You will need to make the space anonymously accessible to the whole world, and then restrict the pages you do not want the world to be able to see.

The best way to do this is:

Global permissions:  Allow anonymous access

Space:  Anonymous access

Top level Page 1: No restrictions

Top level Page 2: Restricted to the login group

Other spaces - only logged in users (confluence users) can use, not anonymous

This is terrible. Having thousand of restricted pages. Then you should ALWAYS be awake to REMEMBER any new pages to make them restricted as it should be. Where is the new Steve Jobs to think with the head of the customer again??

Yes! Terrible. It's 2021 and this question pops up for 10 years already and there is no solution. I start regretting advocating confluence for the company.


@Nic Brough _Adaptavist_ is there something on the roadmap for proper sharing?

Atlassian have stated they are not going to break the visibilty/restriction system in this way.

0 votes
Answer accepted

You could try to alloy public access to this space and restict view to all pages exept one.

Isn't there a better way to do this?

To make a single page public within a private space, I would expect the following:

  1. default permissions keeps all pages private
  2. I can enable public view for a specific page

Not the other way around:

  1. set your space public
  2. restrict pages you wish to keep private

My team's confluence space is private, and I would love to make just few pages public. I think this is a common use case.

Me too. I am running into the same need here. Using an explicit allow vs. explicit deny configuration like this is much easier to manage, and safer as well.

LS I'm New Here Nov 19, 2020

I'll add my voice to this. Seems wrong way around. Came looking for exactly this requirement just now.

+1 for me as well. This should be easier and safer.

+1 Export pages just to share them with external workers feels outdated.

The problem with "just let any page be arbitrarily  visible" is that it makes a nonsense of performing any form of structured access.  You'd be into maintining the visibility of every single page you have by hand.

It's fine for a small site with a handful of pages, but imagine trying to do that for a site with 150,000 pages (i.e. the one I'm working with now).

It's a tracking, privacy and compliance deathwish as well, let alone the maintenance nightmare you'd create.

Like Eric Kramer likes this

This is a valid argument. I don't think this should be the default, but an option.

It's common in file sharing services like OneDrive, calendars like Google Calendar or other services to offer a "private" link to a single page or object that can be turned on or off, sometimes with an additional timely restriction.

While this might not solve any usecase or fit every privacy regulation, it would fit a lot of real world scenarios which now end in "Export to PDF" (bad format by default) or "Export to Word" (manual formating needed most of the time).

If I could make a wish for an implementation, there should be an option: "Create private link" which has an additional comment field and expiration date. Anybody who has the valid link can view the page. (I'm OK if there's no comment or edit feature, or it should be optional.)

(If that doesn't work for any reason, at least the default PDF Export shouldn't look as ugly as it does.)

Like Eric Kramer likes this

It could work if you did it at a space level - "allow people to flag public pages in this space" as a flag which you can easily report on and can only be set by system admins.

Like Eric Kramer likes this

I am space admin and struggling with exactly same issue. I need to ensure that I will not loose information accidentally from secured space, so won't make it public as suggested. At same time, particular pages have to be shared with particular people.

Like Masco likes this

Please see the accepted answer, it's the only way to structure a secured space.

Having thousand of restricted pages, not a small work to turn all of it and then leave only that few that should be read by everybody. Then you should ALWAYS be awake to REMEMBER any new pages to make them restricted as it should be. There is a need for a new Steve Jobs to think with the head of the customer, not what is the easiest way for the programmers. 

I think you need to think it through from the point of view of someone who needs their page restictions to work by default and not have to rely on every single author and editor getting it right every time.

Came here looking for a solution to a similar situation.  Equally shocked this isn't an option, as it's how most modern software works ( you can give permissions on a page level as well as at the space level).  Disappointing.  

Ditto everyone here... community wants this feature, atlassian says no... community shurgs and swears off confluence?

I understand that you think you want this, but you don't want the security nightmare it creates.  That's why Atlassian are saying "no", because it's throwing all the security out of the window.

Google docs has worked this way forever, you can have a default setting, and then you can over ride it when you need to.  Maybe for a huge corporation you have to use the more rigid structure that atlassian provides, but its worked fine for me this whole time, and I'd expect atlassian to have this functionality at this point.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

125 views 0 3
Read article

Community Events

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

Events near you