Sharing outside the app

Most of the people a wedding touches never install anything. The couple answers from a link, guests reply from a page, a vendor reads their sheet in their inbox, and a client pays on a page with no account behind it. These are the surfaces a non-user meets, plain pages and emails that work on whatever they already have.

The couple's hub#

A couple with an account gets more than the link. Your wedding, on their trip, is the hub: the parts of the wedding you have opened for them, each with whether they can read it or also change it.

It is the same trip they were invited to, not a second place. They see the weekend, the decisions and the tasks as part of their own trip, and the wedding is one section of it — which is the point. A couple who had to open a different app to see their own wedding would be doing the wedding in two places, and neither would be current.

What each part says is your decision, not a setting they choose. See What you open for them.

The couple's link#

Copy their link, on the People screen, mints the couple's hub for the first partner with an address. It is one page, and it draws only the parts you have opened for that person: what is waiting on them, their tasks, the notes you shared and the files you did not hold back. Items sent to them carry Approve and Decline; anything you keep backstage is not on the page. Approving confirms the item, declining leaves it as it is, and either lands back in your list of what is with the couple.

Where you have let them change a part, the page takes a comment on a task, a file or a note, and a tick on a task you left editable. Guests, music and design stay in the app, and the page says so. The link does nothing before you open the wedding, and it stops working the moment you use Revoke shared links. The same link is behind Copy the couple's link in the wedding's sidebar. Links you sent earlier still open the trip view they always did.

Couple links live 90 days and are renewed by every re-send. A broken or expired link gets a clear error page, never someone else's wedding. The sending side of this lives in The couple. The roster also has Revoke shared links, which invalidates every outstanding shared link on the underlying trip at once; see People and the team.

The guest reply page#

Ask these guests to reply mints one link per household, handed to you to send however you already talk to guests. What a household opens is one page for everyone at that address, in their own language: a card per person, a row per moment they are invited to, the meal once, anything they cannot eat, the plus one by name, the children, and the bed asked once for the household when you are holding a block. Once the reply-by date has passed the page says so and gives your address, with what they already answered frozen on it. Guests never sign in and never make an account. See Guests.

The details form#

Send a details request mints each guest their own link, and what it opens is their page with the details form on it: name, phone, date of birth, passport and nationality, filled in by them, the email read-only because it is who the link is. The answers land on their roster card. Anyone with no email on file is named rather than quietly dropped. See Guests.

A vendor's sheet#

Send their sheet mails a booked vendor their own run sheet: their lines, the lines around theirs, their arrival, the venue and the numbers to ring, as you, in the wedding's language. The mail carries the sheet itself rather than a link to somewhere they would have to make an account. Print their sheet is the same page as paper, and the floorplan PDF rides along to the venue and the caterer. See The run sheet.

The live view, and the day texts#

Live view, beside a vendor, mints a link that opens straight to a page filtered to that vendor's lines. It reads the same run sheet you edit, so it is right the moment you shift the day. Send the day texts puts vendor links, and the next line, on phones; on the morning of the wedding the first texts go out on their own. Party members can receive those day texts, but there is no separate person row for minting a Live View link. Texts come with every planner plan and need the texting service switched on for your account. See The run sheet.

A view has a link too. In Views, Copy live link makes a page for a saved cut of the run sheet, such as the venue's or the band's, with no sign-in. It shows exactly the view's lines, on each moment's own clock, and follows the sheet as you change it. Deleting the view ends its link. A vendor's own link can be limited to a view the same way. See The run sheet.

Email ballots#

A shortlist sent to the couple is a decision, and a decision can be put to people with no account. Request votes by email sends each email-only participant a ballot link; they vote, and can change their vote until the decision closes. Quiet-mode tallies stay sealed on the ballot too. Ballot links are personal and expire after 30 days, and if that person later creates an account with the same address their votes reconcile onto it. See The couple.

The intake page#

Your public intake page needs no sign-up. The URL carries your own name, and the page does not exist until your account carries one. It asks a name, an email, what they are planning, roughly when and how many, and a note. Submitting it opens a deal on your enquiries board and mails you. See Enquiry forms.

A form's page#

A form you send opens as a page in your name, in the client's own language: your questions, nothing of the product's. Answering it once completes the request; opening the link again shows the same thanks page. An unanswered form is chased on its own, seven days after sending and every seven days after that. See Clients and getting paid.

The proposal page#

A proposal opens as a page in your name: the intro, the lines with the optional ones as checkboxes that update the total, the validity date, and Accept and Decline. Accepting asks for a typed name and an email; declining asks for nothing more than a note. Either is final, and past the validity date the page says so and offers neither button. See Clients and getting paid.

The signing page#

An agreement arrives as a mail with a link to a signing page, no account needed. The client types their name and signs; what is recorded is a simple electronic signature with an audit trail of the time, the address and the browser, and the agreement is locked at that moment. A copy goes to both of you. See Clients and getting paid.

The pay page, and the invoice page#

A payment request is a link, and the link is the whole authorization. The page shows what the payment is for in the milestone's own words, who it is from, the amount, the due date, and a way to pay. WeddingCraftr never sees the card and never touches the money in between. Until charges are enabled on your connected Stripe account, the page says you are not accepting payments yet instead of offering a button.

An invoice's link opens a public page where the client reads the document, the balance, your bank details and your payment link, and pays by card when your account allows it. A transfer, a payment link, cash or a check is one you record yourself. See Clients and getting paid.

The invitation page#

An invitation to the wedding, for the couple or for anyone you add to it, lands on a page that names the host, the wedding and exactly what the offered role can do. Accept joins, after sign-in or sign-up if needed; the page also offers a way to decline, and the roster shows either answer. An expired or revoked invitation lands on a clear "this invitation has expired" page. The bare join link, which the phone apps open directly, offers the store badges and a way to continue on the web. See People and the team.

Unsubscribe#

Every email's footer has an unsubscribe link: one click, no sign-in, clears every non-essential category for that address. The finer-grained toggles stay in email preferences. A vendor's sheet and a guest's reply link carry no preference at all, because neither has an account to hold one.