You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
My team have a Confluence page with many sub-pages. Can we restrict the blog functionality per sub-page? the reason being that each project is a sub-page and we don't want blog posts relating to project A being broadcast out to project B resources unnecessarily
Hi @Sarah Killeen ,
you can restrict blogposts the same way as you can restrict pages. Use the view + edit restriction here. This way, you don't have to work with labels and you prevent watchers from getting unnecessary mail.
Authors of blogposts should restrict their articles before publishing them. If the project members are organized in Confluence groups, this is done in seconds. (If they're not, create groups.)
Hope that helps!
I agree with @Florian Bonniec
If each project had a space (rather than just a page at a certain level of the page tree in a space with all the other projects) then all blogs within would be about that project.
Or as Florian suggests, if all projects in the one space, then by the diligent use of labels and settings within the Blog posts macro, correct routing of the blogs could be achieved.
Not sure to understand but I would say no. Blog post are stored in another hierarchy in each space. It's strutured base on a date and not any paretn page.
You can change the way you manage the project by for instance create 1 space/project or manage every blog post with labels and display them using the blogpost macro in a more standard page.