Hosted Invitations
Purpose, scope, and prerequisites
Section titled “Purpose, scope, and prerequisites”Hosted Invitations are named, private invitations to independently hosted sponsor gatherings—not official program sessions, public listings, or a contact-disclosure path. Admins use /admin/hosted; sponsor users use /sponsor/hosted; invitees use /hosted.
Product boundaries
Section titled “Product boundaries”Pending and accepted invitations consume capacity; acceptance needs no second host approval. Contact sharing is an explicit attendee choice limited to the named primary host. Do not infer, disclose, or export contact data from a roster.
Admin procedure
Section titled “Admin procedure”- Confirm the sponsor and legitimate operational question before opening a gathering.
- At
/admin/hosted, use Gatherings for visibility and Venues for curated venue suggestions. - For a new venue, enter name and address; property, website, and meeting hint are optional. Confirm success and refresh the list.
- Toggle a venue inactive/hidden rather than deleting historical information.
- For capacity/state, cancellation, contact-sharing, or messaging anomalies, capture the gathering/invitation ID and escalate; do not write directly to the database or bypass a gate.
Expected result and recovery
Section titled “Expected result and recovery”Venue changes affect future suggestions; they do not prove existing gatherings changed. Material gathering-detail edits can trigger participant updates, so obtain sponsor/event approval. Never promise that a notification, calendar update, or maintenance sweep occurred without observed target-environment evidence. For privacy impact, stop and use incident response.