Invites, join requests and approvals

Three routes onto a crew — an invite you send by SMS, email or link; a join request someone submits; or a signup waiting for approval — each with a role and crew set at the point of admission.

What it is

InviteModal creates an invitation with a role, an optional locked crew and a delivery channel. JoinRequests lists people who asked to join, PendingApprovals lists signups awaiting a role and crew, and PendingInvitations tracks what is outstanding, expiring or unattached to any crew.

Also called: invite someone to a crew · new person wants access · approve a signup · pending invites · invite a team member · add a user · invite crew · onboard staff

See it
Invites, join requests and approvals
Area
Platform & Admin
Group
People
System
Team & Crews
Solves
3 named problems
01The inviter's own role limits which roles they can grant; a crew lead's invites are locked to their own crew.
02Delivery is SMS, email, both or a copyable link.
03Join requests and pending signups are approved with a role and crew chosen at approval time.
The Crews tab stack: Pending approvals, Join requests and Pending invitations cards above the crew list, with the Invite modal open over them. Sample data — no customer information appears here.
How it works
  1. 1The inviter's own role limits which roles they can grant; a crew lead's invites are locked to their own crew.
  2. 2Delivery is SMS, email, both or a copyable link.
  3. 3Join requests and pending signups are approved with a role and crew chosen at approval time.
  4. 4PendingInvitations polls, cancels in-flight requests on unmount, shows time since and time to expiry, and can resolve an invite for an existing user.
  5. 5Unattached invites (no crew) are listed separately on the Crews tab.
Why we built it

Someone who needs to sign in — a manager, a rep, an office admin — needs a real account, and handing out accounts first and sorting out roles later is how people end up with access nobody meant to give them. Invitations carry the role and the crew, decided at the point of admission rather than afterwards, and people who request access are approved or refused the same way. This is the account-side counterpart to field links: the crew gets a link, anyone who needs a login gets an invitation.

The problem
  • Access requests with no queue to work.
  • Invites disappearing with no visibility of what is outstanding.
  • Role escalation through invitations.
Sound familiar?
What you get
Three admission routes, one place to work them.
Role and crew decided at admission, not later.
Outstanding and expiring invites are visible.
What's inside
Invitations that fix themselves
If someone signs in without going through the invite link, the app finds their pending invitation by verified email and applies it automatically.
Diagnose a stuck invitation
A read-only endpoint that lays out everything known about one invitation across every store, so 'they signed up but it still says pending' has an answer.
Force-finish an invitation
An admin can complete an invitation on the invitee's behalf when the signup finished but the acceptance step didn't.
Self-serve applications land in your queue
A public form on your own address lets someone ask to join your company, and the application lands in your queue and nobody else's.
Nobody gets in until you approve them
A brand-new signup is marked pending and sees a waiting screen until an admin of the right company approves them with a role.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →