What are Users?

Users are everyone with login access to your Atender workspace — agents handling conversations, supervisors managing them, admins configuring everything. The user system covers invitation, role assignment, team membership, and account lifecycle (active / inactive / deleted).

What a user has

• Email — Login identifier. Must be unique within the workspace.
• Full name — The user’s real name
• Display name — The name shown to callers and teammates (often the same as full name)
• Role(s) — One or more roles — at least one required
• Team(s) — Optional team memberships — users can belong to multiple
• Active status — Currently enabled or deactivated
• Beta access — Per-user toggle for accessing beta features

Inviting users

Users are created by invitation:

1. An admin enters the new user’s email, name, and role
2. Atender creates the account and (if Send invite is on) emails the new user a login link
3. The invited user clicks the link, sets their password, and lands in the workspace with their assigned role

There’s no public sign-up. Every user must be invited by an existing admin. The invite includes a one-time link with an expiry; if it expires, the admin can resend the invite.

See Invite a user for the full flow.

Active vs inactive

Users can be deactivated without being deleted. Deactivated users:

• Can’t log in
• Don’t appear in default user lists (separate “Inactive” tab)
• Retain their conversation history, notes, and audit trail
• Can be reactivated at any time

This is the right path when someone leaves the team, takes long leave, or temporarily shouldn’t have access. See Deactivate or reactivate a user.

Deletion is permanent and rare — use it only for accounts created in error or for compliance-driven removals. The user’s history is removed too.

Sole-owner protection

The system prevents you from removing the last user with the Owner role:

• Can’t deactivate them
• Can’t remove their Owner role
• Can’t delete their account

The workaround when transferring ownership: assign Owner to a second user first, then make the change.

What’s NOT supported today

A few things to set expectations:

• SSO / SAML — not currently. All users authenticate via email + password (managed by Supabase auth under the hood).
• 2FA — not exposed as a tenant configuration.
• Public sign-up — workspaces are invitation-only.
• Cross-tenant accounts — a user in Tenant A is not automatically a user in Tenant B. Each tenant has its own user list.

For most teams, the limitations don’t matter day-to-day. They become relevant when integrating with corporate identity providers or scaling across many regions / business units.

Pending invites

Invites that have been sent but not accepted appear in the Pending Invites section. From here, admins can:

• See when each invite was sent and to whom
• Resend — issue a fresh invite link if the previous expired or was missed
• Cancel — withdraw the invite if the user no longer needs access

Where to start

• Add your first user: Invite a user
• When someone leaves: Deactivate or reactivate a user
• Stale invites: Resend an invite
• Access problems: FAQ — User can’t access