Resources

Wave Canvases: Shared Docs, Features, and Product Demo

Explore Wave Canvases: shared pages, rich content, AI writing, comments, ownership, and PDF export. Watch the demo and complete feature guide.

Taylor Owen
15 min read

A project usually needs more than a task list. It needs a brief, the research behind it, a record of decisions, and a clear explanation of what happens next. When those pieces live in separate documents and conversations, the team spends time rebuilding context.

Wave Canvases brings that working context into shared documents with pages, nested subpages, rich content, comments, and ownership. You can develop an idea, organize the supporting material, and keep the discussion close to the work inside Wave.

This guide explains the Wave Canvases features, shows a populated example, and walks through a practical way to use the tool for a team launch.

Watch the Wave Canvases showcase

The 48-second showcase uses actual Wave UI components with fictional sample data. It follows a customer portal launch through its overview, research, checklist, writing tools, AI prompt, comments, and PDF export menu. The AI scene shows a prepared prompt, not a generated response. No customer workspace content is shown.

What is Wave Canvases?

Wave Canvases is a workspace for shared, structured working documents. Each canvas has a main page and can contain additional pages and nested subpages. The document can combine text, headings, lists, checklists, tables, images, video embeds, and other supported blocks.

The surrounding workspace adds practical coordination: an owner, teams, status, priority, dates, favorites, comments, and progress updates. That makes a canvas useful for a product brief, research hub, launch plan, operating plan, onboarding guide, or decision record that the team keeps revisiting.

A useful starting point is one canvas per outcome. Give the main page a concise overview, then put the supporting detail into named pages. Someone opening the canvas should be able to answer three questions quickly: what are we trying to achieve, what do we know, and what needs to happen next?

Wave Canvases launch overview with a page tree, pilot targets, and weekly priorities. Fictional demo data.
Give the initiative a clear opening page and organize its supporting material.

A sample workspace with enough context to be useful

The demo workspace, Northstar Studio, contains six canvases: Customer portal launch, Brand and messaging, Customer research hub, Q4 operating plan, Partner onboarding, and Team working agreements. They have different owners, priorities, statuses, target dates, and health signals so the library behaves like a working team space.

The featured launch canvas contains nine pages in total:

  • Customer portal launch: the outcome, pilot cohort, launch date, and immediate priorities.
  • Launch brief: the problem, scope, success criteria, and boundaries of the first release.
  • Customer research: a synthesis of six illustrative interviews, with Interview notes nested below it.
  • Delivery plan: four workstreams, named owners, a review cadence, and a nested Launch checklist.
  • Decision log: two decisions with their rationale and one question still to resolve.
  • Team handoff: preparation, a walkthrough, follow-up, and escalation ownership.
  • Reference library: supporting references, writing principles, and an example welcome message.

Across the sample there are 140 content blocks, six fictional teammates, four document comments, and a progress update. The launch checklist has ten concrete checks. The names, research findings, targets, and dates are illustrative, not reported customer outcomes.

Find and organize your canvases

1. Create a canvas with its working context

Start with a title and team, then set the owner, status, priority, and dates as needed. Creation requires a title and at least one team. Defining these details early gives the document a place in the team's work and makes it easier to find again.

2. Review the library as a table

The canvas library presents title, health, priority, owner, target date, and status together. You can scan several documents without opening each one. In the sample, this makes it easy to distinguish the active launch brief from a planned operating document or completed team agreement.

3. Search by title or canvas ID

Search helps you find a canvas by its title or identifier. Use a descriptive title for everyday discovery and the canvas ID when referring to a specific document. A name such as “Customer portal launch” gives teammates more context than a generic “New document.”

4. Filter the library

Filter canvases by status, priority, assignee, team, and target date. These controls help narrow the view to the documents relevant to a review—for example, work owned by your team that is currently in progress. Filters are particularly useful as the library grows beyond a handful of documents.

5. Keep frequently used canvases in Favorites

Favorite a canvas to make it easier to return to. Favorites appear as cards above the library, and the display controls let you show or hide that area. The showcase favorites the launch canvas and the messaging canvas because the team needs both during the same working week.

