Salasilah · Step-by-step

Choosing how to share

Every share you make answers two separate questions: how much of the tree goes out, and how the person proves they’re allowed in. Pick one from each — that’s the whole system.

✎ Draft. Screenshots are auto-generated from the live app (re-runnable). English only for now. The numbers on each picture are the step numbers that explain them.
Decision 1 — Scope

How much goes out

Whole tree, one person’s bloodline, or exactly what’s on your screen. People outside your choice are never sent at all.

Decision 2 — Protection

Who can open it

Passcode only, Google sign-in, or both — never neither. A Simple share has no passcode: it is held by sign-in alone, which is why there is nothing extra to send. Both decisions describe a link; live access is not a link and has neither.

A

Where sharing starts

Open the tree first
1

Share lives in the tree, not the dashboard

Open the tree, then press Share in the toolbar. There is no Share button on the dashboard tree cards: choosing how much to send needs the tree on screen, because two of the three options are defined by what you are looking at.

The dashboard still shows a “N shared” badge on any tree that has live links — that is for finding and revoking what you have already sent, which needs no tree.
The Share button in the tree editor toolbar
Share, in the tree editor’s toolbar.
2

Simple decides both for you

If you do not want to think about it, stay in Simple and press the button. Simple always picks whole tree + Google sign-in, read-only. No passcode is set, so there is nothing extra to hand over — the recipient just signs in with Google.

Everything else in this guide is Advanced. Your choice of tier is remembered on this device, so switching once is enough.

The share dialog in Simple mode
Simple: one line of explanation, one button.
3

Advanced shows the two decisions

They sit at the top and the bottom of the same form, and they are completely independent — any scope works with any protection.

  • Share — the scope. How much of the tree goes out (steps 4–6).
  • Protection — how the recipient proves they are allowed in (steps 7–9).
The choice in between — “What should this person be able to do?” — is a third, separate question: a read-only link, a contributor’s copy, or full live access. It has its own walkthrough in the Sharing step-by-step guide. Everything below assumes View it, the default.
The share dialog in Advanced, with the scope and protection choosers marked
Badge numbers are step numbers: 4 the scope selector · 7 the protection chooser.
B

Decision 1: how much goes out

The Share selector, at the top
4

Whole tree

Everyone, including anyone you add later. This is the default, so one-tap sharing stays one tap.

Use it for the family group chat, or anyone you would be happy to show the whole tree to in person.

The scope selector set to Whole tree
Each option carries its own headcount, so you can see what you are sending.
5

One person’s bloodline

That person’s ancestors and descendants, plus their direct spouses — but not the cousins, in-laws and side branches hanging off the rest of the tree. The person used is the tree’s subject, so change the subject first if you want someone else’s line.

Use it for one side of the family: they get their own line complete, and nothing about anybody else’s.

The scope selector set to a person's bloodline
12 people in the tree, 8 in this bloodline — the uncle and cousins stay behind.
6

Current tree view

Exactly the people on your screen right now — whatever the generations window and the Show toggles have left visible. Set the screen up the way you want it before pressing Share.

Use it for a specific slice you have already framed: three generations, or one branch you were just working on.

A scoped share is a real wall, not a starting position. The people outside your slice are never sent to the browser at all — the recipient cannot pan or zoom out to find them.
The scope selector set to Current Tree View
Six on screen, six in the link.
C

Decision 2: who can open it

The Protection chooser, further down
7

Passcode only — no account needed

Anyone with the link and the 4-digit passcode can open it. No sign-in, no Google account, nothing to set up.

Use it for older relatives, or anyone who does not have (or want) a Google account. Tap Generate for a code, and send it in a different message from the link — a link and its passcode in the same WhatsApp message is one forward away from being public.

Protection set to Passcode only, with a generated code
Passcode only — the passcode box appears underneath.
8

Google sign-in — nothing to hand over

The recipient signs in with Google. There is no code to send, remember or leak, and you can optionally list Allowed emails so a forwarded link still will not open for anyone else.

