If you truly want the content to be hidden however you need to combine the visibility plugin with the page include plugin. The reason for this is users could just view the source of the page (tools menu -> view source, or if they have edit permissions they could just edit the page and see the information, also the search engine will index the content so they could see it in search. If you truly want it hidden what you need to do is put the content to be hidden on its own page and then give it a viewing restriction to the group or people that view it. Then on another page you would include the hidden content page onto that page and wrap it in the visibility plugin with the save view restrictions that were assigned to the hidden content page. The reason for wrapping the include macro with the visibility macro is to avoid the error that would be shown to users who don't have viewing rights to the hidden content. This is the way to truly make the content hidden.
You made a really good point. The users of the page won't have edit permissions. But I love your approach to use the include plug-in and restrict the content. If only the include plug-in would render nothing if the user doesn't have permission. Or even better, give us the option to either display an error or nothing.
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs