Salasilah · Step-by-step

Sharing a family tree

Send a link in one tap, share just part of a tree, add a passcode, or give someone full live access — and take any of it back. 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

Decide what goes out

You choose how much of the tree to send, who can open it, and for how long. Every link you make is listed where you can find and revoke it.

Your relative — the recipient

Opens a read-only view

They can pan, zoom, search and export — but not edit. Names are shortened and living people's dates reduced before the page ever reaches them.

A

Share a tree in one tap

The whole job, start to finish
1

Open the tree, then press ShareOwner

Sharing starts inside the tree, in the toolbar. There is no Share button on the dashboard tree cards: two of the three things you can send are defined by what is on your screen, so the tree has to be open.

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

Simple mode has one buttonOwner

There are no decisions to make. Simple always creates a read-only view link protected by Google sign-in — so there's nothing extra to hand over.

The share modal in Simple mode
Simple mode: one line of text, one button.
3

The link is already copiedOwner

Paste it straight into WhatsApp. The link is also shown and pre-selected in the box, so if your browser blocks the automatic copy you can still tap Copy.

Links expire. By default a link stops working after 7 days. Advanced mode lets you change that, or set 0 for a link that never expires.
The created link, ready to paste
Created and copied — nothing else to do.
B

What your relative actually sees

Your relative, the recipient
4

They open the linkRecipient

A welcome screen names the tree they've been invited to. The notice at the bottom explains the privacy rules up front, so nobody thinks the shortened names are a mistake.

The shared-tree welcome screen
The welcome screen, with its privacy notice.
5

The same tree, two different viewsRecipient

This is the part worth understanding. Below is the same tree, at the same moment — on the left as you see it, on the right as your relative sees it through the link.

Full names become a single given name. Ahmad bin Ismail becomes just Ahmad — note that this also removes his father's name. Living people's birth dates disappear from the card, and private notes are never sent at all.

The tree as the owner sees it, with full names
You: full names, full dates.
The same tree through a shared link, with shortened names
Them: given names only.
This happens on the server, not in the browser. The full names are never sent to your relative's computer — there's nothing hidden in the page for a curious recipient to dig out.
Even the deceased are shortened. That's deliberate: a name like "Ahmad bin Ismail" reveals his father Ismail, who may still be living. Dropping the patronymic closes that gap. Deceased people do keep their full birth and death dates — those are the genealogical record.
6

What they can do with itRecipient

The shared view has its own slim toolbar. They can change how many generations show, search, switch theme, and Export the tree as an image or PDF — but there's no Add Person or edit control anywhere, because the link is read-only.

  • View time left — the link's expiry, shown honestly so nobody is surprised when it stops working.
  • Start your own tree — the way a relative goes from looking at yours to building their own.
The shared tree view with its read-only toolbar
The recipient's toolbar — no editing controls, and the expiry in plain sight.
C

Share only part of a tree

From inside the tree editor
7

Frame the screen before you press ShareOwner

The same Share button from step 1 also decides how much goes out — and one of the choices is “exactly what is on screen now”. So set the generations window and the Show toggles the way you want them first, then press Share.

Which combination to pick for which relative is its own guide: Choosing how to share.

8

Pick how much to sendOwner

A Share selector appears at the top of the form with three choices, each showing how many people it covers:

  • Whole tree — everyone. The default, so one-tap sharing stays one tap.
  • Current Tree View — exactly the people on your screen right now.
  • [Person]'s bloodline — that person's ancestors and descendants, plus their direct spouses.

The selector shows in both Simple and Advanced, so you can still create a scoped share in one tap.

A scoped share is a real wall. The people outside your chosen slice are never sent at all — your relative can't pan or zoom out to find them.
The Share scope selector with three options
The scope selector, with a headcount on each option.
D

Advanced: choose what they can do

You, the owner
9

One question firstOwner

Advanced asks "what should this person be able to do?" and then shows only the settings that matter for your answer.

  • View it — a read-only link. Pan, zoom, search, export; no editing.
  • Help build it — they get an editable copy to fill in and you merge their work back later. This is the door into collaboration, which has its own guide.
  • Give live access — the amber one. Full, live, unredacted. See Part E.
A fourth option, "Take their own copy", appears for administrator accounts. It hands over an independent copy that doesn't report back to you.
The intent chooser with three options
Pick the intent; the form follows.
10

