What Is a Confluence Folder
A Confluence folder is a way to group related pages together within a space, making it easier for teams to find and manage documentation. Folders act as containers that hold pages, and they can be nested to create a hierarchy. This structure helps teams keep their knowledge base organized instead of letting pages pile up on the dashboard. When you create a folder, you are essentially building a logical path that others can follow to locate the right information quickly.
More from this site
Keep reading the latest coverage
Folders are especially useful for teams that follow a standard naming convention or need to separate content by department, project phase, or topic. Because Confluence spaces can become crowded fast, using folders gives you a simple way to maintain order without needing external tools.
How to Create a Confluence Folder
To create a folder in Confluence, navigate to the space where you want to organize your content. Click the "Create" button and choose "Folder" from the template options. Give the folder a clear name that reflects what it will contain, such as "Engineering SOPs" or "Marketing Campaigns." You can then add pages directly inside the folder or move existing pages into it by dragging and dropping.
If you need a deeper hierarchy, you can create subfolders inside a parent folder. This is helpful when you want to separate active work from archived material, or when you have multiple teams sharing a single space. Keep the nesting shallow — two levels are usually enough to stay organized without losing sight of your content.
Best Practices for Using Folders in Confluence
Use Clear and Consistent Naming
Name your folders with terms your whole team will understand. Avoid vague labels like "Misc" or "Stuff." Instead, use specific names like "Q3 Product Launch" or "HR Policies." Consistency across spaces makes it easier for anyone who joins the team later to find what they need.
Keep Permissions in Mind
When you add pages to a folder, permissions are inherited from the space or the parent page. Before creating a folder, consider who needs access. If you have sensitive documentation, place it in a folder with restricted permissions rather than relying on the entire space to be private.
Limit the Number of Folders
Too many folders can make navigation just as confusing as having none. Aim for a structure that balances breadth with depth. If a folder contains fewer than five pages, consider whether it should be merged with another folder or whether a label would be a better organizing tool.
Confluence Folder vs. Labels: When to Use Each
Both folders and labels help you organize content, but they work differently. Folders create a fixed hierarchy, which is useful when the structure of the content is stable and predictable. Labels are more flexible and allow a single page to belong to multiple categories, which is helpful for cross-cutting topics like "urgent" or "onboarding."
A good rule of thumb is to use folders for primary navigation and labels for secondary filtering. For example, you might have a folder for each project and then apply labels for status, such as "draft," "review," or "approved."
Managing Confluence Folders Across Teams
As organizations grow, a single space might serve multiple teams. In these cases, folders act as a lightweight way to divide ownership without creating separate spaces. Each team can manage its own folder, add pages, and set page-level restrictions while still contributing to the shared knowledge base.
Regularly reviewing folder structure — every quarter or at the start of a new project — helps prevent stale content from cluttering the space. Archive folders that are no longer in use and document the folder structure in an index page so new team members can orient themselves quickly.