Exclude-strategy for pages of space export

In Confluence 5.1 we want to exclude certain pages from space PDF (possibly Scroll HTML) export for certain customers.

So far this is / was done by restrictions to single (parent) pages, which is a royal pain in the neck as one needs to name half a dozen groups in Restrict (which actually is an Allow) to exclude a single one. The export is then done with a user from the group to be excluded.


4 answers

1 accepted

0 votes
Accepted answer

Guess I ll have to stick with page-wise export exclusion with permissions. <sigh>

I am afraid I don't fully understand your question or what you do.

If you export a space to PDF you can explicitly define which pages should be included and which not. If you want to exclude smaller units (e.g. chapters within a page) you can achieve that with a noprint macro.

Perhaps you could describe your problem in more detail if this is not what you are looking for?

Thanks, Steffen, for your suggestion!
It s no option that I manually go through the include / exclude.

I checked the noprint macro. I don t think this would be any easier than the current cludge.

The pain point with the current approch is / was that I have to name several groups to allow them to view the page - to exclude one group. If there is a new group I need to add it to all pages.

If I could negate this / turn the view restriction logic around it would actually be THE solution. Or maybe to add a group to all pages marked restricted through an API would be good.

Thanks again


I think I finally understand your point. Have you had a look at this page. I think it deals with the same topic.

Do you need a solution for page exports only or is it really about restricting the visibility of pages and the export is just a byproduct?

Yeah, counterintuitive or counterproductive would be a great term for the combination of permissions (at space level) and restrictions (at page level). ;-)

And why does regular support always have the non-answers (see below) and do external people hit the point? <grrrin>

But what product does not have its deficiencies?

On a constructive note:
I guess I m over the worst that I added an additional "restriction" <arrrghh> group to several dozen pages.

And yes, we need it for both - to restrict (really! <g>) visibility and export of pages.

Remains the question: Do you know off the top of your head how to programmatically iterate over the already "restricted" pages to add another group? Or as said to negate a real restriction? Or file an enhancement request for real restrictions? But what do we call it then? <g>

Or do you have something entirely different up your sleeve?


Guess I ll have to stick with page-wise export exclusion with permissions. <sigh>

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...

1,042 views 51 8
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you