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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have thousands of confluence spaces under which there are many pages again. I just want to understand what policies should we set up on the basis of which we can archive certain spaces.
This is entirely up to you.
Most people would archive spaces that are no longer of much use, but they don't want to lose completely. This may happen when a product goes out of support, an organisation changes structure, someone notices that no-one is reading or updating the space, and so-on.
Your policies for archive really need to be decided by you. We can't really give you any solid rules, as we're not running your organisation and we don't know what you need from your Confluence or the data within it.
Thanks for the reply. I guess I will have to find a way to finalise the policies.
Is there any way in confluence where i can create a query to find the pages that have not been updated in like a year.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.