Linking Pages & Embedding Content

Type @ anywhere in a doc — in a paragraph, a table cell, a callout, anywhere — and a picker appears. Start typing the name of any page in the doc. Select it and Coda inserts a live inline link to that page. Click the link to navigate straight there, no mouse hunt through the sidebar required.

This is the primary way to cross-reference pages in long-form content. An onboarding guide might reference @Team Directory, @Company Handbook, and @Project Tracker inline — readers stay in context and click only when they need the detail.

Any page in Coda can have child pages — subpages — nested under it in the sidebar. This lets you build a tree of content that mirrors how the information is actually organised, not just a flat list of pages in whatever order they were created.

To create a subpage, hover over a page name in the sidebar and click the + that appears on its right. Or, drag an existing page and drop it onto another to nest it. You can drag pages up and down to reorder them within a level, or drag them left to unnest them back to the parent level.

Subpages appear indented under their parent in the sidebar. The parent page itself can have its own content — it doesn't have to be a blank container. Many teams use the parent page as a section overview and put detail into the subpages.

One of Coda's most powerful features is the ability to embed a view of any table — with its full filter, sort, and group configuration — on any page in the doc. The embedded view shows live data. Edit a cell in the embedded view and the underlying table updates. Add a row and it appears everywhere that table is referenced.

To embed a view, type /view on any page. The slash command picker opens. Search for the table you want, select it, then optionally choose which saved view to use. The view renders inline on the page, and it stays up to date automatically.

A dashboard page is a regular Coda page that contains nothing but embedded views — pulling from multiple tables, each showing a different slice of data. There's no special "dashboard mode" in Coda; you just use /view repeatedly to embed as many views as you want, then arrange them with headings and layout blocks.

The /embed slash command lets you paste a URL and render external content directly inside a Coda page. The embed is live — changes to the source (a Figma file update, a new YouTube video in a playlist, a Google Maps location) are reflected next time the page loads.

When you embed a table view on a page using /view, you can configure that embedded view to show only a curated set of columns — a "summary" slice of the full table. This is exactly what column hiding is for. The full table might have 12 columns; your summary view on the brief page shows only 4.

The right pattern for shared pages or client-facing summaries: embed the table, open the view's column settings, hide everything except the columns you want stakeholders to see. Their edit permissions still apply — if they have edit access, they can update values in the visible columns. They just won't be distracted by or accidentally edit the internal-only columns.