An agency running several client events in the same stretch of the calendar cannot afford to look the same on every one of them. The client is paying for their event to feel like their event, not like a shared platform with someone else's name across the top of it.

The organiser side of the platform is built around that expectation directly: a banner, a logo, a colour scheme and, for agencies, a custom domain, all carrying the client's brand on every guest-facing page, run from one account that keeps each client's event separate from the next.

This is what an agency can set up itself without a developer: banner, logo and colour scheme on the event page, with a custom domain for the client arranged separately. What follows is where the line sits between what a guest sees and what stays the agency's own, from the first link a guest opens to the report handed back to the client afterwards.

Key takeaways
  • Banner, logo and colour scheme are set by the agency itself, per event, with no developer involved; a custom domain for the client is arranged on top of that.
  • One agency account runs every client's event without their branding or guest lists mixing.
  • Team access is granted per event, so a collaborator only sees the one event you gave them.
  • The access mode and branding are locked once an event is published, so decide them with the client beforehand.
  • Attendee lists, CSV export and engagement reporting give an agency something to show the client after the event, not just during it.

What white label actually means here

White label gets used loosely enough elsewhere that it is worth being specific about what it covers on this platform. It is the banner image or video, the logo, the colour scheme, and the event page itself, its name, date, venue and description, reachable by a link or a QR code that never has to mention the agency by name if the client would rather it did not. For an agency, a custom domain sits on top of all of that, so the client's own web address is what a guest actually sees. The agencies page covers the wider picture; this post goes into the branding and access questions specifically.

A handful of client events also want a proper registration step before anyone reaches the gallery. That option exists and carries the same branding as everything else, but it stays switched off by default, so it only appears on the client events that actually asked for it rather than adding a step to every one.

What travels under whose name
ElementWhose brand it carries
Event page: banner, logo, coloursThe client's
Custom domainThe client's, where one has been arranged for the agency account
Access mode and guest sign-inSet per event by the agency, invisible branding-wise to the guest
Attendee and engagement reportingBuilt for the agency to hand to the client
Account login and billingThe agency's, across every client event

One account, many clients, no bleed between them

Running every client from a single login only works if each event genuinely stays separate. Team access is granted per event, so a staff member, or a contact on the client's own marketing team, can be given entry to the one event you actually want them in, not a general pass to every client the agency has ever run.

That separation is what makes running several clients from one account practical instead of risky: nobody sees a gallery, a guest list or a report that is not theirs to see, because access was never granted at the account level in the first place. It also means a second staff member can be brought onto a specific event part-way through a busy week, to help cover a client's event on the day, without that person needing broader access to the agency's other accounts once it is over.

Every guest gets into every client's event the same reliable way, whichever access mode that event uses, open, registration with a one-time email code, a pre-approved list or a PIN, with no password for anyone to set, forget or reset. That mechanic stays identical from client to client even as the banner, logo and colours around it change.

As the roster grows, the same pattern holds. Each new client event gets its own branding, its own access mode and its own set of collaborators, without any of it needing a new account or a separate arrangement with anyone other than the client already on file.

The domain question

A guest who lands on a generic web address for what is supposed to be their own company's event notices, even if they could not say exactly why it feels off. A custom domain removes that moment entirely: the event page, the sign-in step and the gallery all sit under the client's own address instead of a shared one, carrying a guest through the whole journey without dropping back to a generic address part-way through.

This is arranged per event, so one client's gallery can run on their own domain while a different client's runs on theirs, both handled from the same agency account without either client seeing evidence of the other.

The guest should never have to wonder whose event this actually is.

Choosing how guests get in, per client

Not every client wants the same front door. A public conference and a closed client dinner call for different answers, and the platform gives an agency four to choose from for each event: open to anyone with the link, registration first, a pre-approved guest list where adding or removing an address takes effect immediately, or a PIN of four to eight digits.

