Skip to main content

​
What are Pages?

Pages is Connie’s hierarchical wiki — the place every doc, runbook, meeting note, and SOP lives. It replaces what used to be called the Knowledge Base and was rebuilt from the ground up as a fully Notion-style editor. Every page is a rich document and a container — any page can have child pages, so you can nest your knowledge as deep as makes sense. Pages link to projects, to your CRM, and to each other via inline mentions.
Some API responses and field names still use knowledgeBase / knowledge_base_id for backwards compatibility while the rename completes server-side. The product surface is consistently “Pages”.

​
The editor

Pages are built on TipTap (a ProseMirror-based editor). Inline formatting and block types:

Rich text

Headings, bold/italic/underline, ordered & bullet lists, task lists, blockquotes, inline code.

Blocks

Code blocks (with language selector), tables, callouts, details/expandable sections, two-column layouts.

Media

Resizable images, YouTube embeds, audio/video, file attachments, generic embeds. Markdown paste and drag-drop supported.

Slash menu

Type / anywhere for a quick-insert menu of every block type, plus AI actions.
The bubble toolbar handles inline formatting and block transformations — select text or click a block to surface the relevant options.

​
Hierarchy & navigation

Pages live in a tree:
  • Any page can be a parent
  • Children inherit sharing permissions from their parent (read-only — explicit child grants still take precedence)
  • The page sidebar renders the tree with drag-to-reorder and drag-to-reparent
  • Pages can be scoped to a project for canvas-style grouping
The old “folder vs document” distinction is going away — is_folder is being retired in favor of plain parent/child relationships. A page with children acts as a folder; a page without is a leaf.

​
Inline comments

Pages support threaded inline comments anchored to a text range. The flow:
  1. Highlight any span of text
  2. Click the comment button in the bubble toolbar
  3. Write the comment — optionally @mention teammates or attach files
  4. Replies thread underneath; reactions and resolve state live alongside
Comments stay anchored even as the surrounding document is edited. Resolving collapses a thread; reopening brings it back. Mentioning a workspace member fires a mention notification with a deep-link straight back to the comment.

​
Mentions & page references

Two distinct features, both inline: Page reference chips are live — renaming a page updates every chip pointing at it (with ~500ms cache latency). Older plain-text links get auto-promoted to chips when the page is opened.

​
AI in Pages

The AI copilot is wired into the editor.
  • AI write / continue / summarize — invoke from the slash menu or bubble toolbar. Output streams into the document.
  • Select-and-prompt — highlight any text and ask the AI to rewrite, expand, condense, translate, or transform it.
  • Table shape control — when you ask the AI to insert a table, you can specify exact dimensions (e.g. “a 3×5 comparison table”) and it honors them precisely.
  • Brain context — page content is indexed so the AI copilot can pull it as context anywhere in the product. Vector search is scaffolded; text search is live today.

​
Sharing

Three access modes on every page: Children inherit members from their parents up to 5 levels deep — the share modal shows inherited members in a separate “From parent” section. Only the page owner can change sharing settings.

​
Sources

Pages can be backed by external sources — file uploads, URLs, audio/video, or third-party apps. Today’s source types:
  • Documents — PDF, TXT, Markdown, DOCX
  • Audio — MP3, WAV, M4A and similar
  • Apps — placeholder for upcoming Notion / Zendesk / YouTube / LinkedIn / X / Intercom integrations
Live integrations are coming. The Apps tab is a stub today — adding a connected app source returns “currently empty until a new integration ships”. File and audio uploads work today.
Attachments upload directly to storage via signed URLs and import-from-URL is available for grabbing remote content into a page.

​
Common workflows

​
Build a team wiki

  1. Create a top-level page Team Wiki with access set to Everyone and role view
  2. Add child pages per topic — onboarding, runbooks, FAQs
  3. Grant a small group edit access via the share modal so only owners can write

​
Collaborate on a doc

  1. Open the doc and use Invited sharing to add your collaborators with edit role
  2. Comment inline on phrases that need discussion — every reply notifies the original commenter
  3. Resolve threads as you address them

​
Reference your CRM in a page

Use [[ to drop chip references to other pages — e.g. an account page or a deal review note — directly inline. Renames stay synced.

​
API reference

Pages

Create, list, and manage pages and their tree structure.

Inline comments

Threaded highlight-anchored comments with reactions and resolve.

Sharing

Read and update per-page access, invited users, and public links.

Search

Full-text search across page content.