Your family
Admins and members
The person who creates the family becomes its first admin automatically. After that:
| Can they… | Admin | Member |
|---|---|---|
| Add events, to-dos, and shopping items | ✓ | ✓ |
| Manage their own profile, colour, and preferences | ✓ | ✓ |
| Leave the family | ✓ (see below) | ✓ |
| Rename the family | ✓ | – |
| Rotate the invite code | ✓ | – |
| Add a child | ✓ | – |
| Remove a member | ✓ | – |
| Promote/demote other members | ✓ | – |
| Delete the whole family | ✓ | – |

Adding a child
Children get a name and a colour but no login of their own: no email, no password, nothing to sign in with. You can tag them on events and to-dos, and admins can control which adults get reminded about their events (see below). This is specifically built for kids, not a general “add anyone without an account” feature. Every other member, however old, signs up and joins normally.
Getting another adult into the family
Two ways, both admin-only to set up:
| Method | How it works |
|---|---|
| Invite code | A short code shown on the Family tab. Share it however you like (text, verbally); they enter it themselves when signing up or from onboarding. |
| Invite by email | Enter their email under “Invite an adult by email” and FamKnit sends them a personal link to join directly. Only works for someone not already in the family. |

Who gets reminded about a child's events
By default, every adult in the family is reminded about a child's events and warned if something clashes. Admins can narrow this per child from the “Child event reminders” section, useful if, say, only one parent handles a particular activity. At least one adult always stays selected, and leaving everyone selected is the same as the default (a later-joining adult is automatically included too).
Expire prep to-dos
| Setting | What happens to an unfinished prep to-do once its event has passed |
|---|---|
| Off (default) | It stays visible and counts as overdue until someone completes it. |
| On | It's hidden once the event has passed, not marked done, just cleared off your list. |
This is a family-wide setting any admin can change, affecting prep to-dos linked to events for everyone.
Removing someone from the family
An admin can remove a member from their entry on the Members list. In short:
- Their private to-dos and private events go with them.
- Shared events and lists they created stay, reassigned to the admin who removed them.
- They keep their FamKnit login. They just land back on the “join or create a family” screen.
If you signed in a while ago, FamKnit asks you to confirm it's you before this goes through. The same applies to leaving and to deleting the family below. See Your account & data for how that works.
Leaving a family yourself
You can leave any time from the Family tab. It works the same way as being removed, with one extra rule: if you're the only admin and other adults remain, you'll need to promote someone else to admin first. If you're the last adult in the family, leaving deletes the whole family (any children on it have nowhere left to be).
Security activity
Admins onlyA record of who changed the family, and when: renaming it, rotating the invite code, someone joining, a child being added, roles changing, a member being removed or leaving, and the family being deleted. It's collapsed by default, hidden behind a “View” button, since most admins will rarely need it.
It never shows email addresses or IP addresses, on any screen, to anyone. If FamKnit ever needs to look into a security question, that detail is kept, but not surfaced here (see Your account & data for how long).

Deleting the whole family
Admins onlyThis permanently destroys every event, list, and to-do in the family. Nobody's FamKnit login is affected. Everyone just ends up without a family, same as after being removed.
| Family has… | What happens when you confirm |
|---|---|
| Only one admin | Deletion happens immediately, no waiting. |
| More than one admin | A request is created. Every OTHER admin must approve it. You'll see a banner showing who's approved so far, and they get an actionable notification with Approve/Reject buttons right in the bell dropdown. |
One rejection cancels the request outright. The person who started it has to begin again if they still want to.