Invite a user

Send a new user an email invitation that lets them set their password and access the workspace.

Before you start

• Admin permissions on Users (Owner, or a custom role with Users → Invite granted)
• The new user’s email and name
• A clear answer to “what role should they have?” — see Standard roles reference
• Optionally: which team(s) they should belong to

Steps

1. Open Settings → Users.
2. Click Invite (or Create user depending on UI version).
3. Fill in:
   Email — must be unique in the workspace
   Full Name — the user’s real name
   Display Name — how they’ll appear in conversations (often the same; can be a first-name-only version like “Erik” instead of “Erik Windahl-Olsen”)
   Role — pick from the dropdown. The default is usually Agent.
4. Toggle Send invite on (typically the default). With it on, Atender emails the invitation immediately.
5. Click Save or Send invite.

The user appears in the user list as Pending. Once they click their invite link and set a password, they move to Active.

What the invitee sees

When the new user receives the email:

1. They see an invitation from your workspace name with a “Set up your account” call-to-action
2. Clicking the link takes them to a password-setup page
3. They set a password, confirm, and land in the Atender workspace
4. Their assigned role determines what they see — agents land on the inbox, admins land on settings, etc.

The link is valid for a limited time (typically 7 days). If it expires before they click, the admin can resend the invite.

Add the user to teams

Team membership is set separately from the invite. After the invite:

1. The user accepts and sets a password.
2. Open the user’s profile (or Settings → Teams).
3. Add them to the relevant team(s). See Add or remove team members.

You can pre-assign teams via the API at invite time, but the UI invitation flow doesn’t include team assignment — it’s a follow-up step.

Bulk invitations

For onboarding multiple users at once (a new team, an acquisition cohort), the UI is per-user. Two options for bulk:

• Sequential UI invites — fastest for ~5-10 users.
• API-based invitations — POST to /api/users for each user, with role and team specified. Best for larger batches or repeatable scripts. See API Keys for setup.

A third option is the onboarding flow when first setting up the workspace — it accepts a list of email addresses and roles in one form. For ongoing additions to an existing workspace, use the per-user invite or API.

Verify the invite went out

1. After clicking Send invite, the user appears in the Pending Invites section.
2. Ask the invitee to check their inbox (and spam folder — invitations sometimes land there).
3. If the email doesn’t arrive within ~5 minutes, resend the invite. If it still doesn’t arrive, check the email is correct (it can’t be edited after invite — you’d need to cancel and re-invite with the right email).

Don’t invite

A few cases where invitation isn’t the right path:

• Service accounts for integrations — use API keys instead. API keys are the right primitive for non-human access.
• Bots / automated callers — these aren’t workspace users; they’re contacts in the CRM. Different concept.
• Customers with brief access needs — Atender’s user system is for your team. Customers don’t get user accounts; they’re contacts who interact via channels.

Troubleshooting

• Symptom: Email doesn’t arrive. Fix: Check spam folder. Confirm the email address is correct. If still missing after 10 minutes, resend.
• Symptom: Invite link is broken or shows an error. Fix: It may have expired. Resend a fresh invite.
• Symptom: “Email already in use” error. Fix: That email is already invited (Pending) or active in the workspace. Check Settings → Users → Pending Invites. Cancel the old invite if it’s stuck, or switch to a different email.

See also

• What are Users?
• Resend an invite
• Standard roles reference