---
key: create-a-knowledge-base-page
title: Create a knowledge base page
audience: staff
section: resources
routes: ["/resources/knowledge-base", "/resources/knowledge-base/:slug/edit"]
permissions: ["knowledge_base.pages.create"]
features: ["knowledge_base.core"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Write a new how-to, checklist or procedure for your team in the knowledge base, start from a layout, save it, and publish it when it is ready.
keywords: [wiki, how-to, procedure, SOP, team notes, write a guide, checklist page, safety note, internal docs]
related: [find-or-restore-a-knowledge-base-page, find-your-way-around]
---

In the sidebar, open **Resources**, then **Knowledge Base**. The page address is `/resources/knowledge-base`. The knowledge base is one place for your team's how-tos, checklists and procedures. Anyone whose role can read the knowledge base can read a published page; the people who can write are set by role.

## Before you start

- Your role needs permission to create knowledge base pages. Without it the **New page** button is hidden.
- A new page starts as a draft that only its authors see. Nothing is shown to the rest of the team until you press **Publish**.

## Steps

1. Press **New page** at the top right. The **New page** drawer opens. (If your knowledge base is still small, the **Getting started** box also offers **Create a page**.)
2. Type a **Page name**, for example how to winterize a furnace.
3. Under **Page location**, leave **Top level** selected, or choose **Inside a page** and pick a parent from **Choose parent page** to file it under an existing page.
4. Under **Start from a layout**, pick a starting shape if one fits: **Step-by-step guide**, **New team member**, **Fix-it checklist**, **Job checklist**, **Safety briefing** or **Maintenance schedule**. **Blank page** starts empty.
5. Press **Create page**. Nova opens the editor.
6. Write the page. The buttons above the text add headings, lists and links. Add a one-line description under the name so people can find it in search.
7. Press **Save**. The editor shows **Saved** for a moment; **Unsaved changes** means you still have work to keep.
8. When the page is ready for the team, press **Publish**.

## What you see

- The editor keeps a draft copy as you type, so **Draft saved** may appear before you press **Save**. Only **Save** writes the page itself.
- Leaving the editor with unsaved work brings up a prompt so nothing is lost by accident.
- Back on the dashboard, your unpublished pages are listed under **Your work in progress**, and a published page appears under **Recently updated** and in the **Page outline**.
- Tags and an icon can be added in the editor to make the page easier to spot.

## If something looks different

- The page reads **The knowledge base isn't turned on**: ask an administrator to switch it on for your organization.
- **Create page** shows a red message asking for a name: the **Page name** is empty. Choosing **Inside a page** without a parent shows a similar message.
- **Publish** is missing in the editor: your role can write pages but not publish them. Save the draft and ask someone with the publish permission.
- You cannot find the page you just made: see [[find-or-restore-a-knowledge-base-page]].

[[route:/resources/knowledge-base|Open the Knowledge Base]]