Use it for anyone who already lives in Gmail, and for anything you would rather not have travelling around as a plain link. Leave Allowed emails blank and any signed-in Google account can open it.

Protection set to Google sign-in, showing the Allowed emails box
Google sign-in, with the optional allow-list.
9

Both — sign in and know the code

The recipient must do both. Two independent things have to leak before a stranger gets in.

Use it for the sensitive shares — anything heavy on living people, or a link you expect to sit in someone’s inbox for a long time.

There is no “anyone with the link” option — but that does not mean every link has a passcode. Two of the three styles do; Google sign-in, which is what Simple uses, has none. What every link has is at least one of the two. That is deliberate, and the server enforces it: a bare link is one forward away from being public, and family trees are full of other people’s personal data.
Protection set to Both
Both — sign-in and passcode.
D

The third way: live access

When a link is the wrong tool
10

A link is a snapshot. This is not.

Everything so far makes a link: a fixed slice of the tree, sent to whoever holds it. Live access is a different thing entirely — you name one person by email, and they see the tree as it is now, on their own dashboard, for as long as you allow it.

Neither decision applies to it. There is no scope to pick and no protection to set, which is why choosing it makes both of those controls disappear.

  • A link — any scope, passcode or sign-in, expires, works for anyone holding it, and shows the tree as it was when you made it.
  • Live access — whole tree, one named Google account, no expiry, cannot be forwarded, and always current.
It is unredacted. A link hides living people's details and private notes. Live access does not — that is the trade for it being the real, current tree. Give it only to people you would trust with the whole thing.
11

Choose "Give live access"

It is the amber option in What should this person be able to do? — amber because it is the only choice that hands over everything.

Watch what happens to the form: the Share scope selector and the whole Protection block vanish, and Create link is replaced by Grant access. There is no link to make.

The share dialog with Give live access selected
Live access selected — no scope, no protection, no link.
12

Grant it by email

Type the Google address of the person you trust and press Grant access. Because the grant is tied to that one account, a forwarded message gets nobody anywhere — this is the most secure way to share, and the only one with nothing to leak.

They do not need an account yet. Until they sign in, the list shows them as not signed up yet, and the access is waiting when they do. Everyone you have granted is listed here with a Remove beside them, which takes it back immediately.

Get the address right. Access follows the email, so a typo silently grants nothing to nobody — there is no bounce to tell you.
A granted email listed under the live access panel
Granted — listed, revocable, and waiting for them to sign in.
13

What they see

Your tree appears on their dashboard under Live views shared with me, marked READ-ONLY, with your name against it. They are told once, in a banner, that you shared it.

It sits apart from their own trees — they cannot edit it, and nothing they do touches yours. Every time they open it they get the current version, with no new link from you.

The recipient's dashboard showing Live views shared with me
Their dashboard: the banner, and the tree under “Live views shared with me”.
E

Putting it together

Five situations, and what to pick for each
14

Five recipes

  • The family group chat — Whole tree + Google sign-in. Nothing to send but the link; anyone in the family who is signed in can look.
  • Grandma, who has no Google account — Whole tree (or her bloodline) + Passcode only. One code, sent separately, by phone if you like.
  • One side of the family — that person’s bloodline + Passcode only. They get their own line complete, and nothing about anyone else’s.
  • A specific branch, to someone outside the family — Current tree view + Both. The smallest slice, behind the strongest door.
  • Your brother, who helps keep it accurate — neither. Give him live access: no link, no passcode, no expiry, and he always sees the tree as it is now.
Whichever you pick, add a Label (“Cousins — read only”) and an expiry. In six months the label is how you will know what you handed out and to whom, and an expired link is one less thing to remember to revoke.
15

What you actually hand over

Press Create link. The link is copied to your clipboard straight away and shown in the box so you can copy it again. If your protection includes a passcode, it is printed underneath — that one goes in a separate message.

Every link you make is listed in the same dialog, where you can copy it again, change the passcode, extend the expiry or revoke it. That half of the story is in the Sharing step-by-step guide.
The created link with its passcode shown underneath
Created — link on the clipboard, passcode to send separately.