Permissions protect family history without blocking collaboration. Workspace roles give broad permissions, while tree access allows finer limits.
Roles, permissions, and tree access
Distinguish owner, admin, editor, and viewer
Decide when to use all-tree access or selected-tree access
Invite relatives with the right level from the start
Giving admin access to someone who only needs to comment or review
Forgetting that an editor can change family content
Using all-tree access when limited access is enough
Use viewer for reading, editor for correcting data, admin for invitations, and owner for full control.
If someone should only see one branch, assign only the required trees.
At least one owner with broad access must remain to avoid administrative lockout.
Use Activity and Audit to review important modifications.
Help us keep the documentation accurate. If something is missing, send the context and the section you were using.
Invite members, assign roles, and connect an account with a family profile when appropriate.
Protect sensitive details about living relatives and understand what viewers can see.
Restore archived items and review important changes in the family workspace.