Preview environment — data may be reset without notice. Do not use for real work.

Multi-project

Cross-project references

A cross-project reference pins a phase from another project into your Gantt as read-only rows, so a shared dependency shows up where you actually plan — without copying it or giving everyone access to the other project.

Project A · sourceeditable hereread-only · one-wayProject B · host↗ ref · read-only
The source phase stays editable in its own project; the host sees a dashed, read-only mirror that re-syncs on its own.

What gets referenced

You reference a top-level phase from the source project. Its whole subtree (child tasks, milestones) comes along and renders inline in your chart and Kanban, visually distinct — dashed, muted, marked with a ↗ source tag.

It stays in sync: edits to the referenced tasks — renames, dates, status, progress, deletions — update live, so you're looking at the real phase, not a stale copy. (Brand-new or removed tasks inside the phase appear after the page refreshes.)

Adding & removing a reference

In the host project: Actions → “Reference a phase from another project…”, pick the project, then the phase. To remove it, use the trash icon on the linked phase row. The source project's lead can also revoke a reference from that phase's editor.

The boundaries

  • Read-only & one-way: edits happen only in the source project. The link never writes back, and the host can't change the borrowed rows.
  • Same workspace only: you can reference projects within one workspace. A project in another workspace can't be referenced (even if you're a guest there).
  • Team plan and up: cross-project references are unavailable on Basic. The picker shows an upgrade note instead.
  • Top-level phases only: you reference a whole phase, not an individual task buried inside one.

Privacy

Referencing a private project's phase into a project more people can see surfaces a warning first — the borrowed rows expose that phase's names and dates to the host's audience. The source project's lead always sees a ↗N badge showing who references their phase, and can revoke it at any time.

“I can't edit a referenced row.”

That's intended — a reference is a read-only window into the source. Drag, rename, status, delete and bulk actions all no-op on linked rows so a host can never silently change another team's plan.

Need a change? Open the source project (the ↗ tag links to it) and edit it there; the reference updates on its own.

Recap

  • Is — a live, read-only view of a phase from another project.
  • Add — Actions → Reference a phase…; remove via the row's trash icon.
  • Limits — same workspace, Team plan+, top-level phases, one-way.
  • Edit — only in the source; the reference re-syncs automatically.