Skip to content

Pages ​

Pages are Plane's documents. Use them for specs, meeting notes, runbooks, decision records, onboarding guides, and anything else your team writes down. Every page opens in the same collaborative editor, so several people can write in it at once, comment inline, and embed live work items next to the text.

Pages

Where pages live ​

A page always belongs to one place. That place decides who can see it and which features it gets.

Kind of pageLives inWho can see it
Project pagesThe Pages section of a projectProject members (public pages), or only the page owner (private pages)
Wiki pagesThe workspace WikiWorkspace Admins and Members (public pages), or the owner and people they share with
Teamspace pagesThe Pages tab of a teamspaceTeamspace members. Teamspace pages are always public to the teamspace.

Use project pages for documentation tied to one project's work. Use the wiki for knowledge that crosses projects and teams, like company policies or architecture decisions. Use teamspace pages for a team's own processes and guidelines.

You can move a page between these places later.

What each kind of page supports ​

Most features work the same everywhere. These are the differences.

FeatureProject pagesWiki pagesTeamspace pages
Public and private pages✓✓Public only
Share a page with specific members—✓—
Collections—✓—
Publish to the web✓✓—
Link pages block—✓—
Link to a work item✓✓—
Nested pages✓✓✓
Page labels✓✓✓
Inline comments✓✓✓
Version history✓✓✓
Page analytics✓✓✓
Export✓✓✓
Page templates✓✓✓

Turn pages on or off ​

Project pages are on by default for every new project. A project admin can turn them off or on again in Project settings › Features › Pages.

The wiki is on by default for every workspace. A workspace admin can turn it off in Workspace settings › Wiki. While the wiki is off, wiki pages can't be opened.

Find your way around this section ​

Troubleshooting ​

Page content not visible ​

Issue Page content is not visible to Members, even when the page is public. The title appears but the content does not, and only the page creator can see it. Sometimes content shows on some pages and not others.

Cause When you run an external reverse proxy, it has to forward the HTTP upgrade headers that WebSocket connections need. The page editor syncs over WebSockets, and the default proxy configuration doesn't handle them.

Solution Add WebSocket support to your external proxy configuration. For NGINX, include these settings:

bash
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

For more on running Plane behind an external reverse proxy, see External reverse proxy.