Invitations
Path: /org/invitations
Audience: owners and administrators. Administrator-only section. What the recipient does is in Accepting an invitation.
Two kinds of invitation
| Kind | When to use it | Constraint |
|---|---|---|
| Link invitation | Several people, or you do not yet know who | Anyone holding the link can use it — control distribution |
| Email-targeted invitation | One specific person | Only the account with that email can accept; forwarding does not work |
What you can set
- Role — whether they join as Administrator or Member;
- Quota limit and period — same rules as Members (monthly / daily / total, 0 means unlimited);
- Lifetime — 168 hours (7 days) by default;
- Maximum uses — unlimited by default, but still bounded by the enterprise member cap.
The token is shown exactly once
Creating an invitation returns a one-time plaintext token; the link looks like:
https://alltokens.si/join/<token>This token appears in plaintext in exactly one response. The server stores only its SHA-256 digest, so nobody — including platform administrators — can recover it. If you lose it, revoke the invitation and create a new one; do not ask us for the original.
The token is 24 bytes of cryptographic randomness, so it resists enumeration. Anyone holding the link can join, so treat it like a password.
How an invitation dies
| Case | Detail |
|---|---|
| Revoked | You revoke it from the list |
| Expired | Past the configured lifetime |
| Uses exhausted | The configured maximum was reached |
| Email mismatch | The accepting account’s email differs from the targeted one |
| Member cap reached | The invitation is valid but there is no seat left |
The first four surface an explicit reason on the acceptance page. The list shows each invitation’s state and use count.
Revoking
Revoking from the list invalidates the link immediately. People who already accepted are unaffected — revocation targets unused invitations.
Related
- Members — changing people who already joined
- Audit records — who created and revoked invitations