Families, answers, options and payment shares

Who an answer belongs to and who can read it

On the web, check family/party setup, attendee categories, guardian requirements and capacity before publishing. A question may apply per person or to the whole booking; check whether answers and options belong to each attendee or just once. Review the summary for the correct combination before sharing. Use ordinary questions for practical information, not an open field for health data. This editor cannot save protected questions. Event manager and finance roles do not grant sensitive-answer access; separate protected-reader access has purpose and auditing. If configuration is refused, correct the field/scope or use an agreed access process, not ordinary messages to collect the data.

Included, required and paid are different choices

Check configuration and the current quote for employer and participant shares. Do not derive your own split from an old price. An included garment, a required size answer and a paid extra are three different things; a mandatory size does not automatically make the garment chargeable. After registration, check whether answer editing or a change request is available, its deadline and applicable configuration version. Read both the decision status and any price/payment change; an accepted change is not automatically a receipt for a paid difference. For a conflict, reload the current booking before retrying and do not promise an exchange or refund before a decision.