Client Hub — questions, review rounds, and a private link for your client

Open a published project's Client Hub from the small "💬" button next to it in your projects rail (see "Finding and switching between your projects"). The hub only works for a published project — its link is built from the project's public address, so publish first if you haven't.

The first time, you'll set a hub password (at least 6 characters) under "Client hub access." Once it's set, the card shows your client's link (in the form /s/your-project/hub) with a "Copy link" button — send that link and the password to your client however you'd normally reach them.

"Change password" lets you reset it any time. Doing so immediately signs out every device already using the old password — a deliberate way to lock out access without needing a separate revoke step.

The "Ask a question" card lets you write a question, optionally give it multiple-choice options (one per line — your client can always type their own answer instead by clicking "Type my own answer"), and describe what the answer unblocks in plain language (e.g. "The homepage hours section") — that line is shown to your client so they understand why you're asking.

Checking "Part of the initial discovery batch" marks a question as part of the first round you'd ask right after an initial client meeting, distinct from an ad-hoc question you think of later — both work exactly the same way underneath; the checkbox is just how you keep track of which is which.

Every question you've asked shows up grouped by status. Open questions are still waiting on your client. Answered ones show the answer and who gave it, right under the question, the moment they submit it — nothing to refresh or re-check separately. "Retire" removes a question from your client's open list without deleting it (it moves to a Retired group you can still see, with a "Reopen" button if you change your mind) — use it for a question that no longer applies before your client ever answers it.

Once a question is answered, it can't be edited or retired — the answer is the record of what was asked and what was said, and that stays intact.

Your client opens the link you gave them, enters the password once (their browser stays signed in after that), and sees two tabs: "Questions" and "Review & Approve." Questions shows an optional "Your name" field plus every open question — multiple-choice ones as tappable buttons, free-text ones as a text box. Answering a question moves it into their own "Answered" list immediately, showing exactly what they said back to them.

There's nothing else for your client to configure or navigate — no separate login, no unrelated tools visible. The page shows your project's name and nothing about your other projects or clients.

This tab shows your project's real live page in an embedded preview, with a Desktop/Mobile toggle above it so your client can check both without leaving the hub or resizing their own browser window.

Clicking "📍 Pin a comment" turns the preview into a click target — your client clicks the exact spot on the page they mean, types what should change, and sends it. That comment appears as a numbered pin directly on the preview (an orange pin while open, green once you've confirmed it fixed) and in a plain list underneath, and it lands in your Feedback dashboard exactly like any other change request, with the same Open → In Progress → Awaiting Review → Confirmed status.

"✓ Approve this round" closes the current round once your client is satisfied with everything in it. A round's status and pin count are always visible in "Round history" underneath, so both of you can see exactly what v1, v2, and so on each covered and when each was approved.

Back in your Client Hub manager, a "Proof & rounds" card lists every round the same way your client sees it, plus a "Start round v[N]" button — enabled only once the current round is approved, so "v2" always means genuinely new work, not an arbitrary reset. There's no way to start a new round while one is still open for review; approve or wait for your client to approve first.

The third tab, "Requests," is for anything that isn't tied to one specific spot on the page — "can we add a testimonials section," "the site feels slow on mobile." Four stat tiles at the top count everything by status: Requested, In Progress, Done (needs your client's check), and Verified — the exact ladder Ike described: requested → in progress → done → verified, running on the same underlying statuses as pinned comments and your Feedback dashboard, not a second system.

A pinned comment from the Review & Approve tab shows up here too, tagged "📍 Pinned," so this tab doubles as one place your client can see everything they've asked for and its current state — the shipped-changes picture Ike asked for, always current rather than a separate digest to keep in sync.

You move a request from Requested to In Progress to Done from your existing Feedback dashboard (see that guide) — the same place you already work through every request. Once you mark something Done with a verification note, your client sees a "✓ Confirm this is fixed" button right on this tab and closes the loop themselves.