Relationships
#4554 swamp-club: serve-link copy, the username step, switching account, and withdrawn-link copy, in one pass
Opened by skunk-ape · 11/9/2026· Shipped 11/11/2026
The serve manual corrections moved to #4619 (2026-11-11), which already edits those pages, so one PR owns them. This issue is now the swamp-club UI pass: copy, the username step, switching account, and the withdrawn-link copy.
Part of #4459. This is the one swamp-club pass over the serve-link copy before customers. It absorbs #4589, which is closed into it. The customer guide for building an integration is a separate, new document (item 15).
Consent page, approved message and link email
Reconcile with what #4607 shipped (swamp-club d91a2123), which reversed part of the original list.
- Keep "The app supplied these details, and Swamp Club can't check them." (
components/ServeLinkConsent.tsx). #4607 relies on it now, next to the "this account is mine" confirmation. The original change to drop it is withdrawn. - Consent page, beneath Approve and Deny: "If you approve, we'll email you with a way to undo it." becomes "If you approve, we'll email you."
- After approving (
routes/link.tsx, the "approved" message): "We'll email you once the link is in place, with a way to undo it." becomes "We'll email you once the link is in place." - Link email (
content/emails/serve-link.md): remove "Opening that button only asks you to confirm. Nothing ends until you do." after the button. BumpLINK_EMAIL_TEMPLATE_VERSIONif a template change needs it. Keep the line #4607 added. - Read the copy as a whole after these changes, alongside #4607's wording, and keep it consistent.
The username step on the link page
An existing account with no confirmed username is sent to "Choose a username" when it opens a link, with nothing saying why. The person came to approve an app, and may not know that the name they pick here is permanent.
Change: when the step is reached from a link, say why in one line, such as "Confirm your username to finish linking the app. It can't be changed later." Then continue to the consent page as today. Keep the check, since the link email and the audit name the person by username.
A way to switch account on the refusal pages
#4608 shows a non-member a 403 page. The "signed in as someone else" and other refusal pages also leave a person who used the wrong account with no way forward. Add a "Sign in with a different account" link that returns to the same consent link, as the consent page's own switch-account option does.
Withdrawn link copy
The consent page for a withdrawn link request says "The app's owner replaced its credentials". Since #4622, a request is also withdrawn when the collective's plan lapses, and a person who opens it after the collective regains standing sees that wrong reason. Word the withdrawn state so it's true for every cause, or name the cause, and say the person can ask the app to start a new link.
Done when
- The consent page, the approved message and the link email read as above, and are consistent with #4607's wording.
- A person with no confirmed username who opens a link sees why they're asked, confirms, and lands on the consent page for that link.
- Every serve-link refusal page offers a way to sign in with a different account and come back.
- A withdrawn link request says it was withdrawn and how to link again.
- Tests that match the old text are updated.
Shipped
Click a lifecycle step above to view its details.
system commented 11/9/2026, 4:45:38 PM
Classified automatically when this issue was filed.
- Source: Swamp Club
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.