Adding teammates is a two-step process: send them an invite, they accept, they're in. Takes about 30 seconds per person.
Who can invite users
Only tenant admins can invite. If you don't see an "Invite User" button on the Team Members page, you're a regular user. Ask your tenant admin.
Sending an invite
- Open Team Members
- Click + Invite User
- Fill in two fields:
| Field | What it does |
|---|---|
| Where the invite link is sent. Must be unique across JAMS Incident Management — one person can't have two accounts with the same email. | |
| Role | Member = can see + acknowledge alerts they're a recipient on. Admin = can also manage flows, users, integrations, and billing. Default is Member. |
- Click Send Invite.
That's the whole form — there are no name fields here (the invitee fills those in on accept) and no expiry control. Invites expire automatically after 7 days, fixed server-side.
JAMS Incident Management emails the invitee a single-use link. After they click and submit the accept form, the token's burned.
What the invitee sees
When they click the invite link they land on the Accept Invitation page. It asks for:
- First and last name — pre-filled from the invite when JAMS Incident Management already has them; the invitee can edit before submitting.
- Phone number — required. It's used for SMS and call notifications, so enter it in E.164 format (e.g.
+12025550123). See Your Profile for the format rules. - A password (8+ characters, entered twice to confirm) — unless your tenant enforces SSO, in which case there are no password fields (see below).
There is no SMS opt-in checkbox on this page. SMS consent is handled separately and self-service — see "SMS opt-in" below.
On a non-SSO tenant, the button reads Accept Invitation & Create Account. When they submit, they're signed in and land on the dashboard.
Inviting users when your tenant has SSO
If you've turned on Enforce SSO under Integrations → SSO, the invite-accept flow works differently:
- The Accept Invitation page shows no password fields at all — the subtitle notes that your organization uses single sign-on.
- The invitee still confirms their name and enters their phone number, then clicks Continue to Sign-In.
- On submit, no password is stored; they're redirected to your identity provider to authenticate. Their JAMS Incident Management identity is anchored to the IdP from day one.
Important: for SSO-enforced tenants, the email you invite must ALSO exist in your IdP. If you invite jane@example.com but Jane doesn't have an account in your Entra/Okta/Google tenant, the SSO sign-in will fail with user_not_provisioned. Solution: invite them in your IdP first, then in JAMS Incident Management.
Choosing the right role
| Role | What they can do | What they can't |
|---|---|---|
| Admin | Everything in the tenant: create/edit flows, invite users, manage integrations, change billing, view audit log | Anything outside their tenant — they can't see other customers' data |
| Member | Acknowledge alerts they receive, view + edit their own profile, opt in/out of SMS, update contact info | Create flows, invite others, change tenant settings |
Default to Member for most teammates. Promote to Admin only for the small number of people who need to build flows or manage the team — usually 1-3 people per company.
Why this matters: Admin and Member are both scoped to your tenant. There's a separate cross-tenant "global admin" flag reserved for the JAMS Incident Management operator account — a normal tenant Admin can never see another customer's data.
After they accept
The new user shows up in Team Members with a green dot if active. From there, you can:
- Add them to Team Groups — useful for "on-call rotation" or "data team" recipient lists you reference across flows
- Set their notification schedule — click the user on Team Members to open the per-user Notification Schedule modal, where you set when they're available to receive alerts (after-hours? weekdays only?) or mark them off-duty
- Add them as a recipient on existing flows by editing those flows
SMS opt-in is self-service
JAMS Incident Management will not send SMS to a user who hasn't opted in (or who has replied STOP). That user's other channels for the same alert — call, push, email — still fire, but SMS is held back until they consent.
Opt-in is each user's own choice and can't be flipped for them from Team Members — there's no admin toggle for it. The user enables it themselves on their profile under Settings → SMS Notification Preferences, or by texting START to the JAMS Incident Management number. This keeps SMS consent compliant.
So after a teammate accepts, if they're meant to receive text alerts, remind them to open Settings and turn on SMS consent.
Common gotchas
- Email already exists — that email's already a JAMS Incident Management user (possibly in another tenant). Pick a different one or check with the person.
- Invite expired — past the expiry date. Resend a fresh invite from Team Members → Pending invites.
- Accepted but not getting alerts — they accepted, but they haven't been added as a recipient on any flow. Edit your flows or add them to a Team Group that's already a recipient.
- Got the email but link goes to a "Tenant suspended" page — your tenant's subscription has lapsed. Check Billing.
Removing or deactivating
You can't delete a user (we keep the record for audit trail integrity), but you can deactivate them. From Team Members, click the user → toggle "Active" off.
Deactivated users:
- Can't log in
- Are skipped during flow escalation (the flow doesn't pause for them)
- Stay visible in audit logs and notification history
If they later need access again, just flip Active back on.