Create a Plane Project Page with Intentional Access
Open a Plane project’s Pages section and select Add page to create project documentation. Choose the correct access context before adding sensitive material.
Pages must be enabled and you need creation access. The Private tab creates a private page; other project-page contexts create a public project page. Self-hosted users should confirm the installed editor matches current documentation.
Example: create a Checkout rollout brief with the user problem, success criteria, excluded scope and rollout decision owner, so engineers can understand why the linked work exists.
Step-by-step guide
Open the correct project context
Select Pages inside the relevant project. Choose the Private tab first if the draft is personal; otherwise use the shared project context intentionally.
Create and identify the page
Click Add page and replace the untitled name with Checkout rollout brief. Alternatively, press N then D in the project to set title and access in the creation dialog.
Write the decision context
Add headings for problem, intended outcome, scope, risks and owner. Paste existing Markdown if helpful; Plane converts its headings, lists and tables into formatted content.
Check the page before handoff
Reopen the page from the project’s Pages section and review its access setting and source links. Ask an intended collaborator to confirm the shared content is readable.
Common mistakes
Assuming public means published on the web
Project sharing and internet publishing are separate decisions. Review the page’s access controls before distributing its URL.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.