Skip to main content
A page is a document. It can be anything — a technical spec, a retrospective, a runbook, an onboarding guide. Pages live in a tree structure inside their Space and can be nested to any depth to match the way your team thinks about information.

​
What a page contains

Every page has the following fields.
FieldDescription
TitleThe name of the page, shown in the sidebar and search results
BodyRich text content powered by the Plate editor
StatusWhere the page is in its lifecycle (see below)
AuthorThe member who created the page
TagsOptional labels for filtering and discovery
Custom fieldsConfigurable key-value metadata for your team’s workflows
TasksAction items embedded directly in the page content

​
Page statuses

Pages move through a five-step lifecycle. The status tells every reader exactly how much to trust the content.
1

DRAFT

The page is being written. It is visible to Space members but not yet ready for review.
2

IN_PROGRESS

Active work is underway. Use this to signal that a page is being substantially revised.
3

IN_REVIEW

The page is ready for feedback. Use this to request comments or approval from colleagues.
4

PUBLISHED

The page is ready for its intended audience. It is fully indexed by global search.
5

VERIFIED

The page has been reviewed, confirmed accurate, and approved. This is the highest-trust status.
Change the status to IN_REVIEW when you want feedback, and to PUBLISHED when it is ready to share. Set VERIFIED after a formal review cycle to signal that the content has been signed off.

​
Page tree structure

Pages in a Space are arranged in a tree. You can create a top-level page or nest a page under any existing page to any depth. This lets you model your information architecture exactly — for example: 
Engineering
├── Architecture Decision Records
│   ├── ADR-001: Database selection
│   └── ADR-002: Authentication strategy
└── Runbooks
    ├── Incident response
    └── Deployment checklist
Drag and drop pages in the sidebar to rearrange them. The tree is visible to all Space members based on their permissions.

​
How to create a page

1

Click New Page

In the Docs sidebar, click New Page in the top bar. To create a nested page, right-click any existing page and select New subpage.
2

Give it a title

Type a title. The title appears in the sidebar, search results, and browser tabs.
3

Choose a type

Select Standard for regular documentation or Blog if you want the post to also appear in the Intranet feed.
4

Write your content

Use the rich editor to write your page. Type / to open the command palette and insert any block — image, table, code block, callout, and more.
5

Set the status

When the page is ready for others to read, change the status from DRAFT to the appropriate level. Use IN_REVIEW to request feedback or PUBLISHED to make it visible in search.

​
Rich editor capabilities

The Plate editor supports a full range of content blocks.
Drag and drop images into the editor or use the /image command. Images are stored in your Collabase instance.
Insert a table with /table. Add and remove rows and columns by right-clicking any cell. Tables support rich text inside each cell.
Insert a code block with /code. Select the language for syntax highlighting. Code blocks are ideal for commands, scripts, and configuration snippets.
Insert a callout with /callout. Use callouts to highlight important information, warnings, tips, or notes so readers do not miss them.
Insert a math block with /math. The editor renders LaTeX equations inline and as display blocks.
Insert a diagram with /diagram. Diagrams open the embedded Excalidraw editor and are saved directly in the page.
Paste any URL to embed external content — videos, Figma designs, and other supported providers render inline.

​
Permissions

Pages inherit the permission model of their Space.
  • Members can create, edit, and comment on pages.
  • Viewers can read pages. If the Space allows viewer suggestions, Viewers can also leave comments and propose edits.
Specific folders — meaning a page and all its subpages — can have their own access restrictions. This is useful for keeping sensitive runbooks or internal documents visible only to a subset of the Space membership.
Folder-level restrictions narrow access; they cannot grant access beyond what the Space permission already allows.

​
Version history

Every time a page is saved, Collabase records a new version. To browse the history, open a page and click the History option from the page menu. You can compare any two versions side by side and restore any previous version with one click.