Skip to content

Dependents

A dependent is a gift recipient who doesn’t have a GiftWrapt account: a pet, a baby, a grandparent who never wanted to sign in, anyone with no expectation of autonomy in the app.

Dependents have a name, an optional photo, an optional birthday, and one or more guardian users who manage their lists. They never sign in.

GiftWrapt has three different “people” concepts; here’s when each one applies:

Has an account?Manages own lists?Typical use
UserAn adult family member or friend
Child (role)with helpA kid old enough to have a login but young enough that a parent helps manage things
DependentA pet, a baby, or anyone who shouldn’t have an account

If the person is going to sign in - now or later - make them a user (or a child user). Use a dependent only when there will never be a login.

FieldNotes
NameRequired. Used everywhere the dependent’s identity is rendered.
PhotoOptional. Falls back to a Sprout icon.
BirthdayOptional. Drives birthday reminders and auto-archive timing if the dependent owns birthday lists.
GuardiansOne or more user accounts who manage the dependent’s lists. Same model as guardian-of-a-child.

What a dependent does not have:

  • An email address (better-auth’s “users have emails” rule stays intact)
  • Roles, partnerships, or access levels
  • A way to sign in or be impersonated

A dependent’s guardians have the same full view + edit access on the dependent’s lists that guardians of a child user have. See Guardians for the full grant.

A dependent can have any number of guardians (a pet in a multi-adult household is the obvious case). Removing one guardian doesn’t affect the others.

A list can have a dependent as its subject. The list itself is still owned by the user who created it (ownerId, which is the guardian), but the recipient of the gifts is the dependent.

Permission checks key off the subject, not the owner:

  • Any guardian of the subject dependent has full view + edit access.
  • An explicit None from any guardian denies the viewer (every guardian has to be willing).
  • Public / private toggles still work the same way.

The guardian doesn’t accidentally see the recipient view of their dependent’s list. If they open it, they get the gifter view - they’re a gifter to the dependent, not its recipient.

Everywhere GiftWrapt would normally render “whose list is this?”, a dependent-subject list renders the dependent’s avatar and name instead of the guardian’s. Specifically:

  • List rows in feeds, dashboards, and pickers swap to the dependent’s avatar and drop the Crown badge (a dependent isn’t a list owner).
  • The list-detail header shows the dependent’s photo and name.
  • The recent feed shows the dependent on items and conversations from those lists.
  • Purchases / received-gifts summaries swap the recipient-rendered fields to the dependent.

The guardian’s identity isn’t hidden anywhere it’s relevant - it’s just that “the person this gift is for” is the dependent, not the guardian who created the list.

The list’s guardian can claim items on their own dependent’s list. Same rule as guardians claiming on a child’s list: the guardian is the gifter, the dependent is the recipient, and gift credit follows the normal partner-aware predicate.

The “you can’t claim on your own list” block only fires when the list has no dependent subject and the gifter is the owner.

Dependents are created from the dependents settings page by any non-child user. The creator is automatically added as a guardian; other guardians can be added afterward.