Guests: finding, deleting, downloading
A guest locates the album again through the link the page shows for copying after sending, or via the table code. Downloading works only if you have opened it for the album.
Removing their own contribution isn't something they can do. Without an account there's no private space for it — only you can remove it from the dashboard.
Finding the album again
After sending, the guest page shows a prompt to keep the link: copy it, or save it through the phone s share sheet. That's the only route back, since without an account there's no list of albums visited. Anybody who misses it locates the album again through the code on the table.
Say that one sentence as you set out the cards. It saves you the question the next day about where the photos went.
- Save the link. Right after sending the page shows for copying or share it. That's the route back.
- View the album. The link leads to the shared album, provided you have opened it and no password appears in front.
- Ask for a deletion. Anybody wanting something withdrawn requests the hosts. The remove function rests with you.
What a guest may see
The shared album shows contributions that passed review. You may fully close the album, in which case the link leads nowhere, and you can add a password to it that each viewer types once. Both are your switches, not the guest s.
With the review step running, a guest spots their own contribution only after you approve it. That isn't a fault; it's the purpose of the review.
Downloading, for guests
Guest downloads are off out of the box. Turn them on and anybody with the album link can take the photos in bulk; optionally you set a separate password that covers downloads only. Viewing is left open while taking things home carries an extra step.
On the free tier there's no package to download. Guests get the single-file route there.
Withdrawing a contribution
A guest can't remove their own upload. That's the other side of a route without sign-in: without an account no one can prove a contribution is theirs. Deletion therefore runs through you on the dashboard.
Take those requests seriously and act swiftly. A guest who doesn't know who to request sends nothing next time.
Hiding instead of deleting
You don't need to remove something to pull it from the shared album. An approved contribution can just be hidden: it disappears for guests, remains yours, and can be brought back later. For a blurred photo or a duplicate that's the calmer route.
When somebody explicitly requests for deletion, though, hiding isn't what they meant. Then remove it properly.
What to tell your guests
2 notes are enough. First: keep the link with you, or you won't locate the album again. Second: to remove something tell us — both fit a table card and answer the questions that would otherwise arrive the next day.
If you open downloads, mention that too — otherwise no one knows they're allowed to take the photos.
Common questions
How does a guest find the album later?
Through the link the page shows for copying after sending, or through the code on site.
Can a guest delete their own photo?
Not themselves. Without an account there's no private space; you remove it from the dashboard.
May guests download the pictures?
Only if you open downloads for the album. They're off out of the box.
Can I password-protect the download?
Yes. It's separate from its viewing password and applies only to downloading.
Why does a guest not see their contribution?
Either it's still prepping, or it's waiting for your approval, or it's hidden.
Do guests need an account?
Why there is none, and what follows from it.
Guest page, album and live wall
Which of the 3 a guest actually reaches.
Get more guests to join in
The reminder that collects a second round.
A guest album for a wedding
The whole day in 1 place, findable for everyone.
A guest cannot find their picture
Forward us the album name and about when they sent it. That shows us where the contribution is sitting.