TrainAR Docs
Try Free
Getting Started · Last updated 21 July 2026 · 2 min read

Inviting your team

Inviting a user creates a Dashboard login.

Inviting a user creates a Dashboard login. Giving them a seat to run sessions on is a separate step - that's the Seats tab.

Sending an invite

  1. Dashboard → Settings → Users (admin).
  2. Click Invite User.
  3. Enter their email + name. Pick a role: Admin or Member.
  4. Send.

The invitee gets an email with a link to set a password and join the account. Invitations don't consume a seat - they create a user record only.

Role: Admin vs Member

Two roles only:

Role Sees
Admin Everything - including Users, Seats, Billing, Integrations, API & Webhooks
Member Dashboard, Tasks, Sessions, Skills & Knowledge, Marketplace, Reports, Settings → General/Locality/My Seat

"Trainer" and "Trainee" are seat-mode roles, set on the seat (not the user). A seat can be both. See Users & seats.

Giving someone a seat

Inviting a user doesn't give them a seat or pull from your seat count. To do that:

  1. Dashboard → Settings → Seats → Add Seat (admin).
  2. Details step: pick roles (trainer / trainee) and assign the user you just invited.
  3. Choose Device step: Buy from TrainAR, register BYOH, or Skip for now. (Skip creates the seat in needs_device - add a device later from the seat row.)
  4. The engineer pairs their own phone (or glasses) from Dashboard → Devices, or from Settings → My Seat. See Install and pair.

Editing or deactivating a user

From the Users tab row's ⋯ menu:

  • Edit - full name, role
  • Deactivate - toggles is_active off. User loses Dashboard access; their data is preserved. Doesn't free the seat - handle that separately on the Seats tab if needed.
  • Reactivate - flips them back on
  • Delete Permanently - irreversible. Nullifies FK references on tasks/activity/etc., drops their roles and integration mappings, deletes the user record. Confirmation required. You can't delete yourself.

Bulk invites

For teams over ~10 engineers, the TrainAR REST API POST /v1/users endpoint is faster than one-at-a-time clicks. The accepted role values are admin and member. See the API reference for the exact request shape.

Where to next