What it is
Under the invite form, every pending invitation for the tenant is listed with who it was for, the role, when it was sent and when it expires. Admins see all; a crew leader sees only their crew's. The list polls so an acceptance clears without a reload.
Also called: who hasn't accepted · outstanding invites · invite status
See it
How it works
- 1GET /api/invite/list?status=pending, optionally scoped to a crew id.
- 2In-flight requests are aborted and superseded so a slow poll never surfaces as an error.
- 3Expected onboarding states (no org yet, pre-auth) are treated as normal rather than logged as failures.
- 4Rows offer resend, cancel and a confirm-gated finalize for a stuck invite.
Why we built it
The invite handshake has several places it can stall — the person signs up but the accept call never lands. Without a visible queue, an admin's only signal is that someone still shows as INVITED with no explanation and no action available.
The problem
- Sent invitations were invisible until they were accepted.
- A stuck invitation had no admin-side remedy.
Sound familiar?
What you get
Every outstanding invite is visible with its age and expiry.
Wrong or stale invites can be cancelled instead of waiting them out.
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 →