Inviting teammates during alpha

You can invite teammates into Closr during alpha, but the workflow has two gates. Both have to be satisfied or your invitee gets stuck. Here's how it actually works.

The two gates

1. 1**AlphaInvite token** (Closr's gate). Every alpha account needs a single-use invite link bound to a specific email. Without one, the signup page redirects to a waitlist.
2. 2**GCP test users list** (Google's gate). Because Closr is in Google's Testing mode for OAuth, only emails on the test-users list can complete the Gmail connection. This list is managed manually by Ara in Google Cloud Console. Max 100 entries.

The first gate is something you can do yourself. The second one currently requires a message to Ara.

Inviting a teammate (the actual flow)

1. 1Go to **Settings → Alpha invites**. If you don't see that page, your account isn't currently enabled for inviting. Ping Ara to enable it.
2. 2Click **Mint invite**.
3. 3Fill in: **Label** (an internal note for you, e.g. "Sarah, my TC". Your invitee never sees this.), **Email** (their email; strongly recommended), **Expires in (days)** (optional; leave blank for no expiry).
4. 4Click **Mint invite**. You'll see a URL that looks like `https://getclosr.app/signup?invite=<token>`.
5. 5**Copy the URL** and send it to your invitee. They click it, sign up with the matching email, and they're in.
6. 6**Tell Ara** (reply to your invite email, or message him directly): "I just invited [their-email@whatever]. Can you add them to GCP?" He'll add them to the test users list within the day.

That last step matters. If your invitee signs up without being on the GCP list, they'll get into Closr but the Connect Gmail button will error out at Google's OAuth screen. They can use everything else in the meantime, but the inbox half won't work until Ara adds them.

What your invitee sees

• •They click your link.
• •They land on Closr's signup page. They sign up with the email you bound the token to (the email on the token must match the email they sign up with).
• •They go through onboarding the same way you did. Cody/Cloe greeting, personal phone for nearNumber Twilio provisioning, optional Gmail connect at the end.
• •At the Gmail connect step, if Ara has added them to GCP: they see the "unverified app" warning, click through Advanced → "Go to closr.app (unsafe)", grant scopes, done. If Ara hasn't added them yet: Google's screen refuses the connection with an "access blocked" error. They wait for Ara, then retry.

Why two gates instead of one

GCP test users limit (100 per project) is Google's, not ours. AlphaInvite tokens are Closr's gate, so we control who can sign up at all. The two together let us invite specific people, prove the workflow, and keep the Gmail integration usable while we're in Testing mode.

The plan is to move onto Nylas's shared GCP project once we hit roughly 80 active inboxes. At that point the GCP gate disappears for everyone. The AlphaInvite gate stays for the duration of alpha.

Roles, teams, and what's deferred

Closr has multi-agent role plumbing (TEAM_LEAD, TC, team-scoped deal assignment, audit log). That work exists in the backend but the UI for managing it lives behind feature flags during alpha. For now:

• •Each tester is solo. Their teammates get their own solo workspace.
• •Sharing pipelines and assigning deals across users is being polished and gated on RLS in production.
• •If you need shared deal visibility across teammates today, tell Ara what you'd want and he'll either turn the flag on for your team or move the work up the queue.

Heads up