Skip to main content
Documents in Product Graph provide flexible, rich-text pages for capturing information that doesn’t fit neatly into structured artifacts. Use documents for research, meeting notes, reference materials, and more.

​
Documents vs Artifacts

Flexible, free-form content for:
  • Research and discovery notes
  • Meeting notes and summaries
  • Reference materials and guides
  • Draft ideas and brainstorming
  • Supporting documentation
Start with a document when exploring ideas, then promote key content to structured artifacts when it’s ready.

​
Creating Documents

1

Create a new document

Click the “New” button and select “Document”. Choose a location in your workspace or project.
2

Add your content

Write freely using the rich text editor. Add formatting, images, tables, and embedded content as needed.
3

Organize and tag

Add tags and organize your document within the appropriate folder or project for easy discovery.

​
Document Features

Rich Formatting

Full rich text editing with headings, lists, tables, images, and more.

Embeds

Embed content from other tools like Figma, Loom, and Miro directly in your documents.

Templates

Start from templates for common document types like meeting notes or research summaries.

Version History

Track changes over time and restore previous versions when needed.

​
Document Organization

​
Folders

Organize documents into folders to create a clear hierarchy:
  • Group by project, team, or topic
  • Nest folders for deeper organization
  • Drag and drop to reorganize

​
Tags

Apply tags for cross-cutting categorization:
  • Find documents across folders
  • Create custom tag taxonomies
  • Filter views by tag
Full-text search across all documents:
  • Search document content
  • Filter by date, author, or project
  • Find related documents quickly

​
Import and Export

Import

Bring in existing documentation from: - Markdown files - Notion exports - Confluence pages - Google Docs

Export

Export your documents in multiple formats: - Markdown - PDF - HTML - Plain text

​
Best Practices

Keep documents focused — Each document should have a clear purpose. If a document covers too many topics, consider splitting it into multiple documents.
Use descriptive titles — Write titles that describe the content clearly. Avoid generic names like “Notes” or “Draft” without context.
Link related content — Create links between documents and artifacts to build a connected knowledge base that’s easy to navigate.
Promote to artifacts — When a document contains mature requirements or specifications, promote that content to a structured artifact for better organization and tooling integration.