A renamed workspace still needs a link audit

The event

On July 8, 2026, Coda became Superhuman Docs. The company's help page says existing documents, workflows, tables, Packs, automations, and formulas continued to work, and old coda.io links redirected to the new domain. That is not the same as saying every downstream handoff required no attention. The same help page notes that some embeds and integrations may need updated domain allowances or reconnection.

The supplied research log catches a date trap here: the company adopted the Superhuman name in October 2025, but the Coda product rename came later. Merging those events would make a workflow history wrong even if the broad product story sounded plausible. Keep the organization change and the product change on separate lines.

A proposed post-rename check

Inventory the links that matter: published docs, bookmarks in onboarding material, embeds on internal pages, chat unfurls, and any connector configured for a specific domain. Open a small sample from each category as a user with ordinary permissions. A redirect working in the browser does not prove that an embed's allowlist or a bot's link preview works.

For automations, run a controlled event and inspect both the action and its destination. Save the pre-change and post-change behavior in a short log. If a connector prompts for reconnection, have the workspace owner review the requested access before approving it. This is a proposed checklist based on the documented change, not a claim that any particular customer's integration failed.

1. Keep company and product rename dates separate.
2. Test links, embeds, unfurls, and connectors from ordinary user accounts.
3. Record which flows required reconnection or documentation changes.

The friction to budget for

A rename creates many small points of confusion even when data stays intact. Search results may show both names, old screenshots may teach the wrong button labels, and support instructions may refer to the earlier domain. Update the few documents people actually use instead of attempting a perfect rewrite of every archived page.

The practical result is continuity of work, not a tidy brand vocabulary. If a new teammate can find the document, open the embedded view, and follow the handoff, the migration has done its job. If not, the missing link matters more than the vendor's assurance that content was preserved.

Keep a record of the tested paths and dates. That record is more useful than a general assurance that everything migrated, because it tells the next person which integration was actually inspected and which one still rests on the vendor's description.