A registration may appear in the client portal only through an authorized customer or registration relationship and configured portal settings. A normal contact portal link is not automatic permission to reveal every participant record connected through a household.
Step by step
- Decide which customer owns portal access for the registration: normally the purchaser or an explicitly authorized guardian customer. Confirm the contact identity and household association before enabling event registration content.
- Keep the attendee or camper as a separate reusable participant. Link the participant to the guardian customer where appropriate; do not merge a child into the purchaser profile to make a portal query easier.
- Configure offering and ticket portal settings for the minimum useful view: offering name, occurrence schedule, venue or meeting instructions, registration number and status, participant display name, approved tickets, calendar action, and public attachments.
- Do not expose birth date, medical details, diagnosis, allergies, medication, emergency contact, authorized pickup, waiver/signature evidence, school or student identifiers, accessibility notes, raw form answers, ticket credential hashes, internal notes, or staff fields in a general portal response.
- Show registration-form and waiver status only through the safe completion projection: an overall completion summary and per-requirement Complete, Incomplete, or Not required state. Never include an answer value, signature, waiver document, credential, or protected form payload in the portal completion response.
- When more than one guardian is associated, use explicit authorization rather than household inference alone. A purchaser, guardian, attendee, pickup contact, and emergency contact are different roles and must not be treated as interchangeable.
- Give each sibling or attendee their own participant identity and registration links. The portal may group registrations for presentation while reporting and access checks continue to preserve the individual record.
- For online or hybrid events, reveal meeting URLs only to the authorized attendee or household at the intended lifecycle point. Keep them out of public feeds and search indexing unless the business deliberately publishes an open meeting.
- Show Public assets plus Attendees assets only for a registration this portal identity is authorized to view. Staff assets never enter the customer portal. Private forms and signed documents use a separately authorized flow with appropriate retention and download auditing.
- On cancellation, transfer, ticket revocation, or guardian change, re-evaluate portal access immediately. A previously delivered calendar file or downloaded attachment cannot be remotely recalled, so avoid putting unnecessary private data in either.
- Test with the purchaser, an authorized guardian, an unrelated customer, a sibling household, a staff user, and an expired or revoked portal session. Each identity should receive only its permitted registration projection.
- For an adult self-attendee, the verified purchaser and participant can share one customer identity. Portal access follows that customer relationship without inventing a household or guardian link.
- Return Attendees assets only after the portal resolves a view-authorized registration. Do not send event tabs or registration files through a generic contact portal when the customer has no purchaser, participant, or explicitly authorized guardian relationship to that registration.
- Page registrations beyond the first result set with before_registered_at and before_registration_id together; the default is 25 and maximum is 100. Never send a timestamp cursor without its ID tie-breaker.
- Page each registration child resource independently with limit and after_id, at most 100 per page. The exact resources are participants, tickets, agenda, schedule, assets, requirements, assignment_forms, assignment_questions, assignment_waivers, assignment_groups, assignment_group_occurrences, and assignment_sessions. The assignment-definition limits are 4 forms, 10 questions, 1 waiver, 100 groups, 100 group occurrences, and 50 sessions per page.
- Use the token-scoped assign_event_registration_seat POST only for purchaser_self or new_participant. The body is limited to 256 KiB and carries registration_id, optional ticket_id, expected_version, idempotency_key, identity, and bounded answers, waivers, and concrete occurrence selections. A successful assignment promotes exactly one pending seat to an active participant-bound ticket while remaining seats stay pending.
- Portal ticket history exposes ticket_code and a QR only when the ticket is participant-bound, unexpired, and Valid or Used. Pending assignment, Voided, Transferred, and Expired rows return ticket_code null, credential_active false, and viewer_authorized false.
- A manager-native Attendees asset is limited to 25 MiB and delivered only through /account-portal-event-asset/<capability>/<assetId>. The branded capability expires after five minutes and the portal response never contains the event-assets bucket, object path, Supabase hostname, or project URL.
- Privacy-filtered child pages advance their keyset cursor even when every row on that page is hidden and visible data is empty. Continue until has_more is false; do not retry the same cursor or infer that an empty visible page is the end.
- Unexpected portal and public-quote failures return a generic safe error. Use the request correlation ID for support; never expose internal table, Storage, project, stack, or validation detail to the customer.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Portal owner | Customer identity authorized to view the registration in the client portal. |
| Participant | Reusable attendee or camper identity separate from the portal customer. |
| Guardian association | Relationship between participant and responsible customer; not alone proof of every portal permission. |
| Registration projection | Minimum portal-safe offering, schedule, status, ticket, and instruction fields. |
| Sensitive answer | Medical, emergency, waiver, pickup, birth, school, or comparable private form content. |
| Form and waiver completion | Aggregate and per-requirement status only; it is not an answer, signature, or document payload. |
| Meeting URL | Attendee-only join information unless intentionally public. |
| Public attachment | Asset explicitly approved for customer access. |
| Ticket credential | Admission secret that must be delivered only to the authorized attendee or household. |
| Transfer / revocation | Lifecycle change requiring access and ticket re-evaluation. |
| Unrelated contact portal | Must not receive event registration details merely because the contact exists in the same tenant. |
| Adult self-attendee | Purchaser and attendee share one verified customer identity, with no self-guardian relationship. |
| Attendees asset | Registration-authorized portal file excluded from the anonymous feed and unrelated customer portals. |
| Registration cursor | Atomic before_registered_at plus before_registration_id pair; default 25, maximum 100. |
| Child resource page | Independent limit/after_id keyset page, maximum 100, with resource-specific assignment-definition limits. |
| Portal seat assignment | Token POST supporting purchaser_self or new_participant only, expected version, idempotency, answers, waivers, and concrete selections within 256 KiB. |
| credential_active | True only for a participant-bound, unexpired Valid or Used ticket; every other lifecycle row is QR-inactive. |
| Five-minute asset URL | Branded capability route for authorized native attendee files; never a reusable Storage URL. |
| Generic customer error | Fail-closed portal or quote response with a safe message and correlation ID, not internal diagnostics. |
Expected result
Only an explicitly authorized purchaser, guardian, or attendee sees the minimum approved registration projection, while unrelated contacts and public routes cannot retrieve child, medical, emergency, waiver, pickup, credential, or private-answer data.
Troubleshooting
- Confirm the exact offering, occurrence, ticket option, timezone, and participant before changing registration or attendance.
- Check shared capacity pools and linked morning, afternoon, or full-day sessions before changing availability.
- Keep camper, guardian, medical, waiver, and pickup details out of public feeds, screenshots, webhooks, and general CRM fields.
CentriPOS API explorer · API Center administration