Salasilah · Step-by-step

Collaborating on a family tree

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.

✎ Draft. Screenshots are auto-generated from the live app (re-runnable). English only for now.
You — the owner

Keep the master tree

You assign a branch, watch progress, and decide what gets merged in. Nothing changes in your tree until you approve it.

Your relative — the contributor

Fill in a copy

They get their own editable copy of the branch you handed over. They can't touch your master tree — they work in the copy.

A

Before you start: a safety copy

Optional — but reassuring
1

Duplicate a treeOwner

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.

Duplicate icon on a tree card
The duplicate icon sits on each tree card, next to Share.
B

Hand a branch to a relative

You, the owner
2

Open Share and switch to AdvancedOwner

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.

Share dialog switched to Advanced
The Share dialog, switched to Advanced.
3

Assign to a contributor and pick the branchOwner

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.

Protection. An assignment always requires the relative to sign in with Google, so their email identifies who's contributing.
Assign to a contributor, with an email and a starting person
Assign switched on, the relative's email entered, and Yusof chosen as the branch.
  1. Tick Assign to a contributor.
  2. Enter the relative's email.
  3. Start from — type a name to hand over just that branch.
  4. Protection — an assignment always requires Google sign-in.
4

Create the linkOwner

Click Create link and send the link (and passcode, if you set one) to your relative however you like — WhatsApp, email, anywhere.

The created share link
The link is ready to copy and share.
5

It shows as awaiting acceptanceOwner

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.

Dashboard showing a pending invite
The pending invite, awaiting your relative.
C

Your relative fills it in

Your relative, the contributor
6

They open the linkRelative

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.

Collaboration welcome splash
The collaboration welcome, naming who shared it.
7

They land in their own working copyRelative

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.

The working copy with a consent banner
The relative's editable copy, with the model-B consent banner.
8

They add peopleRelative

They use + Add Person to fill in their side of the family — here, adding Aisyah as a daughter of Yusof.

A newly added person in the working copy
Aisyah added under Yusof, in the relative's copy.
D

Watch progress & merge back

You, the owner
9

See progress in "Forks of my trees"Owner

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.

Forks of my trees monitor panel
Your monitor panel — watch each relative's copy from here.
  1. View — open their copy read-only.
  2. Merge back → — review and pull their changes in.
  3. Revoke — end the collaboration.
10

Peek, read-onlyOwner

View opens their copy read-only, so you can check their work without changing anything.

Read-only monitor view of a fork
A read-only look at the relative's copy.
11

Merge back — review firstOwner

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.

Merge preview screen
The merge preview: one person to add, nothing written yet.
  1. A summary of exactly what will change — add, update, conflicts.
  2. People to add — the net-new people coming in.
  3. Apply merge — commit once you're happy (still nothing written until you click).
12

Resolve any conflictsOwner

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.

A conflict on a birth date, owner chooses
Both sides set Yusof's birth date — you choose which wins.
  1. Per field, pick Keep mine or Take theirs (mine is the default).
  2. Or decide every conflict at once — Keep all mine / Take all theirs.
  3. Apply merge when you've resolved them.
13

Apply — and it's doneOwner

Click Apply merge. Salasilah snapshots your tree first (so you can undo), then writes the approved changes into your master tree.

Merge applied confirmation
The merge is applied — with an undo waiting if you need it.
14

Your relative is toldRelative

Merging is never silent: your relative sees a notice on their dashboard that you merged their contributions, which they can dismiss.

Contributor notified of the merge
The relative's "your contributions were merged" notice.
E

Undo a merge, if needed

You, the owner
15

The Undo-merge buttonOwner

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.

Undo merge toolbar button with a badge
The Undo-merge button appears once a merge has been applied.
16

Undo or dismissOwner

Clicking it lists your recent merges. Undo restores exactly what that merge changed (later edits are kept); Dismiss just clears the reminder without undoing.

Nothing is lost. Undoing a merge never deletes your relative's work — it still lives in their copy, ready to fix and merge again.
Undo merge list panel
The list of recent merges you can undo or dismiss.
F

Merge in your own small tree

Advanced — no relative involved
17

The Merge buttonOwner

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.

Merge button on the dashboard toolbar
The dashboard Merge button (Advanced mode).
18

Pick the two treesOwner

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.

Merge one tree into another picker
Pick the source tree and the target tree.
  1. Merge this tree — the small tree to fold in (copied, not moved).
  2. Into this one — your main tree, the only one that changes.
  3. Continue — on to matching people.
19

Confirm who is whoOwner

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.

Why confirm all? Two different people can share a name. Asking every time is the honest price of never silently fusing the wrong two.
Confirm who is who matching screen
Confirm each person before anything is linked.
  1. Read who Salasilah thinks might already be in your tree.
  2. For each person, pick Same as … or Add as a new person.
  3. Continue to review and apply the merge.
G

End a collaboration

You, the owner
20

Revoke accessOwner

When a branch is done, Revoke on its row ends the collaboration: it drops off your monitor panel and the share link stops working.

Their copy stays theirs. Revoking only severs the link — your relative keeps their copy as an ordinary tree of their own, and they're told the collaboration ended.
Revoke button on the monitor panel
Revoke ends the collaboration; the relative keeps their copy.