Your account

A account is your team's account on TrainAR — the boundary around your data, your users, your glasses, your sessions, and your subscriptions. Everything in this docs site that talks about "your data" or "your engineers" means within your account.

Accounts are strictly isolated. No other TrainAR customer can see your sessions, your knowledge, your tasks, or your engineers. The on-glasses AI only references your account's data.

What an account contains

Thing	What it is
Users	The people in your organisation with Dashboard access (admins and members).
Seats	The paid licences engineers use to wear the glasses + run sessions.
Devices	The paired AR glasses associated with your account.
Knowledge	The documents (manuals, specs, procedures) the AI can search in trainee sessions.
Skills	The tools the AI can call during sessions (system skills, your custom skills, bundle skills).
Bundles	The Marketplace subscriptions you've activated (e.g. Parts & Spares).
Tasks	The jobs your engineers are working on — manual or synced from your FSM.
Procedures	Re-usable training procedures extracted from trainer-mode sessions.
Sessions	Every recording, summary, and procedure-extraction job.
Integrations	The connected systems (FSM, CRM, custom webhook destinations).
API keys + webhooks	The credentials and event subscriptions for external systems calling into your account.

Users vs. seats

These are two different things:

• A user is a Dashboard login — typically an admin, ops manager, or office-side person. Users don't wear glasses. There's no per-user charge.
• A seat is a paid licence consumed by an engineer wearing the glasses and running training sessions. The platform charges per seat per month. You can also have your users hold seats if they're engineers themselves.

Add users from Settings → Users (admin). Add or remove seats from Settings → Seats (admin) — seats also reconcile to Stripe through Settings → Billing.

User roles

There are two roles today:

Role	Permissions
Admin	Full access — manage users, seats, billing, knowledge, skills, integrations, API & webhooks.
Member	Everything that isn't admin-gated: own seat & device pairing (My Seat), running sessions, viewing Sessions / Reports / Marketplace, working tasks.

The first user in an account (whoever signed up) is an admin by default. "Trainer" / "Trainee" in TrainAR refer to the seat's session-mode roles — not Dashboard access roles.

Account settings

Dashboard → Settings is a tabbed page:

• General — organisation name, timezone (everyone).
• Locality — country, language passed to the AI on the glasses (everyone).
• Users — invite, deactivate, delete (admin).
• Seats — add seats; the wizard's Choose Device step lets you buy hardware, register BYOH, or skip and add a device later; pair devices (admin).
• My Seat — your own seat and device pairing (everyone).
• Billing — subscription, plan, seats, minute pool, coupons, invoices, Stripe portal (admin).

Integrations, API & Webhooks, and Skills & Knowledge are separate top-level pages, not Settings tabs. See Settings overview for the full breakdown.

Account lifecycle

• Created at signup. First user becomes admin.
• Active while paid. All features available.
• Past due if billing fails. Read-only after 7 days. After 30 days, sessions stop being processed.
• Cancelled when admin cancels the subscription. Read-only access for 90 days for export purposes; data deleted after that unless you request preservation.

Multi-account scenarios

A few common patterns:

• One organisation, one account. The default. Everyone in your company shares the account.
• One organisation, multiple accounts — e.g. a head office account plus separate accounts per franchise or per region. Each account is fully isolated. Use this if you need strict data separation between divisions.

Where to next

• Your first session — go from "account created" to "session recorded" in 15 minutes.
• Settings & Configuration — the full settings surface.
• Glossary — every term you'll encounter in these docs.