QR Album
Gallery

Approve, reject and approve in bulk

Responsible
Martin Freiwald, Founder
Written
Last checked
Reading time
5 min
Short answer

A queued contribution has 4 possible outcomes: approve it, reject it, flag it for a second look, or approve everything loaded at once.

Approving puts it in the album and on the live wall. Rejecting keeps it out. Neither deletes the file.

The 4 actions

Approve publishes the contribution: it appears in the shared album and, if you are running one, on the live wall. Reject keeps it out of both, while Flag for review marks it for a second look without deciding — useful when it is somebody else s call. Approve all clears everything currently loaded.

None of these deletes anything. A rejected contribution is out of sight, not gone.

  1. Open Moderation. The tab sits on the event. It is empty unless review-first is switched on.
  2. Work top to bottom. The queue is chronological. Approving as you go keeps the album filling during the party.
  3. Use bulk when the room is fine. Approve all clears everything loaded in 1 action. Read the list first.
What each action does
ActionIn the album?Reversible?
ApproveYes, and on the live wallYes — hide it afterwards
RejectNoYes — approve it later
Flag for reviewNo, still waitingYes — it is not a decision
Approve allYes, for everything loadedYes — hide individually afterwards

Nothing here removes a file. Deleting is a separate action, and it is the only irreversible one.

When bulk approval is right

At a party among invited guests, the queue is 60 pictures of the same room. Reading each one costs you the evening and finds nothing. Scan the thumbnails, then approve all — and hide the 2 blurred ones the next morning.

Approve all covers what is loaded on screen, not the entire history. On a long queue you scroll and repeat.

When to go one by one

With a screen in a public room, or an event where you do not know every guest. There, bulk approval defeats the purpose of reviewing at all, since the whole point is that nothing reaches the projector unseen.

Also worth slowing down for video: a thumbnail shows you the first frame, not the 40 seconds after it.

What flagging is for

Flag for review parks a contribution without deciding on it. That is the honest move when the call belongs to somebody else — the couple, the client, the organiser — and you do not want to guess on their behalf.

A flag is not a rejection, and a flagged item stays out of the album until somebody decides.

A rhythm that works

Look at the queue every 30 minutes during the party rather than once at the end. Guests who see contributions appearing keep sending, and a queue emptied in batches never becomes the job that ruins your evening.

The overview tab tells you how many are waiting, so you do not have to open Moderation to find out.

After the party

Do a final pass the next morning, when the last arrivals have come in. That is also the moment for the walk-through: hide what is blurred or duplicated, and leave the rest alone.

Perfect curation is rarely what anyone wants from a party album. Completeness is the thing people come back for.

Common questions

Does rejecting delete the file?

No. It keeps it out of the album; the file stays with you and can be approved later.

Does Approve all cover the whole queue?

It covers everything currently loaded. On a long queue you scroll and repeat.

What is flagging for?

Parking something without deciding, when the call belongs to somebody else. It stays out of the album.

Can I undo an approval?

Yes. Hide the contribution afterwards; it leaves the shared album and stays with you.

Where do I see how many are waiting?

On the event overview. It says so without you opening Moderation.

Still open? Contact

Pass it on
Related articles
Contact

The queue will not clear

Send us the album name and roughly how many are waiting. We will look at where they are stuck.