How to make public just a single page from private space?
Asked by Damian ?liwa:

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?


Answers:
author: Nic Brough -Adaptavist-
body: 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

comments: author: Masco
body: 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??


author: Cristian Serb
body: 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-](/t5/user/viewprofilepage/user-id/781454) is there something on the roadmap for proper sharing?


author: Nic Brough -Adaptavist-
body: Atlassian have stated they are not going to break the visibilty/restriction system in this way.


author: Tomas Sleurs
body: Some really basic functionalities missing in Confluence.

Consider me having a Space with over a hundred seperate pages and want to make public 3 of the pages within this Space. I then have to firsst make the entire Space public to the internet (even though it has critical business information and confidential information) and then per page say which page is restricted for all but the 3 pages I want to leave public?


author: Pierre Lonchampt
body: I agree with the general consensus that this is really a missing feature that one wonders why and how a modern product could still succeed without :(.

That said - there is I believe one "trick" that sounds (to me) simple and should work for many cases, and be less risky. Rather than make public a whole "internal space" and restrict pages in this space, why not keep the internal space actually private, and then:

A/ Create a new "shared/public" space.

B/ Move the page you want to share into this space

C/ Create a link to this now public page from within the private space.

Note also that free plan users don;t have the ability to restrict anything at all :(


author: Vasiliy Zverev
body: You could try to alloy public access to this space and restict view to all pages exept one.


author: rudolf_jurisic
body: 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.

comments: author: Paul Weiss
body: 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.


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


author: Kjetil Brekke
body: +1 for me as well. This should be easier and safer.


author: Nicolas Keller
body: +1 Export pages just to share them with external workers feels outdated.


author: Nic Brough -Adaptavist-
body: 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.


author: Nicolas Keller
body: 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.)


author: Nic Brough -Adaptavist-
body: 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.


author: ????? ?????
body: 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.


author: Nic Brough -Adaptavist-
body: Please see the accepted answer, it's the only way to structure a secured space.


author: Masco
body: 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.


author: Nic Brough -Adaptavist-
body: 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.


author: evanbartlett
body: 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.


author: Todd Foley
body: Ditto everyone here... community wants this feature, atlassian says no... community shurgs and swears off confluence?


author: Nic Brough -Adaptavist-
body: 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.


author: evanbartlett
body: 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.


author: Tomas Sleurs
body: @ Nic Brough  

The security nightmare is when you first need to make an entire space, full of critical business and confidential information, public before you can start restricting access. Or is this something Atlassian does not see?  

There is literally NO security risk in having a space that is completely restricted with certain pages inside it that are public while the rest of the space remains private. Also it would be a very easy thing to visually show which pages are shared by just adding an open eye-symbol to the pages that are public or just the text \[PUBLIC\] next to it.


author: Anton Andreasson
body: How about generating a \`?secretKey=somehashgoeshere\` on a per page basis that opens up the page in question to anyone with the correct URL?

And configurable expiration dates for each key and access management to restrict key generation.


author: rudolf_jurisic
body: This feature was released in December 2021!

<https://support.atlassian.com/confluence-cloud/docs/share-content-externally-with-public-links/>

1. As admin, allow the public links feature (Settings \> Public Links)  
   ![Screenshot 2022-01-13 at 13.42.29.png](https://community.atlassian.com/t5/image/serverpage/image-id/177616iCB87A02149EE4C6A/image-size/large?v=v2&px=999 "Screenshot 2022-01-13 at 13.42.29.png")  

2. As Confluence user, turn it on/off for specific page

![screenshot_2021-12-21_at_11.12.11.png](https://community.atlassian.com/t5/image/serverpage/image-id/177614i2D95EFEC5F45C458/image-size/large?v=v2&px=999 "screenshot_2021-12-21_at_11.12.11.png")

comments: author: evanbartlett
body: Is this "public" as in anyone outside of your organization? I think the OP was asking more about sharing it with a group inside her organization. I've got the same question, I've got content in a private space, and I want to make a single page accessible to other users within my company.


author: rudolf_jurisic
body: This is part of the question asked:

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


author: Daniel Opoku
body: Music to my ears, I have pretty much the same requirement as you Rudolf, but I can't see this option in settings, and I am a Site Admin using Confluence on the Cloud. Same on the individual page, looks the same except no Public Links button.

![Screenshot 2022-01-24 at 10.55.34.png](https://community.atlassian.com/t5/image/serverpage/image-id/179398iBD26A20D4F2B8597/image-size/large?v=v2&px=999 "Screenshot 2022-01-24 at 10.55.34.png")


author: rudolf_jurisic
body: Hm. It's possible that new features rollout differently for specific regions or something like that.


author: Daniel Opoku
body: Frustrating. I'll keep investigating. For info, I'm in the UK so anyone with this working or with ideas on what I might be missing please chip in!


author: Joe Norton
body: **Calling this solved is a joke.** Why on earth should it be required to publish our entire internal documentation library to show one page to customers. We should have gone with Notion.


author: gera
body: Please, consider making noise in **<https://jira.atlassian.com/browse/JSDSERVER-11299>** so the feature we all want gets visibility, the permissions scheme of allow-by-default-then-dont-forget-to-restrict is ridiculous.


author: Will Hall
body: Confluence still has many benefits but there are so many low hanging fruit items (features) that Atlassian just continually struggles to provide as enhancements, including this one.   

As users of other applications we have all most likely experienced this functionality mentioned here in other apps for years. Whether it be Google Docs. Or now MS OneDrive 365.   

As well as many of the newer tools continually coming online, Notion.so comes to mind.  

And in regards to security concerns of single public page sharing, those can be resolved by notifications in the UI and reporting on the backend - of which pages are public and which are not. The public pages just need the necessary controls.

comments: author: Will Hall
body: And after some additional research today I just discovered the 'Public Links' feature.  

<https://confluence.atlassian.com/ge/public-links-979425312.html>  

Very nice enhancement, I stand corrected.


author: Nicolas Keller
body: This would be awesome. I can't find it yet on my Confluence page (Site Admin, Cloud version) and the page you've linked is part of the [Cloud Growth](https://confluence.atlassian.com/display/GE/Home "Cloud Growth") documentation ("This space contains the documentation for features that are still under development. It is not a permanent part of the Atlassian Cloud documentation.").

So I guess we'll have to wait for the release but the feature sounds awesome and would be a solution to our initial request, so I gladly wait some more time if they'll implement it that way.


author: Daniel Opoku
body: Couldn't see it in my settings yet either, so I'm guessing almost 8 months later and we're still waiting on this?


author: Yatish Madhav
body: I am with [@Daniel Opoku](/t5/user/viewprofilepage/user-id/4005575) on this as well. I would like to try this out but the Public Links setting is not yet showing for me :(. Please advise if anyone has found a workaround or got this working for view only for specific groups (non-Confluence linked) only? Thank you


author: Nicolas Degardin
body: I'm waiting for it too...

I would have expected to provide a publicly accessible page showing what's in the upcoming release to teams that don't use JIRA but need to be aware, via a Confluence public page, instead of always sending them the release notes manually.

And I was already conceiving similar use cases.

But that block in the documentation already makes it look a bit useless to me:

*** ** * ** ***

Macros that non-users can see {#toc-hId--1180756887}
----------------------------------------------------

The view-only version of the page hides most Confluence macros. People that access the view-only version can only see the following macros:

* [Status](https://confluence.atlassian.com/confcloud/status-macro-724765291.html)

* [Table of Contents](https://confluence.atlassian.com/confcloud/table-of-contents-macro-724765294.html)

* [Info, Tip, Note, and Warning](https://confluence.atlassian.com/confcloud/info-tip-note-and-warning-macros-724765216.html)

* [Code Block](https://confluence.atlassian.com/confcloud/code-block-macro-724765175.html)

* [Expand](https://confluence.atlassian.com/confcloud/expand-macro-724765195.html)

* [Excerpt](https://confluence.atlassian.com/confcloud/excerpt-macro-724765191.html)

* [Profile Picture](https://confluence.atlassian.com/confcloud/profile-picture-macro-724765268.html)

* [Roadmap Planner](https://confluence.atlassian.com/confcloud/roadmap-planner-macro-724765275.html)


author: Rabih Matar
body: I found a way to grant access to a single page.

you will need to create a new project and link the page you want to share in this new project.

Then you grant anonymous access on this new project.

Result: Single page shared with no menus and no other pages seen.


Tags: permission