Structure a document around the work

6. Give every canvas a main page

The main page is the entry point for the document. Use it for the outcome, a brief summary, and the most useful current information. In the demo, the main page contains the pilot cohort, target launch date, working owner, and this week's priorities, so readers can orient themselves before exploring the detail.

7. Add pages for distinct topics

Add separate pages for research, planning, decisions, references, or handoff instructions. Each page has its own title and content. This keeps a canvas readable as the work develops and gives teammates a clear destination for material that would otherwise make the opening page too long.

8. Nest subpages under their parent topic

Pages can contain subpages, and the page navigation supports expanding and collapsing those branches. In the launch example, Interview notes belongs under Customer research, while Launch checklist belongs under Delivery plan. The hierarchy explains the relationship between the material without requiring a separate index.

9. Rename pages as the work becomes clearer

Edit the canvas or page title directly in the workspace. Names can evolve from an early idea into a more specific outcome. Keep titles short enough to scan in the page tree, and reserve the longer explanation for the page itself.

10. Add emoji and page covers

Use an emoji and cover to give a canvas or page a recognizable identity. Cover options support a color, gradient, or image; image covers can be repositioned, and covers can be removed. A consistent visual treatment helps the team recognize related documents while leaving the content as the main focus.

Write with the blocks the page needs

Wave Canvases research page with a table connecting themes, signals, and design implications. Fictional demo data.
Keep the evidence and its interpretation together.

11. Build a readable heading hierarchy

Use paragraphs and three heading levels to organize longer material. Headings should describe the question or topic below them: “Success criteria,” “Launch workstreams,” or “Open decision.” Readers can then find the relevant section without reading the whole document again.

12. Format selected text

The editor provides text formatting controls for emphasis and links. Use emphasis to make key decisions and labels easier to scan, and link to supporting material where it helps the reader take the next step. A brief works best when the most important sentence remains easy to find.

13. Use ordered and unordered lists

Choose bullets for a set of points and numbered lists for steps that should happen in sequence. The handoff example uses a numbered walkthrough: show the overview, create a useful request, and agree on the next action. The research page uses bullets for follow-up responsibilities.

14. Track simple checks inside the page

Checklists let you mark individual lines complete while keeping them beside the explanation. The sample launch checklist covers product readiness, customer readiness, and after-launch follow-up. Use these for document-level checks; when work needs detailed scheduling or task coordination, connect the context to the team's execution workflow.

Wave Canvases launch checklist with product, customer, and follow-up checks. Fictional demo data.
Keep readiness checks beside the plan they support.

15. Compare information in tables

Insert tables with editable cells to bring related information into a consistent structure. The demo uses them for research themes, pilot targets, and workstream ownership. A small table can explain “theme, evidence, implication” more clearly than several paragraphs with repeated labels.

16. Separate quotations and sections

Quote blocks distinguish a quotation or excerpt from the surrounding explanation, while dividers separate sections visually. In research notes, preserve the difference between what someone said and the team's interpretation. In a handoff guide, use section breaks where they help a reader follow the workflow.

17. Add images and video embeds

The image command offers library, upload, and Unsplash choices. The video command supports YouTube and Loom embeds. These let a page include a useful visual reference or walkthrough alongside its written explanation, rather than requiring the reader to reconstruct the context from a separate message.

18. Include code blocks

Code blocks provide a dedicated place for code with syntax highlighting. Use them for a technical example, configuration note, or handoff detail that benefits from preserving its structure. Keep the surrounding explanation clear about what the example is intended to do.

19. Highlight information with display cards and emoji

Display cards offer a colored block for information that should stand out, and emoji can add compact visual cues. Use these selectively for a decision, review note, or key instruction. The rest of the page should still be understandable without relying on color alone.

20. Reference people and work with mentions

The editor includes mention controls so references can be more specific than plain text. Use the available suggestions to identify people or relevant work in context. This is useful when a sentence needs to make clear who is involved or which item the document is discussing.

21. Insert blocks with slash commands

Type a slash in the editor to open the block menu. It brings headings, lists, checklists, quotes, tables, media, code, dividers, display cards, AI, dictation, and emoji into the writing flow. You can choose the structure as you write instead of deciding the entire layout beforehand.