Decide who can open itOwner

  • ProtectionPasscode only (good for relatives with no Google account), Google sign-in (nothing extra to send), or Both.
  • Passcode — tap Generate for a 4-digit code. Send it separately from the link, not in the same message.
  • Allowed emails — with Google sign-in you can list specific people, so a forwarded link still won't open for anyone else.
Protection options with a generated passcode
Passcode, sign-in, or both.
11

Label it and set an expiryOwner

  • Label — a note to yourself, like "Cousins — read only". In six months this is how you'll know what you handed out and to whom.
  • Expires in (days) — 7 by default, or 0 for never. A short expiry is the cheapest safety net there is.
Label and expiry fields
Label and expiry, just above Create link.
12

Send the passcode separatelyOwner

When you've set a passcode, it's shown with the new link — and you can copy it again later from the links list.

A created link showing its passcode
The link and its passcode.
E

Give someone full live access

Trusted people only
13

This one is differentOwner

Everything else on this page is redacted. Live access is not. The person you name sees the whole tree exactly as you do — full names, living people's dates, private notes — live, on their own dashboard, read-only.

It's marked amber for a reason. There's no link and no passcode: it's a grant tied to one email address. Give it only to people you trust with everything.
The live access panel with its warning
The live-access panel, kept visually set apart.
14

Grant it by emailOwner

Type their email address and press Grant access. They don't need an account yet — the grant is keyed to the address and starts working the moment they sign up.

Entering an email to grant live access
One email address at a time.
15

Everyone with live access is listedOwner

The panel lists who currently has live access, and lets you remove any of them. Removing takes effect immediately.

Read-only means read-only. Someone with live access can never edit your tree — the app blocks writes for grantees regardless of what they try.
The list of people with live access
Who currently has live access.
F

Managing what you have sent

Find it, extend it, change the passcode, take it back
16

Every link you've made is listedOwner

  • Search — paste a URL or type a label to find one link among many.
  • Each link shows its label, its scope, how it's protected, when it expires and when you made it — with Copy, Extend and Revoke beside it.

The next three steps take those three buttons in turn. Nothing here is destructive except Revoke, which asks first.

This list is Advanced-only. Simple mode deliberately doesn't show it — it's a one-tap create, nothing else. Switch to Advanced to manage what you've sent.
The existing links list with copy, extend and revoke
Existing links, with Copy / Extend / Revoke on each.
17

Extend a link, or stop it expiringOwner

Press Extend and pick how long it should stay active counting from now — not from when you made it. Never expires is there for the link you keep in the family group chat.

An expired link is not gone. It stays in this list marked EXPIRED in red, and extending it brings it back to life — same URL, same passcode, so there is nothing to re-send. If you would rather it stayed dead, revoke it.
The Extend link dialog offering 7, 30, 90 days or never
Extend: 7, 30 or 90 days from now — or never expires.
18

Re-copy or change the passcodeOwner

The passcode is printed on the row, so if a relative lost it you can just copy it again — you do not need to make them a new link. edit turns the line into a box: type a new code or press Generate, then Save.

Changing it takes effect at once. Anyone still using the old code is locked out until you send them the new one, which is exactly what you want if a link went somewhere it should not have.

You cannot remove the last lock. If Google sign-in is off, the passcode is the only thing holding the link, so clearing it is refused — a share always keeps at least one gate.
A link row with its passcode being edited in place
The row, and the passcode editor opened in place. Every part of the row is labelled: name, scope, protection and expiry, then when you made it.
19

Revoke itOwner

Revoke kills the link immediately for everyone holding it — anyone with it open loses access on their next move. You are asked to confirm because it cannot be undone: there is no un-revoke, and a new link is a new URL.

Nothing about your tree changes. Revoking removes the way in, not any data.

Not sure which of five links went to whom? That is what the Label is for. If you did not set one, the row still shows the scope, the protection and the date you created it — usually enough to recognise it.
The revoke confirmation dialog
Revoke asks first — it cannot be undone.
20

The shortcut: the "shared" badgeOwner

A tree that has live links shows a count on its dashboard card. Tapping it opens the share modal straight at the list above — switching to Advanced for you, since that's plainly a manage-what-I-sent intent rather than a make-another-one intent.

The shared count badge on a dashboard tree card
The count badge is a shortcut into the links list.