Opt-out requests

Participants don't have accounts, but they can still ask to pause, slow down, leave, or rejoin — through your workspace's opt-out form, whose link rides along in every announcement email. Their submissions land on Requests (the nav badge shows how many are waiting), and nothing changes until you approve it.

Why approval?

The opt-out form needs no login, so approval is what stops one person removing another. The form's link is unguessable and specific to your roster, submissions only ever queue, and the form never reveals whether an address is on your roster — but the final word is always yours, one click here.

What a request looks like

Each card shows who's asking (name and email), when, their ask in one line — "Pause from Jan 6 until Feb 3", "Be paired every 4 weeks at most", "Remove from the roster permanently", "Rejoin the roster" — any note they added, and the roster context: how they're on file, and their current status.

If the address matches nobody on your roster, the card says so in red — probably a typo, or someone who was never added. Approving would do nothing, so the Approve button is disabled; add them first if they should be here.

Acting on it

Approve applies the change exactly as if you'd done it yourself from the roster (a removal also detaches them from any unsent draft weeks). Decline leaves the roster untouched. Either way you can attach an optional note, and the Pending / All filter lets you review past decisions.

If someone sends several requests, the most recent one is the one that matters — that's also what the form tells them.

Requests usually beat the next round

The form promises participants their request "usually takes effect before the next round of pairings goes out" — a quick glance at Requests before you generate keeps that promise.