Collaboration

Pages

Write collaborative documents, import existing text, and reuse page content across tasks, offers, reports, and chats.

Pages

Pages are collaborative rich-text documents. Standalone pages live in Pages. The same editor is also reused for task descriptions, offer descriptions, and report text blocks.

Open the feature

What belongs here

  • Standalone documents that should stay visible in the Pages module.
  • Reusable drafts that may later turn into offers.
  • Embedded content owned by other features:

Standalone pages appear in the Pages list and can be shared across the app. Embedded pages stay attached to their owner record.

Create a page

  • Click New page to create a blank page.
  • New pages start with the default title and icon.
  • Use Import on the overview page to create a page from .md, .markdown, or .docx.
  • Use Paste Markdown to create a page directly from copied Markdown text.

Edit a page

  • Click the title to rename it.
  • Click the icon to choose a different emoji.
  • Edit the body with the rich-text editor.
  • The editor supports headings, lists, task lists, quotes, code blocks, tables, links, horizontal rules, highlight, bold, italic, underline, strike-through, and images.
  • Use the floating + insert menu to add common blocks, upload an image, or insert an image by URL.
  • You can also paste or drag image files directly into the page.
  • Selected images can be aligned, resized, downloaded, or removed from the page.
  • Press Cmd/Ctrl+F to search inside the current page and optionally replace matches.
  • If you paste plain-text Markdown into the editor, it is converted into rich content automatically.
  • Edits update the last-edited timestamp automatically.

Collaboration

  • Page content is stored in a collaborative ProseMirror document.
  • Multiple users can work on the same page without making manual copies.
  • Breadcrumbs show the page path when a page already has parent pages.

Organize and find pages

The overview currently has these tabs:

  • All Pages for standalone published root pages
  • Task pages for embedded pages owned by tasks
  • Quote pages for embedded pages owned by offers
  • Starred for favorites
  • Recent for standalone published pages
  • Archived for archived standalone pages

Other list behavior:

  • Each tab is sorted by last edit, falling back to creation time when a page has no edit timestamp.
  • The search field filters the current list by page title.
  • Child pages are shown nested under a parent when that hierarchy already exists.
  • Embedded entries show which record owns them.

Import and export

From a page detail view you can:

  • import a file into the current page
  • import a file and create a new page instead
  • paste Markdown into the current page
  • paste Markdown and create a new page instead
  • export the current page as Markdown
  • export the current page as Word (.docx)

Page actions

The page action menu supports:

  • add or remove favorite
  • duplicate page
  • archive page
  • delete page
  • create an offer from the current page

When a page is already attached to an offer, the action changes to a direct link back to that offer.

Create an offer from a page

You can turn a standalone page into a draft offer from the page action menu.

How it works:

  • Einblick reads the page text.
  • It tries to extract an offer title, positions, and a client organization.
  • The page is then attached as the offer description.

Requirements:

Relations to other features

  • Tasks: task descriptions use the same editor and appear in the Task pages tab. See Task management.
  • Offers: offer descriptions use embedded pages, and standalone pages can be converted into offers. See Offers.
  • Reports: report text blocks are stored as embedded pages, but they are managed from the report workflow. See Reporting and insights.
  • Chats: standalone pages can be mentioned and shared in chat as internal app links. See Chats.

Current limits

The page data model supports more than the current Pages screens expose.

  • Parent and child pages exist in the schema, but the current Pages UI does not expose a dedicated create-subpage or move-page flow.
  • Archived pages can be listed, but the current Pages UI does not expose restore.
  • Cover images, manual sort order, and parent reassignment exist in the schema and API, but the current Pages screens sort by last edit and do not expose manual reordering.
  • Report text pages use the same storage model, but there is no dedicated Report pages tab yet.