Registration, one of the four, is often the natural fit for a client who wants a guest list out of the event as well as photos, since it collects guest details before anyone reaches the gallery, feeding straight into the attendee list and export covered further down. A closed client dinner might prefer a PIN instead, handed out on the invitation itself rather than collected through a form.

The choice is made once, before the event is published, and stays fixed while it is live. Changing it means unpublishing, changing it and publishing again, so this is a decision to make with the client in the planning conversation, not something to improvise once guests are already arriving.

What this replaces for an agency

Some agencies have been stitching this together themselves, either with generic sharing tools that were never built with a client's brand in mind, or with a one-off microsite per event that someone has to build and then maintain. The real cost of the first approach is usually staff time nobody accounted for, and the second does not scale past a handful of clients.

An agency already running client events on another platform and finding it does not stretch to proper branding is not starting from nothing either. Moving platforms without breaking guest access already out in the world is a bounded piece of work, not a rebuild.

For agencies still comparing options, the questions worth asking of any platform, not just this one, are covered in a separate guide to evaluating them, and it is worth reading before signing anything, whichever platform ends up being the answer.

What a guest actually experiences

None of the branding matters if the steps in between feel like a different company took over half-way through. A guest opens the client's own domain, sees the client's banner, logo and colours on the event page, verifies their email with a one-time code if that is how the event is set up, and reaches a gallery that still looks like the same event they were invited to. At no point does a generic name or a different set of colours interrupt that.

That consistency is what a custom domain and consistent branding are actually buying an agency: not a cosmetic detail, but a guest experience a client can look at start to finish and recognise as their own event, which is worth putting in front of a client who is deciding whether to book the agency again.

Proving the value to the client afterwards

A retainer gets renewed when an agency can show what it delivered, not just describe it. Attendee lists and CSV export, engagement reporting and sponsor visibility reporting turn a gallery the client already liked into a set of numbers an agency can put in front of them at the renewal conversation.

For a client event carrying its own sponsors, a trade show stand, a conference track, a product launch, sponsor visibility reporting adds a second, separate case for the same renewal conversation, without any extra setup beyond the branding the event already needed.

That reporting is exactly the argument covered in turning photo delivery into something a client renews over, and it sits on the same account as the branding, so nothing extra has to be assembled by hand after the event is over.

Starting with one client, not the whole roster

None of this needs to be decided for every client at once. The free plan covers 300 photos a month across unlimited events, with no card required, which is enough to run one real client event through the whole setup, branding, access mode and reporting, before deciding whether it is right for the rest of the roster. There is no obligation to move every client across at once, or at all, if only some of them need this level of branding.

Start a free event with the next client on the calendar, or see the full plan details and book a walkthrough if there is a specific client brief worth talking through first.

Frequently asked questions

Can each client's event use a different domain?
Yes. A custom domain can be arranged per event, so one client's gallery can sit on their own domain while another client's sits on a different one, all from the same agency account.
Do I need a developer to set up a client's branding?
No. Banner, logo and colour scheme are things you set from the organiser side yourself. A custom domain doesn't need a developer either. It's arranged for the event rather than built as a one-off site.
Can a client's own staff get into their event without seeing our other clients?
Yes. Team access is granted per event, so a collaborator you add only sees the event you gave them access to, not the rest of the account.
Can we change the access mode after a client's guest list has already registered?
Not while the event stays published. The mode is fixed once you go live, so decide open, registration, pre-approved or PIN with the client before publishing, then unpublish first if it genuinely needs to change.
Is there a cost to trying this with one client event first?
No. The free plan covers unlimited events with no card required, which is enough to run one real client event before deciding on anything bigger.
Share WhatsApp LinkedIn X

Try the free plan with your own photos

Create a free account, upload photos from your last event and test the selfie search yourself. 300 photos a month, unlimited events, no credit card.

Start freeBook a demo

Free plan · 300 photos a month · unlimited events · no credit card needed