Skip to content

Build web part pages

Pro plan Member

Pages are composable web part pages, the same idea as SharePoint pages. You build a page on a visual canvas by dropping in sections and columns, then filling them with content blocks (headings, text, callouts, images, buttons, quick links, embeds) and live-data widgets that pull real project information. Pages live in the Workspace at organization level and in every project’s Docs section, so you can build a team home page, a project overview, a links hub, or an FAQ, and publish it for others to read.

  1. Open Workspace and select the Pages tab (or, inside a project, the Docs section then Pages).

  2. Select New page. Give it a title and pick a starting point: Blank, Team Home, Project Overview (project pages only), Links Hub, or FAQ. The templates drop in a ready-made layout you can edit.

  3. Select Create page. The editor opens with your template rendered on the canvas.

The Pages list shows each page’s status (Published, Draft, or Published with unpublished edits), when it was last updated and by whom, its version count, and its publish date. Use the search box and the All / Published / Drafts filter to find a page quickly, and the row icons to copy a page’s link or open the published page in a new tab.

The left panel lists the parts you can add, grouped into Layout (Section, Columns), Content (Heading, Text, Callout, Divider, Spacer), Media & links (Image, Button, Quick links, Embed, App), Workspace (Document, List), and Widgets (live-data cards such as a stats card, task status chart, milestone timeline, activity feed, and more). Drag a part onto the canvas, then select it to edit its options in the right panel.

Your changes autosave as a draft while you work. The header shows a Saved indicator, and if someone else edits the same page at the same time you are prompted to reload so no work is lost. You can rename the page by selecting its title in the header, and copy its link with Copy link.

Pages use a curated palette of brand-safe colors, so a page always looks consistent and works in both light and dark mode:

  • Section background (select a Section, then its Background option): None, Subtle, Card, or a color tint (Indigo, Blue, Emerald, Amber, Rose, Violet, Slate). Use tints to visually group related content.
  • Page background (the Page panel, Page background option): a subtle page-wide tint (White, Gray, or a color) behind the whole page.
  • Section width: Normal, Wide, or Full, so a section can span the screen.

The colors are a fixed palette rather than free-form values, which keeps every page on-brand and readable against text in either theme.

Three parts bring your own workspace content onto a page:

  • Document embeds a file from a document library. Word, PowerPoint, PDF, Excel, images, markdown, and CSV files render an inline preview (with a Download button); or switch the part to a compact card. Files linked from external tools (Miro, Figma, Google Docs, and similar) show an Open button. On a project page you can pick from the project’s libraries or the organization’s.
  • List embeds a Workspace list as a read-only grid, with proper checkbox, date, link, rating, and tag columns. Very large lists show their first rows with a note to open the full list in the Workspace.
  • App (Playground) embeds one of your published Build apps by its live URL.

If a reader does not have access to the embedded document or list (for example it is restricted to specific people), they see a small “isn’t available” placeholder instead of the content.

A page has a draft (what you are editing) and a published version (what readers see). Select Publish to snapshot the current draft and make it public. Viewers see only the published content; a page you have never published stays hidden from them. Once published, Preview in the editor header opens the live page in a new tab.

Every publish saves a version. Open History in the editor to see the version list and Restore an earlier version into your draft (restoring does not publish, so you can review before making it public).

Published pages always render at full width, and sections keep their own width setting (Normal, Wide, or Full). By default a page opens inside the app, with the navigation sidebar still available. For a page that should take over the whole screen (a kiosk-style landing page, for example), select an empty spot on the canvas to open the Page panel and set Published display to Full screen. The change reaches readers the next time you publish.

By default a page follows your workspace or project access. To restrict it to specific people and teams, open the page’s Manage access menu, turn on restriction, and add the people or teams who should see it. To share a project page with someone outside the project, add them as a project guest first.

Every page has a stable, human-readable URL, for example /workspace/p/team-home for an organization page or /projects/<id>/p/overview for a project page. Renaming the page title does not change the URL, so links stay valid. You can change the URL deliberately with Change URL when you need to.

You can ask AI to draft or restyle a page for you, in two places:

  • In the New page dialog, switch to Design with AI, describe the page you want, and AI creates it ready to edit.
  • In the editor, open Design with AI and describe a change (“add an FAQ section”, “make the hero two columns”). You review the proposed result before applying it, and an applied AI edit can be undone with one click (Revert AI edit).

AI generates the same page building blocks a person would use, so an AI-designed page is exactly as safe and editable as one you built by hand. If a proposed change would remove parts or add links to outside sites, you are asked to confirm before it is applied.

Deleting a page moves it to the Recycle Bin, where it is kept for 30 days. Restore it from the bin to bring it back with its original URL and version history intact.