# Setting eligibility and slip prerequisites Eligibility is the list of students whose parents can book into an event. A slip prerequisite is a permission slip that must be submitted before booking is allowed. Together they decide who can book and what they have to do first. ## Setting eligible students Every booking event has a student list. Parents see the event on their dashboard only for children who are on that list. ### From the create/edit form When you create a booking event, the **Students** field is a tick-box list of every student at the school. Tick the students who are eligible. For year-level events, an easier approach is to filter the student list first (by year group or by class) and tick the result. ### From the *Manage students* page After the event exists, use **Manage students** on the event detail page to add or remove students without going through the full edit form. ### When the event is in a group with *Override students* on The event's own student list is ignored. The group's student list applies instead. See [Grouping recurring booking events](/portalhq/articles/grouping-recurring-booking-events/). ## Slip prerequisites A slip prerequisite is a permission slip the parent must submit before they can book. Use this when you want to gather consent or information up front — e.g. a *Year 12 Camp consent form* must be in before the parent can book a camp interview slot. To configure: 1. Open the event edit page. 2. Tick **Requires submitted slip**. 3. Pick the specific slip from the **Slip required** dropdown. Only slips your school has set up in the Slips module appear here. 4. Save. ### What parents experience When *Requires submitted slip* is on: - Parents see the booking event on their dashboard as usual, but the **Book** button is replaced by a prompt to submit the slip first. - Clicking through takes them to the slip form. They fill it in and submit. - Once the slip is in, they can come back to the booking event and book normally. If a parent has already submitted the required slip for that student (e.g. from a previous prompt), they go straight to the booking flow. ### Slip status doesn't carry across students The check is per-student. A family with two eligible children has to submit the slip once for each child before booking each of them. ## Combining eligibility, slips and groups The three settings layer together: 1. **Group with override students** (if set) — defines the student pool. 2. **Event-level student list** — if no override, this defines the pool instead. 3. **Slip prerequisite** — applies to every student in the pool. They have to submit the slip before booking. Make sure all three are consistent. Common mistakes: - Forgetting to add new enrolments to the student list — they won't see the event. - Turning on *override students* on a group without also setting the group's student list — the events become invisible to everyone. - Linking a slip that's been retired — the parent gets a broken link. ## Auditing eligibility before launch Before opening bookings: 1. Open the event detail page. 2. Check the eligible student count looks right (e.g. *180 students eligible* for a year-level event). 3. Check the slip prerequisite (if any) points at the right slip. 4. Hide the event (see [Hiding, closing and copying events](/portalhq/articles/hiding-closing-and-copying-events/)) and test from a parent account to confirm the flow works as expected. When you're happy, unhide the event and parents can start booking.