Beta invites are gated by the CLOSED_BETA_INVITE_CODE env var. To invite someone, share that code with them (typically via the sales team or a personal email).

They register at /register, verify their email, then enter the invite code at /onboarding to create their first workspace.

Open /admin/workspaces every morning. The queue shows new pending workspaces.

Recommended checks: 1) Is the email work-related? 2) Is the workspace name + slug brand-appropriate? 3) Does the use case fit the beta criteria?

Approve in one click. The user gets an email and is automatically redirected to /dashboard the next time they refresh /pending-approval.

Watch for: spikes in disposable_email rejections (could indicate spam), spikes in `429 too_many_attempts` (could indicate brute-force), 5xx errors in /api/auth/me.

In preview, tail the Next.js log via the supervisor. In production, use your hosting provider's log explorer.

For email issues, browse /dashboard/email-logs for delivery health.

Use the public chatbot widget on the marketing site for inbound questions.

Schedule a 30-min checkpoint call with each new beta customer in week 2 — that is when they have actually tried the product.

Encourage them to file feedback in /contact?topic=feedback.

Open /admin/workspaces, find the offender, click "Suspend". The workspace immediately returns HTTP 403 `workspace_suspended` on writes.

If they have multiple workspaces (rare during closed beta), suspend each. If you need to fully terminate an account, contact engineering — there is no self-serve "delete account" yet.