Inviting a teammate and withdrawing the invitation

Who this guide is for: the business OWNER or a customer ADMINISTRATOR who manages people.

This guide shows exactly what happens when you invite a teammate to your business: the invite form, the one-time invite code that is shown once and never again, and how to withdraw (revoke) an invitation. It covers what the recorded evidence proves — invite and revoke — and names honestly what has no recorded evidence yet.

About the pictures. The test owner u-alice, the test business "Sample Business A" and the invited address lane3456.f350b9ab@example.test come from an isolated test run — not live customer traffic. No invite email was actually delivered; the code shown is the product's own one-time display.

Plan note. Inviting teammates needs a plan that carries teammate seats. The Basic plan is one person including the owner and one WhatsApp number — there is no second seat to invite on Basic, so this screen is for plans above Basic. Basic is messaging-only with no bots and no AI. (What a limited teammate experiences after joining has no guide in this tree yet — see the pending list below.)

Step 1 — Open the Seats screen and fill the invite form

Your Seats screen shows the seat register (everyone invited or joined) and the invite form: an email address and a role. In the example the role is member and the address is lane3456.f350b9ab@example.test.

Seats surface with the invite form (member role)

Step 2 — Copy the invite code when it appears (you get one chance)

When you issue the invite, the product shows the invite code with its own warning on the panel: copy it now — it is never shown again. After you dismiss the panel, returning to the screen will not bring the code back.

Invite token surfaced once, with its never-shown-again warning

What to do: copy the code immediately and pass it to your teammate through a channel you trust. If it is lost, revoke the invite and issue a new one.

Step 3 — Withdrawing (revoking) an invitation

To withdraw an invitation, revoke it from the same screen. The register then shows the invite in its revoked state — the address was invited, the invitation was withdrawn, and the register says so honestly. (This final state is recorded in the run's receipt; the screenshots capture the screen and the code panel.)

What has no guide yet — the honest pending list

The parts of the seat lifecycle beyond invite-and-revoke have no recorded journey evidence. They are deliberately not described:

None of the above is claimed or sketched; they stay on the missing-evidence list until a qualified journey records them.

Where the receipts live

What Where
Final-run screenshots (this guide's images, byte-exact) C:/CT-ZCODE-BATCH3456/journey-artifacts/final-run/lane3456-A/
Per-leg record (invite, token, revoke, register state) …/final-run/lane3456-A/journey-results.json
Journeys lane ledger (receipt mapping) C:/CT-ZCODE-BATCH3456/lane-journeys-ledger.json
Playwright results of the final 3-pass run …/final-run/results.json, …/final-run/journeys-combined.json
Guides lane ledger of record C:/CT-ZCODE-BATCH3456/lane-guides-ledger.json

Evidence record (kept for honesty). Written from the final passing run of the BATCH3456 journeys lane (journey A, owner admin — seats leg A4), recorded 2026-10-24T12:29Z — 3 journeys passed together in one chromium run, exit 0 — on branch codex/zcode-3456-journeys @ 9d2136cb (fresh Main358 base). Leg record verbatim: "seat invite issued (member, lane3456.f350b9ab@example.test), token surfaced + dismissed, then revoked; register shows the revoked state." All of it is local candidate evidence — Chief acceptance OPEN, Main integration OPEN, nothing here is a live claim.