Wave Canvases slash command menu for headings, lists, checklists, and other content blocks.
Choose the structure while you write.

Develop the draft with AI and dictation

22. Ask AI a question about the writing task

The inline AI composer accepts a freeform prompt. Give it a specific instruction and enough context to make the request useful. The showcase prepares: “Summarize these launch decisions and list the open questions for our next review.” The prompt is grounded in the visible decision log.

23. Apply AI actions to selected writing

Selection actions include Improve Writing, Fix Spelling and Grammar, Simplify, Make Shorter, Make Cleaner, Summarize, and Turn into Action Items. Selecting the relevant passage helps focus the request. For example, a long research synthesis may need a shorter summary, while rough meeting notes may need clearer action items.

24. Review proposed AI changes

The AI workflow includes controls to review and accept or reject proposed changes. Check the wording and factual meaning before accepting a revision, especially when it changes an owner, date, customer statement, or decision. AI availability and execution depend on the workspace's enabled services and access.

25. Capture a spoken draft with dictation

The Dictate command opens voice capture controls, including recording state and transcript handling. It gives you another way to get an initial thought into the document before editing it into a clearer form. Dictation requires microphone access and the connected service; recording is not exercised in this showcase.

Wave Canvases inline AI composer with a prepared prompt about launch decisions. Fictional demo data.
Give AI a focused request, then review the proposed changes.

Keep ownership, discussion, and progress close

26. Save edits as you work

Canvas editing includes automatic saving and save-state handling. The workspace also handles pending changes when navigating between its pages and before preparing an export. Pay attention to a save error if one appears and use the available retry path before relying on the latest edit elsewhere.

27. Collaborate in the shared editor

Canvases uses Wave's shared editing infrastructure so teammates can work in a common document. This supports the idea of a current working brief that the team develops together. The illustrative video uses one local session; it does not present simulated collaborators as a live multi-user demonstration.

28. Discuss the canvas in Comments

Open the comments drawer to keep feedback with the canvas. The comment workflow supports attachments, replies, and reactions. The sample discussion stays specific: simplify the first screen, finish permissions QA, confirm the pilot cohort, and defer billing and reporting to a later review.

Wave Canvases comments panel with feedback from four fictional teammates.
Keep the review conversation attached to the canvas.

29. Add health updates with an explanation

Use the updates drawer to record a progress note with an On Track, At Risk, or Off Track status. The explanation matters as much as the signal. “On Track” becomes more useful when the update also states what is ready and which launch gate still needs attention.

30. Set status and priority

Canvas properties support Backlog, Planned, In Progress, Completed, and Cancelled states, along with No Priority, Urgent, High, Medium, and Low priority levels. Status describes where the work stands; priority helps signal its relative urgency. Both are visible in the library as well as the document details.

31. Assign an owner and teams

The details drawer keeps the working owner and team associations accessible. A named owner gives the team a clear person to follow up with when the canvas needs a decision or refresh. Team associations provide useful organizational context and support filtering the library.

32. Set dates and review activity

Add start and target dates to connect the canvas to a working schedule. The details drawer also includes an activity area for available events. Use the target date for the document's intended outcome or review milestone, then make the next action explicit in the page content.

Bring the document into the next conversation

33. Copy the canvas URL or ID

The More actions menu provides Copy URL and Copy ID. Use the URL when you want a teammate to open the canvas and the ID when you need a concise reference. Access to the linked document still follows the workspace context; copying its URL is not a public-publishing workflow.

34. Export the canvas as a PDF

Export PDF prepares the main page and its pages in their hierarchy, including nested subpages. This makes it useful for a review packet or a handoff snapshot that needs to travel beyond the live editing view. Review the document before exporting so the snapshot reflects the current decisions and supporting detail.

35. Bring a canvas into a meeting agenda

The meeting agenda integration can show a selected canvas in a read-only preview with page navigation. The team can review the brief, research, or checklist within the meeting flow. Use the meeting to resolve an open question, then capture the agreed outcome in the working document.

36. Remove documents and pages deliberately

