Creating a new page in Confluence helps teams organize documentation, projects, and knowledge in a single, shared space. This quick start guide walks you through the essential steps so you can get started fast and keep your workspace structured.
Use the following reference points to plan your Confluence page structure and permissions before you build out content.
| Step | Action | Where in UI | Why it matters |
|---|---|---|---|
| 1 | Select the space where the page will live | Space directory or sidebar | Controls visibility and team context |
| 2 | Click Create and choose page type | Top right Create menu | Defines blank page or template use |
| 3 | Add title and page labels | Title field and Labels sidebar | Improves search and cross-linking |
| 4 | Set parent page and outline structure | Parent page selector and heading styles | Organizes hierarchy and navigation |
| 5 | Insert content blocks and macros | Insert menu and slash commands | Enables rich elements like tasks and diagrams |
Create your first Confluence page
Start by signing into Confluence and opening the target space. From the space homepage, click the Create button in the top right corner. Choose Page to begin with a blank canvas, or select a template if you want predefined sections and styling. A clear, descriptive title helps teammates quickly understand the purpose of the page.
After you create the page, set the parent page to establish the right location in the site hierarchy. Use the sidebar to add labels that describe the content, such as project name, product version, or department. These metadata choices make the page easier to discover through search and improve overall navigation.
Use the editor toolbar to format headings, lists, and links so that information is easy to scan. Break content into sections with clear headings and insert relevant macros for diagrams, tables, and task lists. Save your work frequently and share the page with the appropriate teams to encourage collaboration and feedback.
Organize content in a clear hierarchy
A well-structured Confluence site uses parent and child pages to represent relationships and priorities. When you create a new page, decide whether it should sit at the top level under a space or as a subpage under an existing topic. Nesting pages logically reduces clutter in the space sidebar and makes it easier for readers to follow the flow of information.
Use headings consistently, moving from
to deeper levels only when you need subsections. Limit each parent page to a handful of key child pages to keep navigation intuitive. Periodically review the hierarchy and archive or restructure pages that no longer align with team goals.
Consider adding a page index or table of contents macro on key parent pages to help users jump directly to the section they need. This practice is especially valuable in large spaces where dozens of pages support ongoing projects and ongoing documentation efforts.
Use templates to speed up page creation
Confluence templates standardize layouts and ensure that critical information is never missed. You can use built-in templates or create custom ones that reflect your team's preferred structure and branding. Templates are ideal for project charters, meeting notes, incident reports, and onboarding documentation.
When you create a new page from a template, you can keep the template title or customize it for the specific context. Populate required sections early, such as purpose, stakeholders, and success criteria, so that readers get the context they need within seconds. Encourage team members to suggest improvements to templates so they evolve with changing workflows.
Store frequently used templates in the space gallery or personal favorites for quick access. Review templates regularly to remove outdated sections and align them with current compliance or quality standards within your organization.
Configure permissions and page restrictions
Permissions determine who can view, edit, or restrict a Confluence page. When you create a new page, consider the audience and sensitivity of the content before adjusting these settings. Use space-level permissions for broad access and page-level restrictions for confidential information.
Limit editing rights to content owners while allowing broader view access to stakeholders. Use the Restrictions option to specify individual users or groups who can edit or comment, and document any special access requirements directly on the page. Review permissions periodically to ensure that former team members no longer have unnecessary access.
Communicate permission changes to relevant teams to avoid confusion and maintain smooth collaboration. Clear documentation about who can change what reduces support questions and unintended edits to important pages.
Plan and maintain resilient documentation structure
- Define a clear naming convention for page titles and labels to support consistent search results.
- Use templates for recurring page types to reduce setup time and maintain content quality.
- Establish a logical page hierarchy with parent and child pages that reflect team workflows.
- Review permissions and archive outdated pages on a regular schedule to reduce noise.
- Leverage labels and linked pages to connect related topics and improve cross-team visibility.
FAQ
Reader questions
How do I create a child page under an existing topic in Confluence?
Open the parent page, click the More menu (three dots), and select Create Child Page. Enter a title, choose a template if desired, and confirm the page will be nested under the current topic in the hierarchy.
Can I change the parent page after I have created a Confluence page?
Yes, use the Move page option from the More menu to relocate the page under a different parent. Confirm the new location so that links and navigation update correctly, and check space permissions after moving.
What happens to page labels when I copy a Confluence page?
Copying a page duplicates the content and labels by default, but you can edit the labels in the new page to better fit the target context. This helps maintain consistent tagging while allowing adjustments for the new purpose.
How can I prevent unauthorized edits to a critical documentation page?
Restrict editing permissions using the Page restrictions option, limiting access to specific users or groups. Combine this with clear ownership assignments and scheduled permission reviews to protect sensitive information over time.