Linking Documents Together

MDflow lets you link one document to another without copying URLs around.

Creating a link

Type @ anywhere in a document. An autocomplete list appears, searching your whole workspace by title. Pick a document and MDflow inserts a live internal link to it.

That is the whole feature. There is nothing to configure.

What actually gets stored

The link is stored as ordinary markdown pointing at the document's stable address:

[The Document Title](/doc/8f3a1c2e-...)

Two things follow from this:

• The link survives renames and moves. It points at the document's identity, not its title or its folder. Rename the target or move it to another folder and the link still works.
• It is still just markdown. If you export or download the document, the link is a normal markdown link. It will not resolve outside MDflow, but it does not corrupt the file or require special handling.

What readers of a shared document see

This is the part worth understanding, because MDflow does something careful here.

When someone opens a document you have shared, your internal links are rewritten to a URL that specific reader can actually open:

• If the linked document is part of the same shared collection, the link points to it inside that collection — the reader stays in the same reading experience.
• If the linked document is publicly shared in its own right, the link points to its public share link. See 01 Public Share Links.
• If the linked document is privately shared with that reader, the link resolves for them, because they have access.
• If the reader has no access to the target, the link is not rendered as a link. The text remains, but there is no broken URL and no clickable path into your private workspace.

The important consequence: an internal link never leaks a private document. Sharing one document does not silently expose everything it links to. A reader only ever gets a working link to something they were already allowed to see.

Practical uses

• Build a hub document that links out to the rest of a folder, then share the whole set as a collection. Inside the collection, every link resolves to its sibling. See 05 Collections.
• Use it as a table of contents for a Knowledgebase collection share, where the hub is the homepage. See 03 Sharing Collections.
• Cross-reference freely while writing, knowing the links stay correct as you reorganize.