Inviting Users

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.

Field	What it does
Email	Where the invite link is sent. Must be unique across JAMS IMES — one person can't have two accounts with the same email.
First / Last name	Pre-fills the invitee's profile. They can change it on accept.
Role	`admin` = can manage flows, users, integrations, billing. `user` = can only see + acknowledge alerts they're a recipient on. Default is `user`.
Expires in	How long the invite link stays valid. Default 7 days.

JAMS IMES emails the invitee a link like https://app.jamssoftware.com/invite/accept?token=inv_.... The token is single-use, 128-bit random. 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 a "Welcome to [Tenant]" page that asks for:

Their name (pre-filled from your invite)
A password (8+ characters; OR skipped entirely if your tenant has SSO enforced — see below)
Optionally a phone number for SMS/call alerts
Optional SMS opt-in checkbox (required if they'll receive SMS notifications — TCPA compliance)

When they submit, they're auto-signed in to JAMS IMES 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 invitee skips the password field entirely (it'd be unused — they can only log in via your IdP).
Instead of auto-signing in, they're redirected to your identity provider to authenticate.
Their JAMS IMES identity is then 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 IMES.

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
`user`	Acknowledge alerts they receive, view their own profile, opt in/out of SMS, update contact info	Create flows, invite others, change tenant settings

Default to user 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.

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 — when they're available to receive alerts (after-hours? weekdays only?)
Add them as a recipient on existing flows by editing those flows

Common gotchas

Email already exists — that email's already a JAMS IMES 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.