> 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/custom-properties.md).

# Custom Properties

Govern long-tail event and session data with explicit exposure and use grants.

Custom properties allow organizers and tenant administrators to capture legitimate long-tail fields on events, sessions, and attendee registrations. They provide flexible data collection without polluting the core relational schema or weakening domain invariants (see [Modular Event Aspects](/islamu-event/documentation/readme/events-and-ticketing/modular-event-aspects.md)).

***

## Governance & Exposure Ceilings

Each property definition enforces strict access and privacy controls:

* **Value Type**: Text, Number, Boolean, Single-Select, Multi-Select, or File Attachment.
* **Exposure Ceilings**:
  * `Public`: Visible on public event listings and marketing pages.
  * `Private`: Visible strictly to authenticated organizers and event staff.
  * `System`: Restricted to platform background processes and administrative tooling.
* **Purpose Grants**: Explicit permission flags determine whether an answer may be used in search indexes, CSV attendee exports, or moderation reviews.

> \[!IMPORTANT] The configured `ExposureLevel` is a strict ceiling. Client UI code and analytics jobs can never widen access beyond what the server authorizes.

***

## Lifecycle: Retirement vs. Hard Purge

1. **Normal Deletion (Retirement)**: Soft-deletes the field definition. Existing event registrations preserve their historical answers for auditability and financial reporting, but no new events can select the retired question.
2. **Hard Purge**: An audited, administrator-confirmed operation that permanently deletes field definitions and scrubs all collected answers from database storage (see [Privacy Erasure & GDPR Compliance](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md)).
3. **Template Immutability**: Editing a registration template never retroactively alters published events or past tickets.

***

## Related Guides & Next Steps

* [**Modular Event Aspects**](/islamu-event/documentation/readme/events-and-ticketing/modular-event-aspects.md) — When to use typed relational aspects vs. custom properties.
* [**Ticketing & Check-In**](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md) — How custom registration questions integrate into ticket checkout.
* [**Google & Microsoft Forms**](/islamu-event/documentation/readme/integrations-and-ai/google-and-microsoft-forms.md) — Map external survey responses into native custom properties.
* [**Privacy Erasure & GDPR**](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md) — Learn how custom property responses are purged upon user 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/custom-properties.md?ask=<question>&goal=<endgoal>
```

`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.