**From lightest to deepest.**
- [Attach](/nodes/29525) links your graph under a node. Nothing is copied; readers of that node can open your graph; it stays yours. Instant, and undone with Detach.
- [Join](/nodes/29556) adds your graph's nodes to another graph as new nodes. Into the public graph that is a proposal, decided by the owners of the node it goes under.
- [Merge](/nodes/29511) folds your work into nodes that already exist: edits to public nodes, plus new nodes where something is missing. The owners of each node it changes decide.

**Who decides.** For the public graph, always the owners of the nodes a change touches, each for their own node: see [Owners decide](/nodes/29512). For your own private graphs, you do.

**One dialog.** **Connect…** in a node's menu offers all three, says what each one does (who can read the result, who owns it, whether it is reviewed, how to undo it), and leads to the right step.

**In the terms of Knowen's contribution spec (v0.3):** our Attach is its ATTACH; Join into the public graph is its ADD plus ATTACH; Merge is its MERGE and, when two nodes turn out to be the same and are unified, its JOIN.

**Why three.** Most graphs only need to be found (attach); some belong in the public graph as they are (join); the best improve what is there (merge). This is how a graph grows from many sources: see [Growing a graph from many sources](/nodes/29550).

---

**Read on**

- [Attach](/nodes/29525): Link your private graph under a node, public or private: readers of that node can open it, nothing is copied, and it stays yours.
- [Join](/nodes/29556): Add your graph's nodes to another graph as new nodes: into the public graph as a proposal, or into another graph of yours directly.
- [Merge: fork, edit, merge back](/nodes/29511): Improve public nodes you don't own: fork them, edit your copy, and propose merging it back; the owners of each node decide.
- [Growing a graph from many sources](/nodes/29550): Each source becomes its own small graph, then joins the combined graph: duplicates merged, new pieces placed under what needs them, structure refactored as it grows.
- [Owners decide](/nodes/29512): Each public node a proposal changes needs one answer from its owners; the approved part is merged, and nothing waits forever.