I have several pages with reusable text that I'm using throughout my knowledge base site. Although it is currently a private site, it will eventually be public. I want the public to be able to see the content of the inserted pages but I don't want the inserted pages to show up in the navigation pane. When I restrict permissions on my reusable text pages, they disappear from the navigation pane for the public, but the macro also cannot display their content.
For example, I have a page that just says "No additional information provided." On my knowledge base pages where there are no additional instructions in the section we call "Guide for Use," I use an "insert page" macro to display this text so that if we eventually decide to change how we say this, I only have to update it in once place instead of dozens. I do not want any of my reusable text pages, including "No additional information provided," to show up in the left-hand navigation pane for public users because it's confusing.
Is there a way to solve this problem?
Hi @Sydney Edlund,
Only the descendants of a space's Overview (homepage) appear in the page tree.
You can move your reusable pages to be siblings of the Space Overview. This effectively hides them from your users if navigating using the sidebar.
The easiest way to do this is in Space Settings -> Manage pages -> Reorder. On this page you will be able to drag and drop the pages outside of the Space Overview's tree as well as access them if you need to edit them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sydney Edlund I am afraid in your setup it cannot be done.
See the note regarding page permissions in the macro definition page.
https://support.atlassian.com/confluence-cloud/docs/insert-the-include-page-macro/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sydney Edlund You will not be able to hide the pages in the navigation. We have had the same issue and the way that we solved it was to create page excerpts and then use the insert excerpt macro. https://support.atlassian.com/confluence-cloud/docs/insert-the-excerpt-macro/
This allowed us to create excerpts on one page that could be updated and update content across all the pages. It also did not create pages we did not want in the navigation. To help manage our master excerpt pages we created a page that we listed them on with the excerpt that it housed. This page we locked down using page restrictions so only our internal team would see it. https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.