Skip to content

Join requests

Join requests are the self-serve path for a second employee at a company that already has an InPolicy workspace. Instead of hitting a dead-end waitlist, they can request to join and a workspace admin approves or declines from the Users page.

  1. A prospective member goes to the InPolicy sign-up page and enters their work email.
  2. Because a workspace already exists for their email domain, the sign-up gate redirects them to a Request to join screen.
  3. They confirm their email and click Request to join your workspace.
  4. Every workspace admin with the Manage users permission receives an email notification with a link to the pending requests list.
  5. An admin opens the Requests tab on the Users page, reviews the request, and clicks Approve or Decline.
  6. The requester receives an email with the outcome.

Admins can turn on Auto-approve join requests in Settings → Plan. When enabled, join requests for the workspace are approved automatically (the requester is provisioned as a Viewer without waiting for admin review). Auto-approve only takes effect once seats are unlocked. On the free plan, requests still queue for manual review.

  1. Open the Users page.
  2. Click the Requests pill next to All (a count badge shows how many are pending).
  3. The table shows every pending request and anything approved or declined in the last 24 hours.
  4. For a pending row, click Approve or Decline.
    • Approve provisions the person as a Viewer in your workspace and sends them a sign-in link. You can assign a more specific role afterward using the role-assignment controls on the Users page.
    • Decline notifies the requester by email.

Approved rows briefly remain visible in the Requests tab before moving to the All/Active filter — this lets you immediately apply role changes without switching views.

InPolicy workspaces start on the free plan, which has one seat (seatLimit = 1): the workspace owner only. Until seats are unlocked, nobody else can be added by any route. Join requests are queued but can’t be approved. Invitations, directory import, SCIM provisioning, SSO sign-in by new people, and reactivating a deactivated user are all refused, with a prompt to unlock seats.

Unlocking lifts the one-seat limit. There are four ways to do it:

Path Who Where
Sign up with an access code Any new user Sign-up gate
Redeem a code as an existing admin Workspace admin (Manage tenants) Settings → Plan → Unlock with code
Pay your first InPolicy invoice Whoever pays the invoice The Pay invoice link in the invoice email or on Settings → Plan
Internal flip InPolicy ops/sales Internal API

Once seats are unlocked, admins can approve join requests and optionally enable auto-approve.

If your workspace is invoiced by InPolicy, workspace admins (Manage tenants) see an Invoices section on Settings → Plan listing each invoice with its status (Open, Overdue, Paid, Void). Pay invoice opens the secure Stripe payment page, and PDF downloads a copy for your records. Seats unlock automatically as soon as the first invoice is paid. The number of seats is part of your agreement with InPolicy and appears on the invoice. Workspaces that aren’t invoiced don’t see the section.

Three transactional emails are sent as part of the join-request flow:

Email Recipient When
New join request All workspace admins A request is submitted (de-duplicated: one email per requester per 4 hours)
Request approved Requester An admin approves, or auto-approve fires
Request declined Requester An admin declines

All emails are localized to the workspace’s default locale (English, Spanish, French, German, Japanese, Korean, or Chinese).

Re-submitting a join request for an email that already has a pending or decided request returns the existing status without creating a duplicate or sending another admin notification.