Open a private invitation from the wedding website

A published wedding website can offer Open your invitation. The guest pastes the private invitation link or code already supplied by the host. The application opens that household’s existing invitations in a short-lived device session. There is no guest directory, name search or automatic creation of new invitations.

Turn entry on

Open the wedding’s Website, then Manage guest entry. An owner or administrator can enable entry, choose a device session duration from 15 minutes to 12 hours, and allow private photo sharing when Guest Hub uploads are also enabled. Save the settings. The public website must be published for entry to work.

Saving these settings invalidates earlier website sessions. It does not replace original invitation links, alter saved RSVPs, or republish the website’s content. Changing website access, replacing or revoking an invitation, changing its household contact, or unpublishing the website also prevents affected sessions from continuing.

Use an invitation

Choose the invitation link on the public website. Paste the full invitation URL from the host, its /rsvp/… path, or the invitation code. Only the configured application’s invitation URLs are accepted. The application does not fetch the pasted URL. Links to other sites, names and email addresses cannot open an invitation.

For example, the Moss household contains Rowan and Ash. Both are invited to Saturday’s ceremony; only Rowan is invited to Friday’s family dinner. The private page shows Friday’s event for Rowan alone. Another household’s guests, answers and private event invitations are not included.

Select each person’s attendance, meal and required answers, then choose Send our reply. Events left unanswered keep their saved state. Closed events display the saved response and direct the guest to the host for changes. A changed invitation or a reply saved from another device may require a reload before the new response can be accepted.

If the host has reserved an additional place, Add an invited companion consumes one available place. The companion receives only events shared by every existing named household member. Repeating the same interrupted request does not create another guest or save a second response.

Device access and privacy

The private page uses a secure, HTTP-only, host-only cookie on the application’s origin. The invitation code is not carried into the private page’s URL or exposed as a client-side session secret. A website on a custom domain hands off to the application origin; the private session is not placed in a custom-domain cookie.

Choose Sign out of this device when finished, especially on a shared device. The host can also revoke a specific session from Guest invitation entry. The session list identifies the household, creation time, expiry and whether access is still current. Revoking one session does not revoke the household’s original invitation or remove earlier replies.

Possession of the invitation is the basis for access. This flow does not verify a person’s identity or ownership of an email address. Anyone holding the original link can open another session while that invitation remains current. Keep it within the household; ask the host to replace or revoke the invitation if it was shared accidentally. Guest accounts and subscriptions are not required.

Messages and photos

When Guest Hub is enabled, the private page can include the household’s permitted community messages and photos. New photo uploads also require the host’s website-session upload permission and Guest Hub upload setting. Turning off new uploads does not by itself remove access to previously shared photos or prevent a permitted removal.

Guest Hub moderation controls visibility within the private guest community. It is separate from publishing a public wedding website. Uploading, approving or viewing a guest photo does not place it in the public website. See guest hospitality and community access for the existing private community controls.

Availability and activation

An unavailable or expired session asks the guest to open their invitation again. Entry failures do not reveal whether a name, email or household exists. Repeated attempts are throttled; the host can help with the current invitation when access is unavailable.

This flow reuses the saved invitation, event roster, meal and RSVP history. It does not send an invitation email or text. Production database migration, encryption configuration, the canonical HTTPS application URL, secure-cookie and custom-domain rehearsals, and private media storage remain coordinated activation gates. Local database tests and isolated browser rehearsals do not establish live provider delivery or a public launch.