A user is in /pending-approval if their workspace.approvalStatus is `pending_approval`, `rejected`, or `suspended`. The page polls /api/billing/state every 8s — the moment you flip them to `approved`, their session refreshes them into the dashboard.

If you have already approved and they are still stuck, ask them to click "Retry" on the page or sign out and back in.

Browse /dashboard/email-logs for that recipient. If `delivered` — they need to check spam.

If `bounced` — there is a domain config issue (SPF/DKIM/DMARC).

If nothing logged — they may have hit the 10/day per-email cap. Clear it: db.rate_limits.deleteMany({ scope: "resend_verify_email", key: "<email>" })

As a last resort, you can manually set `emailVerified=true` on their user row in Mongo and ask them to sign in again.

Check 1: Is the workspace `approvalStatus = "suspended"` or `"rejected"`? Flip it back.

Check 2: Is the workspace.organization_members row still present for that userId? If they were removed, re-invite.

Check 3: Is the user still email-verified? Some operations require it.

Check 4: Is the user hitting the trial gate? Their /api/billing/state will say `trial_expired`.

In Mongo, extend `subscriptions.trialEndsAt` to a future date. The trial gate re-evaluates on every request — no restart needed.

If they are ready to commit, flip `subscriptions.status` to `active` to remove the gate entirely.

The code is case-sensitive. Confirm with the user that there are no leading/trailing spaces.

Confirm the CLOSED_BETA_INVITE_CODE env var on the server matches what was shared with the user.

If MAX_WORKSPACES_PER_USER is set to 1, a user who has already created a workspace will see "invite code invalid" if they try to create another — clarify the cap.

Step 1: /dashboard/email-logs for the impacted address.

Step 2: If multiple workspaces affected, check the platform-level Resend API key and quota.

Step 3: Inspect Resend's status page for incidents.

Step 4: Confirm the workspace email_settings has a verified sender domain.

If a user reports "stuck on Loading your workspace…", they should now see an actionable recovery card after 8s with Retry / Sign-in / Create-workspace buttons.

Common root causes: 1) workspace pending approval (chrome redirects to /pending-approval), 2) session expired (chrome redirects to /login), 3) network hiccup (Retry usually resolves), 4) /api/auth/me 5xx (the auth-error card surfaces).

If the issue persists, ask the user to open dev-tools → network tab and share the /api/auth/me response.