A folder structure is useless if users cannot guess where a page lives. Enforce strict naming conventions.
Master Your Confluence Folder Structure: A Guide to Organized Spaces
Limit the number of top-level pages (Root Parents) to between 5 and 9. Cognitive load theory suggests humans struggle to process more than nine options at once. Common Root Parents include: confluence folder structure
Never delete old content; move it. Create a top-level parent called . When a project finishes or a policy is obsolete, move that page tree into Archives. This keeps the active workspace clean but preserves history.
To implement a robust structure, follow these specific steps: A folder structure is useless if users cannot
Best for: Product teams, IT Support, or Customer-facing help centers. This structure is topic-centric.
Here are some best practices to help you set up a effective Confluence folder structure: Cognitive load theory suggests humans struggle to process
Before content is ready for the team, let users draft it in a personal space or a designated "Sandbox." This keeps the main departmental spaces clean and verified. The "Archive" Folder is Essential
| Pitfall | Consequence | Solution | |--------|------------|----------| | Creating >20 top-level parent pages | No hierarchy; users get lost. | Group related parents under a single "Index" page. | | Using pages instead of child pages | Loses navigation context. | Convert to parent–child via Move → New parent . | | Over-reliance on page links instead of hierarchy | Broken links when pages move. | Prefer nesting over manual links. | | No space for stale content | Cluttered "folder" view. | Create an _Archive parent page or separate Legacy space. |