The link reached the wrong people
Access belongs to the link, not to a person, so a forwarded link works for whoever receives it. Closing the upload window stops contributions immediately and invalidates the links guests were using.
Making the album private stops viewing. Neither undoes what somebody has already seen or saved.
How access actually works
There is no guest list. Anyone holding the link can open the page and contribute, which is what makes the whole thing work at a party and also what makes a forward effective. The page itself even offers guests the link to pass on after they upload.
So the question is never who was invited. It is who currently holds the link.
- Close uploads first. It takes effect at once and revokes the links already in circulation.
- Make the album private. The link then shows nothing at all, to everyone.
- Reopen deliberately. A password in front of viewing lets you go back to open without going back to public.
Closing uploads
This is the first lever and the fastest. Contributions stop at once, and the tokens guests were using to send are revoked — so a page somebody already had open stops working rather than continuing quietly. Viewing is unaffected.
Reopening restores it for everyone. It is a tap, not a decision you are stuck with.
| Lever | Stops uploading | Stops viewing | Reversible |
|---|---|---|---|
| Close uploads | Yes, immediately | No | Yes |
| Make album private | No | Yes, entirely | Yes |
| Set a viewing password | No | For anyone without it | Yes |
| Delete a contribution | No | That item only | No |
None of these reaches a copy somebody already saved. That is the limit of what any switch can do.
Making the album private
This stops viewing for everyone holding the link, invited or not, and the page then shows nothing at all. It is the blunt option, and it is the right one while you work out what to do next.
Tell your actual guests you have done it, or they will report the album as broken.
The password as a middle option
A viewing password lets you reopen the album to the people you choose without making it public again. Everyone types it once, and you give it out through a channel the wrong recipients do not have.
It needs at least 8 characters and it is separate from the download password, which gates taking the files.
What none of it undoes
Anything already viewed has been viewed, and anything already downloaded is on somebody s device. No switch reaches those. Deleting a contribution removes it from your album and from every future download, which is the most any platform can do.
Being clear about that is better than implying otherwise. A host who thinks a switch recalls a copy plans badly.
Setting it up so this is less likely
For anything semi-public, decide before the link goes out: a viewing password from the start, guest downloads left off, and review-first so nothing appears unseen. All 3 are cheaper to switch on beforehand than to retrofit.
For a private party among invited guests, an open link is the right call. The forwarding risk is real but small, and every barrier costs contributions.
Common questions
Can I revoke access for 1 person?
No. There is no guest list, so the levers apply to everyone holding the link.
Does closing uploads also hide the album?
No. Viewing is a separate switch.
Do links guests already have stop working?
For uploading, yes — closing the window revokes them immediately.
Can I get back something somebody downloaded?
No. Deleting removes it from the album and future downloads, not from their device.
What is the least disruptive option?
A viewing password. The album stays reachable for the people you give it to.
Still open? Contact
Publish or hide the album
The 3 visibility states in detail.
Hide or delete uploads
Removing a single contribution for good.
Do guests need an account?
Why access belongs to the link.
A guest album for a company event
Set the barriers before the link goes out.
You need to act quickly
Close uploads and make the album private, then write to us with the album name. We will help from there.