Groups and households
Organizations know their people. EntryWick keeps that knowledge — households, guardians, groups and their leads — instead of flattening it into a list of names.
Two structures run through every EntryWick event. Groups are your organization — regions, congregations, schools, teams — arranged in a tree. Households are the people who register together — a family, a carpool, a roster. Both are kept all the way to check-in, which is why a youth's ticket can name the adult bringing them and a group lead can see only their own people.
Step by step
- 1
Set up the group tree
Settings → Groups. Create groups and nest them. Each group has a code (used in imports and the API), optional leads, and can own a pre-check point. People are attached to a group when they register (by choice, by their email domain, or by import).
A tree your organization already recognises. - 2
Give group leads their own view
Invite a lead and give them the Group lead role scoped to their group. They see the registrations, attendees and check-ins inside their subtree and nothing outside it. Roles are built from permissions, so you can also make your own — "Desk volunteer: register walk-ups, print tickets, nothing else".
Seats per plan: Free 2, Starter 5, Growth 15, Scale 50. Custom roles are a Growth feature.
A lead sees their own people, not the whole region. - 3
Households register once
A parent registers everyone in one go. EntryWick creates one household holding each person as an attendee with their own type (adult, youth, child, volunteer…) and their own days. Shared contact details are stored once, so a change of phone number is made once.
One household, four attendees, each with their own type and days. - 4
Guardians and companions
A minor's attendee record names a guardian from the same household. A youth's ticket can be shared with the adult bringing them, so one scan admits both and the scanner asks "Everyone here?". If the guardian later cancels, EntryWick refuses unless another adult of the right type can take the companions — a child is never left outside because an adult's ticket quietly stopped working.
A shared ticket at the gate: tick everyone present. - 5
Pre-check at the group, confirm at the venue
For events where people gather locally before travelling, give each group a pre-check point. It holds only that group's roster, works offline, and records "left Houston Central at 3:40 AM". The venue gate is the count that decides how full the hall is. Both appear in the live view, side by side.
Counted twice on purpose: departure and arrival.
When you are done
What should be true now
- Your tree matches how your organization actually works, with codes you recognise.
- Each lead signs in and sees only their group.
- A test household with a youth has a guardian named and a shared ticket.
- If you pre-check, each group has its own point.