Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Restrictions applied to 'include page' macro

Javier Lopez June 21, 2024

Hello guys !

 

Need your thoughts about this one please 😀

I have two different spaces:

  • One for internal use: Only the members of the team can view/update ...
  • One for public: Anyone can review those documents.

We want to create and maintain all the documents in the private space but there are some documents that we must share with external people. For these cases, I thought about the 'Include page' macro.

 

But when I set it up, I realized the document is not shown for the external users because it's restricted in the main space.

 

-> Restrictions apply: There are inherited view restrictions. 😁

 

 Any good idea you can think about to bypass this issue and to avoid publishing and maintaining the same document in two different spaces ?

 

Regards

Javier

2 answers

0 votes
MJ Valencia -drawio diagrams-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 21, 2024

Hi Javier, have you tried using the Comala Publishing app? I think it suits your needs. You can write and update your documents in your private space, and then easily publish them to another space where external users can view them without restrictions. This way you won't have to maintain two versions of the same document. 

Hopefully it saves you some time and hassle.  

Javier Lopez June 24, 2024

Hello.

Will review this option.

 

Thank you

Javier

0 votes
Shawn Doyle - ReleaseTEAM
Community Champion
June 21, 2024

This is working as designed.  If your first space is restricted, those restrictions will carry over to any other spaces via the include macro.

You could move the page in question to an unrestricted space and share it from there.

Javier Lopez June 24, 2024

Hello Shawn.

 

Yes, I do know this is working as expected and I understand it, indeed.

I'm looking for a way to bypass this restriction, if there is any other than publishing the document twice, as I said in my post.

Thank you

Javier

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events