Sharing photos at an event

A shared photo album is the artefact attendees come back to weeks later, and it is the one part of an event app where a single upload can create a real problem. Both facts argue for the same thing: decide the policy first, and staff it.

The three modes

Every shared album is one of these. Choose deliberately.

Mode	Who can add	Who sees it immediately	Right for
Open	Any attendee	Everyone	Internal events, team offsites, communities that already know each other
Moderated	Any attendee	Organizer first, then everyone	Most public conferences
Admin-only	Organizers and the photographer	Everyone	Regulated, clinical, minors, security-sensitive audiences

Open produces the most photos and the most life. It is right when everyone in the album already knows everyone in the room, which is true at an offsite and false at a public conference.

Moderated is the default for a paid, public event. It costs a few minutes per break and removes almost all the risk. The queue is small in practice: most events see tens of uploads, not thousands.

Admin-only is not a lesser mode. For a clinical audience, an event involving minors, or anything with a security dimension, it is the only correct one, and the album is still worth having.

event67 supports all three, and auto-hides a photo once it is reported regardless of mode. That last behaviour matters more than the mode choice, because the failure you must plan for is a photo that was fine when approved and is not fine now.

Write the policy before you launch

One paragraph, in plain words, shown where people upload rather than buried in terms:

Photos you add here are visible to everyone at this event in the event app. We may use them in a post-event summary. We will not use them in advertising. If you want a photo removed, email photos@yourevent.com and we will take it down. Photos stay in the app until [DATE] and are deleted after that.

Five sentences. Each answers a question somebody will otherwise ask you at the worst moment: who sees it, what else you do with it, what you will not do with it, how to get it removed, and how long it lasts.

The sentence people care about most is the third. “We will not use these in advertising” costs you nothing at most conferences and buys real comfort.

Consent, honestly framed

The rules vary by jurisdiction and by the nature of your audience, and this is not legal advice. The operational floor that holds up in most contexts:

• Tell people before, not after. In the registration confirmation, in the app’s first-run screen, and on signage at the entrance.
• Make removal easy and fast. A published address, a named person, and a resolution measured in minutes.
• Do not repurpose without asking. An attendee uploading to a shared album has not agreed to appear on your homepage. If you want that photo for marketing, ask that person.
• Signage at the door. “Photography is taking place at this event” is standard and worth doing even when your album is admin-only, because your photographer is also working.
• Offer a way out. A different lanyard colour for people who prefer not to be photographed is a small, well-understood convention, and it works.

For events involving minors, patients, or anyone whose attendance itself is sensitive, none of the above is sufficient. Use admin-only, brief a photographer, and work to written consent.

Staffing it

Moderation. Whoever runs it needs to be able to approve from a phone, between sessions. Check the queue at each break and once after the evening reception, which is where the uploads cluster.

Takedown. One named person, reachable during and after the event, who can remove a photo in minutes. Publish the address. Remove first and discuss afterwards — the cost of removing a photo that turns out to be fine is zero, and the cost of the reverse is not.

Reports. If your app auto-hides a reported photo, the reported queue is a separate thing to watch. A photo that has been hidden by a report needs a human decision reasonably quickly, because the reporter and the uploader are both waiting.

Getting people to actually add photos

Albums do not fill themselves. Three things reliably work:

1. Seed it. Ten good photos from the first morning, added by you, before you mention it. Nobody wants to be first into an empty album.
2. Ask once, from the stage, at the right moment. After the opening keynote, not during housekeeping. “There’s a shared album in the app — add yours.”
3. Give it a subject. “Photos from the workshop track” produces more uploads than “photos”. A prompt beats an invitation.

What does not work: a QR code on a table tent nobody reads, and a reminder notification on day two asking people to upload photos of day one.

After the event

Say what happens next, and do it. If you promised deletion after ninety days, delete after ninety days. The commitment is only worth something if it is kept.

Give people a way to keep their own. Attendees will want the photo they are in. A full-screen viewer they can save from is enough; you do not need a download-all feature.

Do not migrate the album into marketing. If you want three photos for next year’s site, ask the three people in them.

The five failure modes

A photo of somebody who did not want to be photographed. Solved by moderation plus a fast takedown path, not by policy alone.

A photo of a slide that was not meant to leave the room. Speakers should be told the album exists and asked to say if a slide is not for sharing. One line in the speaker brief covers it.

The album fills with photos of the ceiling. Seed it and prompt it, or moderate lightly and let it be human. Both are fine; drifting into neither is not.

Nobody moderates after the reception. This is when the awkward uploads arrive. Put it on somebody’s card explicitly.

The album outlives its welcome. Set the retention date up front. An event archive with no end date becomes a liability that nobody owns three years later.

Where the album sits next to your other photography

Most conferences have two photographic streams and treat them as one, which causes the problems described above.

The commissioned photographer is producing marketing assets. The shots are staged, the subjects are usually briefed, and the output is destined for next year’s website and the sponsor report. Consent for that use is a separate conversation and should be handled with a release, not with a signage notice.

The shared album is producing memory. It is candid, it is attendee-generated, it is for the people who were there, and it should not quietly become marketing.

Keeping the two separate makes both easier to run. The photographer’s images can go into the album if you want them there, seeded on the first morning, and the album’s images do not go into a campaign without asking the person in them.

Tell your photographer about the album, and tell attendees about the photographer. Two lines at registration and one on the entrance signage covers it.

A third stream is worth naming because it is the one nobody plans for: attendees photographing slides. Speakers should be told the album exists and asked to flag anything not for sharing, on the slide and to you in advance. It is one line in the speaker brief and it prevents the awkward conversation entirely.

Where this fits in the app

A shared album earns its place because it is the part of an event app attendees open after the event is over. Everything else — the schedule, the Q&A, the directory — has a half-life measured in days. Photos have one measured in months, and they are the reason someone opens the app again when you announce next year’s dates.

That is the argument for doing it well rather than doing it at all.