Run several events at once
One account can hold as many events as you like, each with its own code, album, plan and retention window. Nothing is shared between them.
The 2 things that go wrong are printing the wrong code and assuming a plan covers every event. Both are cheap to avoid and expensive to discover late.
Events are entirely independent
Each event has its own code, its own album, its own plan and its own retention window. Nothing carries across: upgrading 1 event does not upgrade another, and closing uploads on 1 leaves the rest open.
That is what makes an account workable for somebody running events for other people, and it is also the source of both usual mistakes.
- Name events so you can tell them apart. The name appears on the guest page and in the exported archive.
- Take each code from its own event. Print 1 sign per event and scan it before the run.
- Archive what is finished. It leaves the list without touching the album or the files.
A plan belongs to an event
There is no subscription covering everything you run. You buy for a specific event, and a second event starts on the free tier however much you spent on the first. The invoice matches the purchase rather than the account.
So check the plan on each event before its party, not once at the start of the season.
| Belongs to | Examples |
|---|---|
| The event | Code, album, plan, storage, retention, guest-page language, styling |
| The account | Your name, dashboard language, signed-in devices, billing details |
Almost everything that matters during a party belongs to the event. Almost nothing is shared.
Keeping the codes apart
The exported files carry the event name already, which helps as long as you do not rename them to something generic on the way to the printer. Delete last season s files from the folder you print from, and print 1 sign per event to scan before the run.
A code that opens the wrong album is an older file, not a fault — and the only cure once printed is reprinting.
Archiving what is done
Archiving takes an event out of your active list without touching the album, the files or the retention window. It is housekeeping rather than an ending, and it is what keeps a list of 30 events readable.
Deleting is the other thing entirely: it takes the event and its contributions with it, and there is no undo.
Every event expires on its own clock
The window runs from each event s own date, so events created on the same day can expire months apart. Warning emails go out 14 days, 3 days and 1 day before removal, per event.
With several running, those warnings are the thing to watch. Download each album while it is still there.
When they are not your own parties
If you run events for other people, the question stops being organisation and becomes whose name is on the sign. Putting your own brand, colours and domain in front of a client s guests is what the business plans are for.
The watermark on a guest page already disappears with the first paid tier; the rest is a step above that.
Common questions
Does 1 plan cover all my events?
No. A plan belongs to an event, and a new event starts on the free tier.
Can events share an album?
No. Each event has its own album and its own code.
What does archiving do?
It removes the event from your active list without touching the album or the files.
Do all my events expire together?
No. Each runs on its own date, so they can expire months apart.
How do I avoid printing the wrong code?
Take it from the event itself and scan 1 printed sign before the run.
Still open? Contact
The QR code opens the wrong page
What happens when an older code goes to print.
When to create it, how long it collects
Why each event expires on its own clock.
Update your profile and language
What belongs to the account rather than an event.
A guest album for a company event
Several events a year, kept apart.
You have lost track of an event
Send us the event name or its code. We will tell you which album it belongs to.