← Help

Product help

Sneak peeks and final gallery delivery

Product team · Reviewed

Open a gallery’s Sneak peek & full delivery page to prepare a deliberate handoff. A sneak peek contains photographs you choose. A Delivered release captures every current, visible, ready original. Both retain an immutable manifest containing each original’s identity, stored checksum, filename and byte count.

Review the people, photographs and message together

Give each couple, vendor or guest a separate invitation. Choose the whole release or a smaller selection, viewing-only or permitted download sizes, usage terms, expiration and an optional password. Passwords are shared separately and never placed in the email.

Enter the exact expected recipient addresses, select Queue this exact invitation email, and choose a send time in your browser’s local timezone. Review exact release shows the filenames, permissions, subject, business reply address and complete email text for each recipient. Approval freezes those values and creates a private scoped link for that person. Link-only recipients receive no automated message.

Changing a source, recipient, term or reviewed branding before approval requires another preview. Repeating the original approval returns the same release instead of creating more invitations or emails. Existing whole-gallery links keep their existing permissions; a sneak peek does not revoke those links. If the gallery is a draft, explicitly approve publication before releasing anything. That publication also enables existing whole-gallery links according to their current access settings.

Exact originals stay exact

Later uploads do not silently enter an older release. A recipient’s selection is checked against its retained original manifest whenever they open the invitation or request a file. Hidden, replaced, deleted, unfinished or altered originals make that selection unavailable until the studio reviews a new delivery. A smaller recipient selection remains independent of photographs they were never granted.

Current gallery expiration, archive status and access withdrawal also apply. Temporary authorized file URLs expire after one minute. Copies already downloaded cannot be recalled. Retained manifest history does not prevent an explicitly approved original-file deletion; use the studio archive export and your own independent backup for preservation.

Recipients browse up to 100 photographs per page, with page selection and ZIP download preparation. A release supports up to 20,000 originals and 25 recipients. A recipient’s smaller selection supports up to 2,000 files; “all photographs in this release” can include the entire release. The workbench shows the 50 most recent releases and their notices. Download the retained JSON manifest from any displayed release to inspect its original-file checksums and manifest hash.

Workflow milestones and delivery receipts

Delivered means the studio approved its complete collection. Each email separately records queued, provider accepted, delivered, failed, or uncertain. A carrier/provider receipt is required for delivered status. The invitation is a private bearer link, not verification of the recipient’s legal identity.

Email dispatch rechecks current reviewer authority, gallery publication, source integrity, invitation expiry, download settings and recipient suppression. Gallery email opt-outs are respected; this flow does not enroll anyone for marketing. A signed bounce, complaint, failure or suppression stops further gallery mail to the matching gallery contact.

Email, worker and sender activation remain part of the coordinated setup phase. Without configuration or while dispatch is paused, approved messages stay queued. Once activated, the worker checks due notices at least every scheduled minute. A provider attempt keeps its original key, message and first-attempt timestamp. The application retries only within its original 23-hour safe window. An unresolved older attempt requires reconciliation; clicking retry cannot restart that window or invent a new delivery identity.

Cancel an email or withdraw a release

Cancel pending email stops an unsent notice and leaves its invitation available. Withdraw release and its invitations disables all private invitations created for that release and cancels pending notices. Original manifests and receipt history remain; other gallery invitations remain independent. Messages already accepted by the provider cannot be recalled.

When an original source was temporarily unavailable, resolve the underlying issue and use Retry original approved notice only while its original attempt is still eligible. Changed content needs a new reviewed release. Do not create another release simply to work around an uncertain provider result: first reconcile whether the original message was accepted.

API and setup

The versioned /api/v1/gallery-releases interface invokes the same authorized services as the web workbench. It requires a named account session and current full private-workspace membership; shared-wedding access and integration keys do not confer this authority.

Activation requires the galleryReleaseDelivery deployment feature, current workspace availability, configured Resend sender and signed callback ingress, stable token-encryption key, private gallery storage and durable workers. Sandbox rehearsals must verify accepted/delivered separation, suppression, source changes, cancellation, lost responses and restart recovery before external delivery is enabled.