The decision behind the feature
Tap Tap Go’s product model includes event, ticketing, membership and engagement programme concepts configured for the relevant organiser. Work from approved public event content and the intended resource audience. Being registered for an event does not automatically make every attendee’s information public.
Check the handoff before acting
Before sharing, review three points: check names in documents; confirm directory permissions; avoid exposing private registrations. Ask yourself: Which participant details are approved for this audience?
Hypothetical example
Imagine an organiser sharing resources with participants. In this hypothetical scene, the resource page includes programme information while contact sharing remains a separate choice.
Make it practical.
Use this checklist as you read. Checks are not stored.References & further reading
Tap Tap Go Journal: product context and editorial approach ↗Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
