Run several events at once
One account can hold as many events as you like, each getting its own code, album, plan and retention window. Nothing is shared together.
The two things that fail are printing the wrong code and assuming a plan spans each 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 plus its own window. Nothing transfers over: upgrading 1 event doesn't upgrade another, and closing uploads on 1 leaves the rest open.
That's what makes an account workable for somebody running events for other folks, and it's also the source of both usual mistakes.
- Name events so you can tell them apart. The name shows up 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's no subscription spanning everything you run. You purchase for a specific event, and a second event starts on the free tier however much you paid for the first. The invoice matches the purchase instead of the account.
So check the plan on each event before its party, not just 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 lives with the event. Almost nothing is shared.
Keeping the codes apart
The exported files carry the event name already, which helps provided you don't rename them generically en route to the printer. Remove last season s files from the folder you print from, and print 1 sign for each event to scan before the run.
A code that opens the wrong album is an older file, not a bug — and the only fix once printed is reprinting.
Archiving what is done
Archiving pulls an event out of your active list without touching the album, files and window. It's housekeeping instead of an ending, and it's what keeps a list of 30 events readable.
Removing is the other thing fully: it takes the event and its contributions with it, and there's no undo.
Every event expires on its own clock
The window tracks each event's own date, so events created on the same day may expire months apart. Warning emails go off 14 days, 3 days and 1 day before removal, for each event.
With a few running, those warnings deserve watching. Download each album while it's still there.
When they are not your own parties
If you run events for other folks, the question halts being organization and turns into whose name is on the sign. Placing your own brand, colors and domain before a client s guests is what the business plans are for.
The watermark on a guest page already lifts with the first paid tier; the rest goes further.
Common questions
Does 1 plan cover all my events?
No. A plan lives with 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 drops the event off your active list without touching the album or the files.
Do all my events expire together?
No. Each runs solo date, so they may expire months apart.
How do I avoid printing the wrong code?
Grab it from the event itself and scan one printed sign first.
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
Forward us the event name or its code. We will show you which album it belongs to.