Navigate between products at the same organization

[olliechillie]

It would be nice if you could navigate to "external systems" that were other products at the same organization.

There would have to be a unique key in both diagrams that corresponded.

[davydkov]

Hey @olliechillie

By saying "other products" do you mean other likec4 workspaces, or other likec4 project in same workspace?

[olliechillie]

Hi @davydkov — thanks for the reply!

To clarify: we have multiple teams, each owning a separate LikeC4 project (their own .c4 files / workspace). We want each team to model their own product in isolation, but reference other teams' products as external systems — even though they're internal to the organisation.

The feature we'd love is: if Team A marks Team B's product as an external system, they could annotate it with a link (e.g. a URL or a shared key) that navigates to Team B's own LikeC4 diagram when clicked. So the diagrams stay independently owned, but are loosely connected via navigable references.

The "unique key" idea I had was something like a stable identifier that both sides agree on — Team B publishes their diagram at a known URL and declares a key like com.example.teamb, and Team A references that same key on their external node to wire up the link.

Is that something that exists already (even partially), or is it outside the current model?