Restricted Public Link

[touchlineconnect]

When we have a public link for a space any user accessing that link can then also navigate and access any other public links that we make available.

Is there a way to provide a public link that functions as a unique instance?  That is where users on that public link are not able to navigate from that link to see and access other public links that we make available.

Example we have is publishing a knowledge base or support material for different user types (eg: User and Administrator).  We want these public spaces to be separate unique instances where users cannot navigate from one public space to the other. Visitor in the User space could not navigate from that public space to the Administrator public space.

[Kristian Klima · Accepted solution]

Hi @touchlineconnect 

First of... public links are only intended to be used for individual pages, one-off shares.

If you want to share the entire space, you can enable Anonymous access.

The easiest way to achieve your goal is to create a dedicated doc center from Confluence content.

For example, for our site we're using Scroll Viewport. The reason is that it allows us to keep our Confluence spaces private. Another app that does that is Instant Websites. These two apps build a doc sites from Confluence Content outside of Confluence.

You can also use a theme app like Refined or Spacecraft that that work with Anonymous spaces but provide a nice looking 'skin' over your Confluence.

What ALL apps can do is they allow you to define which spaces you want people to appear in your doc site. They also hide the Confluence UI.

[touchlineconnect]

Thanks Kristian, 

I use Scroll Viewports at the moment for this content so am familiar with that app. It does an excellent job but I find it does restrict the content formatting and UI options.

Public links let us use great content tools like Karma and Aura to format the space content but that formatting is prevented from making it to Scroll Viewport or Instant Websites (have used this one too). 

I will try Refined and Spacecraft to see if that gets me closer to what we would like to provide as a public facing front end for the Confluence content. 

Again, thanks for your help.

[Kristian Klima]

@touchlineconnect 

Most of theme apps will struggle with third-party macros and extensions, but Viewport is pretty pliable (look at ours ;) ) and I think the options are likely to expand.

[touchlineconnect]

Got it thanks Laura, I am indeed trying to manage anonymous access ... got my terms wrong. 

I have tried Spacecraft which I think does a great job with the content but is unacceptably slow to render the content .. we experience 4-5 second lag for content to display after a click. 

[touchlineconnect]

@Kristian Klima your site looks great, well done.  How did you get the icons into the page title like you have for the Documentation section? 

If we can replicate that then I think it will do the job well for us too.

[Kristian Klima]

Thank you @touchlineconnect 

We have our resident Viewport 'hacker' and whatever he does is outside of my skills realm. What I know is that those icons are hardwired to the section titles (page titles) in JS/CSS. :)

[Dave Mathijs · Accepted solution]

Hi @touchlineconnect 

Each public link corresponds to one content item only. If you turn on and share a public link for a content item that has any child items, the public link will only reveal the parent item, not any of the child items. To share the child items too, you’ll need to turn on their public links and share each of them individually.

So I don't really understand your question. There's a difference between the public link of a page and a public space (with anonymous access).

[touchlineconnect]

Thanks for the input Dave.  What my users see is access to all spaces in the Space menu for any spaces we have a public link set for.  My question is whether we can hide the access to other spaces from this public link.  See image for current view for users accessing any of the public links we have.

[Dave Mathijs]

I see. In Confluence Cloud, users can only see the spaces they have permission to access. When a user clicks on "View all spaces" in the navigation bar, they will only see the spaces where they have at least view access. If a user does not have permission to access a particular space, that space will not appear in the list for them. This is controlled by the space permissions set by the space administrators.

But if you have view access, then you will see that space, you cannot "hide" it.