Hand a relative one branch to fill in, watch their progress, and merge their work back into your tree — with a safety net at every step. Every screen below is the real app.
You assign a branch, watch progress, and decide what gets merged in. Nothing changes in your tree until you approve it.
They get their own editable copy of the branch you handed over. They can't touch your master tree — they work in the copy.
On any tree card, the duplicate icon makes an independent copy. Handy before a big change, and it's the same snapshot Salasilah takes for you automatically before a merge.
Click the Share icon on your tree, then flip the toggle from Simple to Advanced. Assigning a branch is a deliberate hand-off, so it lives under Advanced.
Tick Assign to a contributor and enter their email. Under Start from, type a name to hand over just that person's branch — here, Yusof's. Leave it blank to share the whole tree.
Click Create link and send the link (and passcode, if you set one) to your relative however you like — WhatsApp, email, anywhere.
Back on your dashboard, a new Forks of my trees section appears with the invite marked Not accepted yet — so you know it's out there before anyone opens it.
The link opens a welcome that names you as the sender and explains they'll be filling in a copy you can merge back. They click Start collaborating.
A banner reminds them this is a working copy you can see and merge. Everything they do here happens in their copy — your master tree is untouched.
They use + Add Person to fill in their side of the family — here, adding Aisyah as a daughter of Yusof.
Once accepted, the invite becomes a live row showing the person count and when it was last touched, with View, Merge back →, and (after a first merge) Undo last merge.
View opens their copy read-only, so you can check their work without changing anything.
Click Merge back →. Salasilah shows exactly what would change — people to add, fields to update, and any conflicts — before anything is written. Nothing commits yet.
If you and your relative changed the same detail differently, it's flagged as a conflict and you pick which to keep. The safe choice — Keep mine — is selected by default. Use Keep all mine / Take all theirs to decide in bulk.
Click Apply merge. Salasilah snapshots your tree first (so you can undo), then writes the approved changes into your master tree.
Merging is never silent: your relative sees a notice on their dashboard that you merged their contributions, which they can dismiss.
Open your merged tree and you'll find an Undo merge button in the toolbar with a count badge. It's only there while there's a merge you could still roll back.
Clicking it lists your recent merges. Undo restores exactly what that merge changed (later edits are kept); Dismiss just clears the reminder without undoing.
Built a small tree separately (a mother's side, or one imported from a file)? In Advanced mode the dashboard shows a Merge button next to Import for folding it into your main tree.
Choose which small tree to merge, and which tree to merge it into. Only the target changes; the source is copied, not moved, and stays on your dashboard.
Because the two trees were built separately, Salasilah can't know who's the same person — so you confirm every match. For each person you pick Same as … or Add as a new person. Even identical names are never linked automatically.
When a branch is done, Revoke on its row ends the collaboration: it drops off your monitor panel and the share link stops working.