Role glossary

# Part 18 — Role glossary (appendix)

| Term | Meaning |
|---|---|
| **Author** | The internal user who can edit project content directly. |
| **Reviewer** | A collaborator who can comment and suggest but not commit edits. |
| **Approver** | A collaborator who can approve content per language. |
| **Client** | The person who owns the project on the dashboard (you, by default). |
| **Family member** | Someone invited to the **Family portal** to view but not edit. |
| **Heir** | Someone invited to the **Legacy portal** for generational handoff. |
| **Primary successor** | The first named heir in continuity. |
| **Secondary successor** | A backup successor. |
| **Executor** | A successor with the right to issue release attestations and (optionally) trigger unlocks. |
| **Next‑generation** | A successor reserved for a future generation depth. |
| **Visitor** | An anonymous user looking at a public or semi‑public memorial page. |
| **Unlock condition** | A rule that determines when a successor's access takes effect. Five kinds: date / event / executor‑approval / age / generation. |
| **Release attestation** | A signed link issued by an owner or executor that unlocks a project ahead of schedule. |
| **Visibility mode** | Memorial page setting: public / private / semi‑public. |
| **Generation depth** | A number — 1 = primary (you / parent), 2 = grandchild, 3 = great‑grandchild, and so on. |

---

*End of guide. Welcome aboard. — The Roots We Planted team.*