I'm looking to create a one-stop space for troubleshooting guides and depending what team the user is part of is the pages they'll have access to. Since some of the guides apply to multiple teams, I want to create a page tree that has all the guides, while each team's page tree will have "Include Page" macros to include those guides within each tree that it applies to (this way if the guides change, the change only needs to be done in one place).
I know for this to work, these guide pages will need to be able to be viewed by everyone, but I still don't want users that are limited to their own page trees to access guides for other teams simply because they have a link. Would making the parent page as restrictive as possible, and leaving all the pages under this parent page as permissible as possible accomplish what I am trying to do?
This is the hierarchy I have in mind:
Team members would have access to the page tree that belongs to their team and nothing else, while content managers would have access to the GUIDES page tree, and a few administrators that would update the macros and hierarchy as needed.
Hey there, folks! For most of us, the past six months- yes, you read that right- have been a journey. More people than ever before have pivoted to working remotely, and navigating being on-scre...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events