> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/events-and-ticketing.md). # Events & Ticketing Typed event data, governed properties, admission, check-in, payments, refunds, and payouts. ISLAMU Event keeps event domain content, attendee registration, payment truth, admission issuance, and physical check-in as distinct authorities. This section explains each lifecycle and the invariants operators must preserve. *** ## In this Section * [**Modular Event Aspects**](/islamu-event/documentation/readme/events-and-ticketing/modular-event-aspects.md) — Relational sector models (Islamic-event details, prayer times, speakers, technology tracks) and feature module gating. * [**Custom Properties**](/islamu-event/documentation/readme/events-and-ticketing/custom-properties.md) — Governed custom registration questions, privacy exposure ceilings, property retirement, and GDPR data scrubbing. * [**Ticketing & Check-In**](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md) — Registration vs. admission, cryptographic QR credentials, attendee recovery, and day-of-event check-in gates. * [**Guest Participation Without Email**](/islamu-event/documentation/readme/events-and-ticketing/email-optional-participation.md) — Save a private post-confirmation status link and keep it separate from checkout and public calendar files. * [**Paid Events & Payouts**](/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.md) — Organizer-direct Stripe Connect onboarding, webhook reconciliation, refund workflows, and payout boundaries. *** ## Operating Invariant Before publishing a paid or controlled-entry event, verify module policy, registration capacity, provider-confirmed payment/refund state, admission issuance, credential recovery, and exact-target check-in. Current server-issued [HAL links](/islamu-event/documentation/readme/security-and-identity/authorization.md#the-golden-rule-of-client-ui-affordances) govern every operator affordance. ## Removing a Scheduled Item Deleting a session, session group, or agenda item removes that item's venue and room references together. It does not delete the shared venue or another scheduled item's location assignment. *** ## Related Guides & Next Steps * [**Administration Guide**](/islamu-event/documentation/readme/administration-and-branding/admin-guide.md) — Configure platform monetization and organization verified badges. * [**Email SMTP Notifications**](/islamu-event/documentation/readme/communications-and-notifications/email-smtp.md) — Reliable ticket delivery and event confirmation emails. * [**Webhooks & Callbacks**](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md) — Reconcile external ticket sales and payment status changes. * [**Privacy Erasure & GDPR**](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md) — How attendee registrations and custom answers are scrubbed on account deletion. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://islamu.gitbook.io/islamu-event/documentation/readme/events-and-ticketing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.