Event presets
A preset is the template of a whole party. It stores the complete state of an event: all settings including cloud, mail and print, plus layouts, fonts, graphics, custom AI styles, green screen backgrounds and custom notice pages — but no pictures and no counters. An event created from a preset therefore looks exactly like a copy of an existing event.
| Event | Preset | |
|---|---|---|
| What it is | A running or past party | The template new events are built from |
| Contains pictures | Yes | No |
| Contains counters | Yes | No |
| Contains layouts and graphics | Yes | Yes |
| Contains cloud, mail, print | Yes | Yes |
| Contains the quick settings PIN | Yes | Yes |
| Contains the access code | Yes | No — every event gets its own |
| Contains camera, printer, accounts, licence | No — that belongs to the device | No |
How it is used#
- Set up one event exactly the way it will be needed again — layouts, colours, print rules, sharing.
- Save that state here as a preset and give it a telling name: "Wedding classic", "Company party without cloud", "Trade fair with pay-per-use".
- When creating the next event, choose that preset as the basis in the assistant.
There is no supplied preset. As long as none has been stored, a new event starts empty: it gets the supplied fonts, the supplied layouts are in the first event from the setup onwards, and the first layout of your own is created in the "Layouts" step.
Passing presets on#
Presets can be exported as a package and imported again — handy for putting the same state on a second booth or for keeping a backup. The package contains everything the preset is made of: settings, layouts, fonts and graphics. The identifiers of the template stay out, so an imported preset never points at the cloud album of someone else's party.