Control When Your Event Photos Are Revealed to Guests

Yes: you decide when an event's photos become visible to guests, and there is more than one way to do it. The whole gallery can stay unpublished until you switch it on or until a time you set in advance. Inside a published gallery, an individual album can stay private to you or sit behind a PIN so only guests you have told can open it. If guests are contributing their own photos, each one can wait for your approval before it appears anywhere at all.

None of this is a workaround. It is how the platform is built: an event exists in a state you control from the moment you create it, and nothing on the guest-facing page shows a photo until you decide it should. That is what a corporate retreat needs while comms reviews what came out of a candid session, what a gala needs when a client wants first sight of the gallery, and what a wedding needs when the couple would rather see their own photos before three hundred guests do.

The rest of this guide goes through each control in turn: publishing the whole gallery on a switch or a schedule, holding back one album inside it, approving guest uploads before they go live, and deciding who can reach the event page at all before any of that even comes into play.

Why this needs to be your decision, not an accident

Photos from an event rarely stay contained to the people who were actually there. A guest posts one to their own feed before your official recap goes out, a colleague forwards an internal shot to someone who was never meant to see it, or a couple finds their own wedding photos have already done the rounds of a family group chat before they have chosen a single one to keep. None of that is really about the photos. It is about nobody having decided, in advance, when they were supposed to become visible in the first place.

Eventiere treats that as a setting rather than something to police after the fact. An event exists in a state you control from the moment you create it, and every layer covered below, publishing, album visibility, guest upload approval and who can reach the page at all, is set before anyone sees anything, not negotiated once photos are already circulating.

The gallery stays closed until you publish it

Every event you create sits unpublished from the moment it exists to the moment you decide otherwise. While it is off, the gallery does not open for anyone, including a guest who already has the link or the QR code from your invitation. Photos can be uploaded, sorted into albums and checked over in private the whole time, so uploading has never had to wait for photos to be ready to show.

There are two ways to publish, and neither happens by accident. You can flip the switch yourself the moment you are actually ready, or set a specific date and time in advance and let the event go live on its own. Scheduling ahead is the simplest way to delay sharing event photos without relying on remembering to do it in the middle of a busy day, and it suits a product launch with an embargo, a gala where the client wants first sight of the gallery, or a wedding where the couple would rather see their own photos before anyone else does.

• A switch, flipped the moment you are actually ready
• A scheduled date and time, so the event goes live on its own

Holding one album back while the rest of the gallery is open

Publishing the whole event is a blunt instrument next to what an album lets you do on its own. Inside a published gallery, an album is set to one of three states when it is created: public, so every guest can browse it; private, visible to you alone and never served to a guest under any circumstance; or secret, which stays out of the guest-facing album list entirely until someone enters the PIN you set for it.

A private album suits anything that should simply never reach a guest: shots from a walkthrough, a set you are still deciding whether to use at all. A secret album is for something you do want a specific group to eventually see, a leadership-only set from a retreat, family-only portraits from a wedding, a sponsor's own coverage, revealed by handing out the PIN whenever and to whoever you choose, independently of when the rest of the gallery went live.

This choice is made once, when the album is created, because changing it later causes its own problem in either direction. Turning a public album secret after guests have already browsed it does not un-show anyone what they have seen, and turning a private album public exposes it to everyone with the link at once, with no gradual reveal. Deciding the state up front avoids both.

Guest photos: instant, or only after you say so

Publishing controls your own photos. Guest uploads are a separate setting, because a gallery of your own photography and a gallery anyone at the event can add to are different kinds of risk. With guest uploads on and approval left off, a guest's photo appears the moment they upload it, which suits a relaxed event where the only real risk is a duplicate or a blurred shot.

Turning approval on changes that. An uploaded photo sits aside until you or a collaborator looks at it, and only an approved photo ever reaches the gallery or a screen at the venue. A rejected one never reaches the gallery at all, and it was never visible to another guest at any point in between. This is worth switching on for a work event where a candid could be the wrong candid, or a wedding with more relatives holding cameras than the couple can reasonably vet themselves.

A different question: who can reach the page at all

Everything above controls what is visible once someone has actually reached your event page. A separate setting controls whether they reach it in the first place. An event can be open to anyone with the link or the QR code, ask for registration with an email and a one-time code before anything past the page loads, restrict entry to a pre-approved list of addresses you maintain yourself, or sit behind an event PIN of four to eight digits.

These two layers work together rather than instead of each other. A registration-only event with a private planning album inside it means an outsider cannot even reach the page, and even a registered guest cannot reach the one album you have kept back. All four access modes, whether the event is a corporate day or a public launch, are set up from the same event screens covered on the features page.

The access mode is decided before you publish and stays fixed while the event is live, the same way an album's state is fixed at creation. Changing it once guests are already arriving means unpublishing the event, changing the setting, and publishing again, so it is worth agreeing on with anyone else involved, a client, a comms team, a co-planner, before the event goes live rather than after.

What a guest actually sees before anything is revealed

A guest holding a link or a QR code before you have published anything does not see a gallery slowly filling up. The event simply is not open yet, whichever way they try to reach it, so there is no risk of an unfinished album or a half-checked guest upload reaching anyone by accident.

An event protected by a PIN behaves slightly differently, and it is worth knowing the distinction. The event page itself, its name, date, venue and banner, is shown to anyone with the link, so a guest can confirm they have the right event before doing anything else. It is the photos that stay behind the PIN, not the page's existence. That is deliberate: a guest needs something to recognise before they will bother typing a code in.

The same logic applies at a smaller scale to a secret album inside an otherwise open gallery. It does not appear in the list of albums a guest can browse until the correct PIN is entered for it, at which point it opens like any other.

Putting the controls together

A corporate retreat is a reasonably typical case for combining several of these at once. Registration is switched on so only people who actually work there, or were invited, can reach the page. The whole event stays unpublished while comms reviews what came out of the more candid sessions, and a private album holds anything that will never go beyond an internal debrief. Once comms has signed off, the event is published on a schedule set for the following Monday morning, so it goes live for every attendee at the same moment rather than trickling out over a weekend nobody is checking email.

A wedding usually needs a lighter version of the same idea. The couple wants first sight of their own photographs, so the event stays unpublished until they have had a look, then goes live with a single switch once they are ready to share. A guest album stays open to uploads with approval switched on, so a hundred phones contributing candids does not mean a hundred unreviewed photos reaching grandparents in real time. A separate secret album, shared only with the wedding party by PIN, holds getting-ready shots nobody else needs to see.

Deciding this before your first guest has a link

Every control in this guide, publish timing, album state, upload approval and access mode, lives on the same event setup screens, covered in full on the features page. None of it has to be decided all at once on day one. What matters is agreeing the sequence, who reviews what, and when the switch actually gets flipped, before your first guest has a link in hand rather than after.

It costs nothing to test the whole sequence on a real event. You can start on the free plan, detailed on the pricing page, unlimited events and 300 photos a month with no card required, and try the whole sequence on a real event before deciding on anything bigger.