Approve, reject and approve in bulk
A queued contribution has 4 possible endings: approve it, reject it, flag it for another look, or approve everything loaded at once.
Approving adds it to the album and onto the live wall. Rejecting keeps it out. Neither removes the file.
The 4 actions
Approve posts the contribution: it shows up in the shared album and, if you run one, on the live wall. Reject bars it from both, while Flag for review marks it for another look without deciding — useful when it's somebody else s call. Approve all wipes everything right now loaded.
None of these removes anything. A rejected contribution is out of sight, not gone.
- Open Moderation. The tab rests on the event. It's empty unless review-first is switched on.
- Work top to bottom. The queue runs in time order. Approving as you go keeps the album filling during the party.
- Use bulk when the room is fine. Approve all wipes everything loaded in 1 action. Read the list first.
| Action | In the album? | Reversible? |
|---|---|---|
| Approve | Yes, and on the live wall | Yes — hide it afterwards |
| Reject | No | Yes — approve it later |
| Flag for review | No, still waiting | Yes — it is not a decision |
| Approve all | Yes, for everything loaded | Yes — hide individually afterwards |
Nothing here removes a file. Removing is a separate action, and it's the only irreversible one.
When bulk approval is right
At a party among invited guests, the queue holds 60 photos from the same room. Reading each one costs you the evening and locates nothing. Scan the thumbnails, and approve all — and hide the 2 blurred ones the following morning.
Approve all spans what's loaded on screen, not all of history. On a long queue you scroll and repeat.
When to go one by one
Given a screen in a public room, or an event where you haven't met every guest. There, bulk approval misses the point of reviewing at all, since the entire point is that nothing reaches the projector unseen.
Also worth slowing down for video: a thumbnail gives you the first frame, not the 40 seconds after it.
What flagging is for
Flag for review shelves a contribution without deciding on it. That's the actual move when the call belongs to somebody else — a couple, a client, an organizer — and you don't want to guess on their behalf.
A flag isn't a rejection, and a flagged item is left out of the album up until somebody determines.
A rhythm that works
Watch the queue every half hour during the party instead of at the finish. Guests who see contributions appearing keep them coming, and a queue emptied in batches never turns into the chore that ruins your evening.
The overview tab shows you how many are waiting, so you don't need to open Moderation to locate out.
After the party
Do a final pass the following morning, when the last arrivals have come in. That's also the moment for the walk-through: hide what's blurred or duplicated, and leave the rest alone.
Perfect curation is seldom what anybody wants from a party album. Completeness is the thing folks come back for.
Common questions
Does rejecting delete the file?
No. It's left out of the album; the file remains yours and can be approved later.
Does Approve all cover the whole queue?
It covers everything right now loaded. On a long queue you scroll and repeat.
What is flagging for?
Shelving something without deciding, when the call belongs to somebody else. It's left out of the album.
Can I undo an approval?
Yes. Hide the contribution afterward; it leaves the shared album and remains yours.
Where do I see how many are waiting?
On the event overview. It says so without you opening Moderation.
Review uploads before they appear
Where the queue comes from in the first place.
Hide or delete uploads
The morning-after pass, and which tool it needs.
Get more guests to join in
Why an album that fills matters more than a perfect one.
A guest album for a wedding
Sixty photos from the same room, and how to handle them.
The queue will not clear
Forward us the album name and about how many are waiting. We will look at where they're stuck.