Folder Structure ((better)) | Confluence

Best for: Agencies, Consultancies, or PMOs where work is temporary. This structure organizes information by deliverable.

Confluence allows you to restrict viewing/editing on pages. While you can use restrictions to hide "sensitive folders" (e.g., HR Salaries), overuse of restrictions creates a fractured user experience. Users will see empty folders they cannot access. confluence folder structure

Search is powerful, but only if you use it right. Encourage the team to use prefixes. Instead of "Meeting Notes," use "2023-10-12_Product Sync." Use Page Tree Macros Best for: Agencies, Consultancies, or PMOs where work

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 While you can use restrictions to hide "sensitive

The perfect Confluence folder structure is not static; it is iterative. Start with a broad structure (The Root Parents) and allow your team to create the child pages they need. Review the Page Tree report every quarter. If a folder has more than 20 children, it is time to create sub-folders (new Parent Pages). By combining a logical hierarchy with strict naming conventions, you transform Confluence from a dumping ground into a powerful knowledge engine.

| Traditional Term | Confluence Equivalent | Function | |----------------|----------------------|----------| | Root Directory | | High-level container for a team, project, or department. | | Subfolder | Parent Page | A top-level page that serves as a table of contents or category. | | File | Child Page | A page nested under a parent; inherits permissions and styling. | | Path | Breadcrumbs & Page Tree | Visual navigation showing hierarchy. |

Here are some examples of Confluence folder structures: