A small team behind the collection
Give two trusted helpers a clear wedding collection job
You can hand somebody a table sign without giving them your account. Wedding photo sharing with extra managers is for the different situation: a trusted helper genuinely needs dashboard access while you are getting married. Keepsake includes two extra managers alongside the event owner, with access you can change or remove.

Decide whether the helper needs the dashboard
Start with the job, not the invitation button. A friend who reminds tables about the QR code can do that without administrative access. A relative who contributes photographs uses the guest page like anyone else. Manager access becomes useful when someone must inspect the collection or make permitted changes while the owner is busy. Keeping these activities separate prevents a simple request for help from becoming an unnecessarily broad invitation into your event.
Help that needs no manager seat
- Place the printed upload instructions, check that the code scans and point guests towards the correct address. None of this requires seeing the host dashboard or learning its settings.
- Explain the upload process on a guest's own phone, with their permission. The guest selects the files and contributes without registering; the helper does not need to act as the owner.
- Send a reminder through a family conversation you already use. Agree the wording and deadline with the couple instead of assuming that access to the collection is necessary.
Help that can justify access
- Look through incoming contributions from the event workspace and report a missing batch. Decide whether viewing alone is sufficient before granting the ability to change anything.
- Carry out agreed collection tasks when the owner is unavailable. A helper making changes needs the appropriate edit access, a clear brief and a way to escalate an uncertain decision.
- Cover a planned period after the reception, such as checking that contributions arrived. Arrange the end of the assignment at the same time as its beginning.
Read the two access labels literally
The collaborator controls offer View only and Can edit. These are broad access choices, not a menu of custom wedding jobs. A rota saying that one person handles photographs and another handles settings is an agreement between people; it does not create technical boundaries inside the software. Choose somebody you trust with the actual access granted, even if the task you ask them to perform is much narrower.
- View only
- This lets a collaborator browse uploads, guestbook entries and statistics without changing them. It suits someone checking whether expected contributions have arrived or reporting what needs attention. It is not a hidden editing role, and you should not assign actions to that person which require altering the collection.
- Can edit
- This permits moderating uploads, editing the guestbook and changing event settings. Give it to someone whose judgement you trust, not merely someone who is comfortable with a phone. There is no separate promise here of a photographs-only editor, a guestbook-only editor or a settings-excluded editor.
- Owner responsibilities
- The owner invites collaborators, changes their access and removes them. Collaborators cannot invite other collaborators or delete the event. Keep the owner's account under the owner's control rather than sharing credentials to imitate an extra seat or avoid choosing the appropriate access level.
Price the seats as part of one event
Keepsake costs USD 69 once per event and includes two extra managers, 2,000 photos, 300 videos, 50 GB and six months online. It also includes original-quality downloads, written and video guestbooks and a slideshow. The two seats are additional to the host, not a promise that an unlimited team can administer the collection. A helper contributing as a guest is a different matter from a person occupying a manager seat.
Do not budget seats on another package
Preview, Gather and Celebrate do not include extra managers. If shared administration is essential, make the package decision before asking helpers to depend on access. Do not plan around an imaginary single-seat purchase or assume a guest link opens an administrative workspace.
Do not confuse contributors with managers
Paid plans have no contributor-number ceiling, but their file counts and storage remain finite. Two managers does not mean only two people can send wedding pictures. Equally, many contributors does not mean they can all edit the event: contribution and administration are different activities.
Do not buy more organisation than you need
If the owner can handle the dashboard and the helpers only explain the QR code, choose capacity on its own merits. Extra access is useful when it solves a real scheduling problem. A small, well-briefed collection can run without turning the whole wedding party into administrators.
Invite early enough to practise the actual work
Send collaborator invitations before the wedding-day rush, but check that they are accepted rather than treating a sent message as completed setup. An invitation expires after seven days. The collaborator list distinguishes an invitation from active access, which gives you a concrete thing to verify. Administrative access uses the invitation and account flow; the account-free promise is for guests uploading, not for people joining the management workspace.
Confirm the address privately
Ask which email address the helper will use, check its spelling and explain why you are inviting them. Do not publish an administrative invitation in the same group message as the guest upload link. Those two addresses serve different purposes and should travel separately.
Select the access the task requires
Use View only if the job is observation and reporting. Choose Can edit when the helper must make agreed changes. Explain the breadth of edit access before sending, so the helper understands that being able to change a setting is not an instruction to change it.
Confirm acceptance and do a small rehearsal
Ask the helper to open the correct event and locate a test contribution. For an editing job, practise a harmless agreed action before the event, then check the result together. A successful invitation says little about whether the person understands your collection policy.
Resolve an expired invitation before the event
If the invitation has expired, arrange a fresh one rather than lending the owner's password. Keep the list tidy when someone is no longer helping. Pending invitations also occupy seats, so an unanswered invitation can matter when you try to invite a replacement.
Write a human brief for decisions software cannot make
Your helpers can recognise an obvious test image, but they cannot infer every family boundary. Brief them on what you want collected, what must wait for your decision and who can answer a question when you are unavailable. Do this in a short message you already share, not as an invented workflow feature. A written agreement is especially helpful when two people have edit access and might otherwise apply different standards.
- Routine decisions
- Describe the ordinary material you welcome: candid conversations, room details and pictures people knowingly posed for. If approval is switched on, explain what the helper may accept without consulting you. Use examples of content categories, not a list of relatives whose photographs should automatically be treated differently.
- Pause and ask
- Identify sensitive categories such as children, visible personal documents, embarrassing moments or photographs that someone has asked you not to share. Ask helpers to leave uncertain decisions for you rather than guessing. Permission to edit is not permission to settle a family disagreement on your behalf.
- Settings and addresses
- Agree that the invitation wording, guest gallery visibility and collection instructions will not be changed casually during the reception. If a change is genuinely necessary, tell the other helper. Two people independently fixing the same problem can leave the guest experience different from the printed promise.
- Personal copies
- Discuss whether any helper should keep a downloaded copy and, if so, where it belongs afterwards. Access to the working collection does not automatically make that person the family archivist. Treat copies outside the event as a separate responsibility that requires a clear agreement.
Use a handover rather than simultaneous guesswork
Two helpers are useful when they cover different moments, not when both assume the other is watching. Build a light rota around the wedding itself. Nobody should miss a ceremony because they were informally made responsible for a queue. Choose short checking windows and one person responsible at a time. The rota is your planning arrangement, not a scheduled assignment system inside the product.
Before arrivals
The setup check
The first helper verifies the printed code, guest instructions and expected viewing behaviour with the owner. They report whether the test worked, rather than redesigning the collection. Keep any test files recognisable so they are not mistaken for wedding contributions later.
During a natural break
The agreed review window
An editing helper can check incoming material during a pause if that is their assigned task. They should not feel responsible for instant decisions throughout the ceremony or meal. Tell guests that some contributions may take time to appear when approval is enabled.
At the shift change
The three-line handover
Send the next helper a plain message saying what was checked, what remains uncertain and whether any setting changed. This is enough to prevent duplicated work without inventing a formal task queue. Mention anything that needs the owner's judgement rather than passing it silently along.
After the reception
Return attention to the owner
Summarise outstanding contributions and any questions from guests. The owner can decide on later reminders, downloads and access removal when the immediate celebrations are over. A clean handover means the helper does not remain informally responsible for months.
Keep visibility decisions separate from staffing
Adding a manager does not decide who can browse the guest gallery. The host's gallery-visibility setting controls that experience, and the approval switch determines whether submissions wait for acceptance. These are separate questions. A helper with edit access needs to understand both so that a quiet collection is not mistaken for a broken one, or an upload-only page is not reopened merely because a guest asks where the pictures are.
An unlisted link is not a verified guest list
Do not tell helpers that the guest address authenticates everybody visiting it. Unlisted is not the same as authenticated private access, and a recipient can forward a link. Keep administrative invitations out of guest messages, share the guest address deliberately and make any request not to forward it an honest social request rather than a claimed technical guarantee.
- Tell the helpers whether guests should currently see a gallery or only an upload page, and make the welcome message match that choice.
- Explain what approval means for new contributions and who should handle an uncertain image. Do not use manager access as a substitute for an agreed review policy.
- If a slideshow is being used, assign responsibility for the screen separately from responsibility for the incoming collection. The two jobs can have different timings.
- Ask helpers to report sensitive content privately. Describing the problem in a large wedding group can expose the very material you were trying to keep out of view.
End the assignment as deliberately as you began it
A wedding helper's job should not drift into indefinite access. Choose a handover point: perhaps after checking the last expected contributions or after the owner has made the archive. The owner can change access or remove a collaborator in the collaborator controls. Removing access is not the same as deleting a copy somebody previously saved, so address those copies directly in your agreement.
Collect unresolved questions
Ask each helper to send any outstanding issues before their role ends. Include missing contributions and decisions they deliberately left untouched. Do not rely on remembering a conversation held while clearing tables or travelling home; a short written handover is easier to act on later.
Check the owner's copy
Download the collection before its expiry and open representative files to verify the archive. Keepsake includes original-quality downloads and six months online. If you need longer online access, extensions cost USD 9 for six more months or USD 15 for twelve, starting at the existing expiry.
Review and remove access
Remove collaborators who have finished, or reduce an editor to viewing if a remaining task genuinely needs that access. Confirm the new arrangement with them. Thanking someone for their work and closing the administrative assignment are compatible parts of the same handover.
Questions to settle before choosing your helpers
Can one helper edit only the guestbook?
The current controls offer View only and Can edit, not custom permissions for individual areas. You can agree that a helper works only on the guestbook, but that agreement does not narrow the technical scope of edit access.
Can a collaborator invite a substitute?
No. The event owner manages collaborator invitations and access. Ask a helper to contact the owner if they can no longer cover the agreed time rather than forwarding an administrative invitation.
Do ordinary guests use the two manager seats?
No. Guests contribute through the guest page without an account. Manager seats are for invited access to the event workspace, not a count of the people who send photographs.
Should both helpers get edit access?
Only if both need to make changes and you trust them with that scope. A person who is checking arrivals and reporting problems may need only viewing access, while someone distributing printed codes may need no seat at all.
Choose the people, then define their access
Write down the two jobs you need covered, the decisions that stay with you and the date the assignment ends. If those jobs need shared administration, choose Keepsake and invite your helpers early enough to rehearse. Keep the guest upload link simple and the owner account yours.
How it works
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.