Archiving and cloning templates
Updated June 29, 2026
As you build more templates, two bits of housekeeping keep your designer manageable: cloning to make variants, and archiving to hide ones you're done with.
Cloning a template
Cloning makes a full, independent copy of an existing template. It's the right move when you want a variant without rebuilding from scratch, for example:
- a summer and a winter version of the same loyalty card, or
- a VIP and a general-admission version of an event ticket.
The clone is a deep copy. Edit it freely; the original is untouched.
Archiving a template
Archiving hides a template from your designer without deleting it. Use it for templates you've finished with, like last year's event, so your list shows only what's current.
Archiving is safe:
- It doesn't affect passes already issued from that template. Those keep working and keep updating.
- The template stays on record, so its history is preserved.
Archiving is about tidiness, not cancellation. To stop an individual pass from being valid, void the pass instead. Archiving the template it came from doesn't invalidate passes already out there.
A simple workflow
- Build new variants by cloning, not by editing a live template in ways that might surprise passes already issued from it.
- Archive templates once their campaign or season is over.
- Keep the active list short so the template you need is always easy to find.