Find your fit
Who it is for
It suits teams that need a flexible home for recurring knowledge: meeting decisions, product plans, operating notes and the live records tied to them. A small team can begin with a shared hub; a larger one can divide work into workspaces, docs, pages and tables.
The fit is strongest when someone can maintain the structure. Doc Makers build and manage documents, while Editors contribute to existing material. A buyer should identify who will own the hub and who only needs to read or edit before choosing paid roles.
The work it supports
Core capabilities
Start a team hub with pages and subpages. Each page can hold explanatory text alongside a table, image, button or embed, so a policy or project brief can sit beside the records people use to act on it. A wiki can keep notes, decisions and product context together.
When information becomes structured, add a table for tasks, requests or other records. Filter, group and relate data, then create separate views for different audiences. Updates flow through the shared underlying table instead of creating competing copies.
Views can present the same data as a board, calendar, card layout, chart or timeline. That lets one group review a schedule while another works from a task board. Check the intended view and permissions with a real sample before moving a large process into a doc.
Comments, owner assignments and teammate mentions keep discussion close to the page or table row. The Share control shows the doc owner and access levels, which makes a small knowledge pilot easier to govern before inviting a whole organization.
Buttons and automations can move repetitive work along from a doc or table, including scheduled rules and responses to document changes. A useful first test is an internal notification or handoff, then review the rule before it touches an external system.
Packs extend docs with data or actions from connected applications. The vendor names Slack, Jira, Salesforce, Google Calendar and GitHub as examples, but each Pack can have different sync and action behavior. Confirm connector rights and security settings for the exact tools a team needs.
Docs AI can help draft a page, build a table or view, organize information and answer questions using document context. Its output remains editable for team review. Start with a small draft and inspect the generated structure before sharing it broadly.
Understand the offer
Pricing and getting started
The current product page offers a free start. Superhuman Docs uses a maker-based billing model: Doc Makers are paid and Editors are free. Count people who must create or manage docs, pages and folders rather than treating every reader or contributor as the same seat type.
Before choosing a plan, compare the current Doc Maker seat price with the number of people who need to create and manage pages. Check document and version-history limits, Docs AI rights, and whether the offer bundles other Superhuman products before budgeting the workspace.
Organization-wide administration and SSO are presented in the current Enterprise guide as higher-tier controls. A buyer with compliance or access needs should verify these rights and the intended admin scope against the selected offer.
Look a little closer
Before you choose
For a practical pilot, build one small team hub: create a page for guidance, a table for active requests, two views for different readers and a comment on a record. Confirm how ownership, editing and sharing work before importing important files.
Coda was renamed Superhuman Docs. Teams that already link to Coda content or connect Packs should test their actual links, embedded content and integrations during a small migration pilot, especially where another system restricts allowed domains.
Budget for the people who maintain the knowledge structure, and confirm role changes before rollout. Editors can work in existing docs; Doc Makers create and manage docs and pages. Check current pricing and AI entitlements rather than assuming every contributor requires a paid maker license or every beta feature is included.
Before relying on a shared workflow, test a small document with the intended owner, an editor and a viewer. Confirm each person's access in Share, then try one relevant Pack with harmless sample data so the team understands its permissions and what it can update.
8 distinct sources behind this profile. Research observed Oct 26, 2026. Features and offers can change.
View sources and research →