The library supports selecting canvases for deletion, and canvas and page actions include deletion controls. Deleting a page can also remove its descendants. Treat these as permanent cleanup actions and check the scope before confirming; the current Canvases workflow does not present an archive or a restore bin.

A practical workflow: from launch idea to handoff

Start by naming the outcome and assigning its owner. Create the main page with a short explanation of the problem, the intended result, and the next review date. Add only the pages you need initially; a brief, research page, and decision log are often enough to begin.

As evidence arrives, add it to the research page and keep detailed observations in subpages. Separate the observation from the interpretation. In the sample, the research table connects a theme to a signal and then to a design implication, so reviewers can see how the team reached its recommendation.

Turn the agreed direction into a delivery plan. Give each workstream an owner and a next milestone. Keep detailed execution in Wave Projects, while the canvas explains the purpose, boundaries, and decisions behind that work. Use the launch checklist for the checks that the team needs to confirm together.

During review, use comments for focused feedback and updates for the current progress narrative. Write decisions as an outcome plus a reason, with an owner and a point at which to revisit them. A decision log is most useful when it explains why the team chose a direction, not just what changed.

Finally, prepare the handoff page around the next person's workflow. Include preparation, a short walkthrough, expected follow-up, and escalation ownership. Review the relevant canvas pages in Wave Meetings, then export a PDF when a static review copy is needed.

Where Canvases fits alongside other Wave tools

Use Canvases for the written working context around an initiative. Use Wave Whiteboards when the thinking benefits from a spatial board, and Wave Sketches when the output is a design. Use Projects for coordinated execution and Wave Knowledge for the knowledge workflows covered in that tool.

A useful pattern is to keep one clear home for each type of work. The canvas explains the launch, the project tracks delivery, and the design file develops the interface. Reference the relevant material instead of copying it into several places that can drift apart.

Keep the canvas useful over time

Give each page a clear purpose, keep the opening summary current, and review stale decisions when the underlying facts change. Avoid creating a deep page tree before there is enough content to justify it. A short, current brief is easier to use than a large document whose owner and next step are unclear.

This guide covers the Canvases UI and implementation inspected for the showcase. It does not claim offline editing, a public website publishing flow, a version-history browser, or an archive. AI, dictation, uploads, and live collaboration depend on their connected services and workspace access.

Start with one real outcome: a launch, a research question, or a team handoff. Give it a shared home, organize the supporting pages, and keep the decisions close. Get started with Wave.

Frequently asked questions about Wave Canvases

What can I use Wave Canvases for?

Use it for shared working documents such as project briefs, research hubs, launch plans, operating plans, decision logs, and handoff guides. Pages and subpages let you keep related material in one document structure.

Can one canvas have multiple pages?

Yes. A canvas has a main page and can contain additional pages and nested subpages. The page navigation lets you move through the hierarchy and expand or collapse branches.

Can I add tables, checklists, images, and videos?

Yes. The editor includes tables, checklists, image insertion, and YouTube or Loom video embeds, alongside headings, lists, quotes, code blocks, dividers, display cards, and other writing controls.

Does Wave Canvases include AI writing tools?

The editor includes a freeform AI composer and selection actions for improving, simplifying, shortening, summarizing, and turning text into action items. Proposed changes can be reviewed before acceptance. Execution depends on the workspace's AI services and access.

How do teammates review a canvas?

Teammates can use the shared editing workflow, discuss the canvas through comments, and record progress through health updates. A selected canvas can also be reviewed through the meeting agenda's page preview.

Can I export a canvas with its subpages?

Yes. Export PDF gathers the main page and the document's pages in their hierarchy, including nested subpages. The export is a snapshot of the document prepared for sharing or review.

What is the difference between Canvases and Projects?

Canvases organizes the written context: the brief, evidence, decisions, and handoff. Projects coordinates execution. They work well together when the canvas explains the outcome and the project manages the work needed to deliver it.

Is the data in the showcase from a real customer?

No. Northstar Studio, its teammates, customer research, launch targets, comments, and dates are fictional sample data. The video uses actual Wave UI components to demonstrate a realistic working example without exposing customer content.

Explore