Where templates live
Settings → Modules → Events → Templates. Creating, editing, and deleting templates requires the Orgo administrator flag on your account, not only an admin permission. Templates belong to the whole organization, not to a group or local center.
Two ways to create one
1
Build it from scratch
Settings → Modules → Events → Templates → Create Template.
2
Or save an existing event as a template
Open any event, then choose Save as Template from the Actions menu in the event header and give it a name. This copies the event’s settings, its cover image, its live ticket types (skipping archived ones), its vouchers, its custom registration fields, and its agenda sessions. Requires the Orgo administrator flag.Two limits to know: ticket add-ons and the membership level or chapter lists on a ticket are not copied this way, so re-add them in the template editor. Agenda sessions are stored as a day number counted from the event’s start date plus a start and end time; a session that starts before the event’s start date is left out, and a template holds at most 200 sessions.
What a template stores
The editor has two tabs, General settings and Agenda.
A template deliberately does not carry the event’s dates, the hosting group, attendees, or speakers. Those are decided per event. Agenda sessions are the exception to “no dates”: they are kept as day offsets and times and re-dated when you pick the event’s start date.
Registration form
This card appears once the template requires a registration form or is Paid. The Form fields tab is a drag-and-drop builder. Standard fields available: Email and Name (always required), plus Phone, Organisation, Role, Town, LinkedIn, X (Twitter), Instagram, Company Identifier, Company Name, and Company Address. You can also define custom fields with a name and a type: text input, text area, dropdown, radio, checkboxes, date, or yes/no. Dropdown, radio, and checkbox fields need at least two options. See Registration Forms for what each field does. The Settings tab holds Disable newsletter subscription, Disable register checkbox, and Custom text at bottom of registration form (shown above the consent checkboxes). The Styling tab holds Display title, Selected color, Button color and Hero image border radius.Tickets, add-ons and vouchers
When Access is Paid, the template shows the same Ticket types, Add-ons and Vouchers lists as an event’s Tickets page, with the same editors, working on the template’s draft copies. A ticket carries a name, price, description, who can buy it (Everyone, All members or Specific members by level or chapter) and a seat count; there is no sales window on a template, because a template has no dates. Add-ons carry a name, price, which tickets they are offered with, a per-ticket limit, a total and Adds a separate attendee. Vouchers carry a code, a percentage or fixed discount, Never more than, Tickets per order, Max orders, Active and an optional restriction to ticket types. Ticket links and invitations are not part of a template. See Ticketing for what each of those does at checkout.Agenda
The Agenda tab builds the event’s schedule ahead of time. “Days count from the event start date; times are in the event timezone.” Use Add session to add sessions, and the pencil and bin icons on each row to edit or delete one. Sessions with stage colours show them in the list, and you can filter by stage.Using a template
On the events list, select Create an event. When your organization has at least one template, a Start from template button appears in the action bar of the create form. It lists up to five templates, followed by Start without a template (once one is chosen) and Browse all templates.
Template management is admin-only, but the picker itself works for any organizer who can create an event. That is the point: admins curate the setups, everyone else uses them.
Common questions
I changed a template. Do existing events change too?
I changed a template. Do existing events change too?
No. A template is applied once, at creation. Events created earlier keep whatever they had.
A template or a duplicate: which should I use?
A template or a duplicate: which should I use?
Duplicate copies one specific event, including its group and its agenda, and is quickest for “same event, new date”. A template is the right tool when several people create similar events and you want a consistent starting point without them hunting for last year’s event.
Can a template set the hosting group?
Can a template set the hosting group?
No. The group is always chosen on the event form, because it decides who sees the event and which permissions apply.
Why does a paid template force the registration form on?
Why does a paid template force the registration form on?
Ticket buyers have to supply at least a name and email to receive a ticket, so paid events always collect a form. The toggle is shown but locked.
Related
- Create Event - the form a template pre-fills
- Event Types and Statuses - the type a template can default to
- Ticketing - ticket types, vouchers, and checkout
- Registration forms - the per-event form builder
- Events overview - module settings and the event workspace

