Event templates: saving and reusing an event's setup

Events → Event templates, and "Save as event template" on an event. Growth plan to save; Scale to share with other organizations. Spec: docs/EVENT_TEMPLATE_FORMAT.md §5–§6.

Who opens it: an organizer about to set up this year's event, or one who has just run one well. What they came to do: start from something that already works instead of a blank event. What must be true when they leave: the event they start from a template is the event the template describes — and nobody's personal details travelled with it.

Saving an event as a template

On an event, Save as event template keeps its whole setup: days and times (as offsets, so it works next year), types, forms, registration forms, check-in points, messages and their templates, rules, checklists, the event page and the organization's terminology, group levels, groups, custom roles and feature flags.

It never keeps people. No registration, contact, ticket, check-in or message is read, so no email address, phone number or name can end up in a template. Links to the organization's own uploaded files become blanks the next importer fills in.

Saving under a code already used adds a new version; the older versions stay in the library.

The library

Three shelves: From EntryWick, Saved by us, and Shared by other organizations (templates saved as "Every organization on EntryWick", which needs the Scale plan). Preview shows what a template sets up and which features it uses; Use opens the import wizard with it chosen. A feature your plan lacks is imported switched off, never refused.

API

POST /v1/events/{event_id}/export-event-template (code, name, visibility) stores the export and returns it; GET /v1/templates/{id} returns the document.