You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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
Atlassian have stated they are not going to break the visibilty/restriction system in this way.
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?
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 :(
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:
Not the other way around:
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.
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.
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.)
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.
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.
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.
@ 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.
This feature was released in December 2021!
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.
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.
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 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.
I am with @Daniel Opoku 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
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:
The view-only version of the page hides most Confluence macros. People that access the view-only version can only see the following macros: