Inviting Your Team

Overview

PreStartGo has two kinds of people, and they join in two different ways. Console users — the office side — are invited by email and sign in to the admin console with an email and password. Field operators — the people inspecting and starting machines — are never "invited" at all: you create a licence against their phone number, and their account comes into existence the first time they sign in to the mobile app with that number.

The split is deliberate. An email identity with console access and a phone identity with machine access carry different powers, different sign-in flows, and different audit trails — and one person who genuinely needs both holds both, as two separate identities.

Inviting console users

1. 1
   Open the Users page in the admin console and choose Add User.
2. 2
   Enter their work email address and pick an organisation role — see the table below.
3. 3

   They receive an email with an invite link, set their password, and land in your organisation. Pending invites are listed on the same page, where you can re-send or revoke them.

The organisation roles, from widest to narrowest:

Account Owners and Administrators must enrol in multi-factor authentication at sign-in — see Signing In and MFA. The full permission-by-permission breakdown lives in Console Roles and Permissions.

Adding field operators — by licence, not invite

An operator's authority in PreStartGo is a licence: permission to operate a particular group of equipment, at a particular level, for a period you set. To add an operator:

1. 1

   Open Licences in the console and create a licence against the operator's mobile phone number, choosing the equipment group, the licence role, and a validity period.

2. 2

   The operator installs the PreStartGo mobile app and signs in with that phone number — a code arrives by SMS, and their account is created on that first sign-in. There is no invite email and no password.

3. 3

   From then on, the machines in their licensed groups appear in their app, and their pre-starts, defects and unlocks are attributed to them.

The licence roles sit side by side rather than on a ladder:

See Licensing Operators for renewals, revocation and licence periods.

One person, both worlds

A supervisor who also works the console holds two identities: an email account for the console and a phone-based account for the field. They are separate sign-ins with separate audit trails — deliberately, so that what someone did at a machine and what they did at a desk are never blurred together.

Site-based access (Builder plans)

Builders hosting sites have a third audience: site personnel — gate officers, safety officers — who need site tools rather than equipment authority. They're granted site access on the site itself rather than an equipment licence, and they use the lightweight Go web app rather than the full operator app. If you're not hosting sites, this doesn't apply to you.

Edge cases

• Changing an operator's phone number means their identity moves with it — talk to support before recycling numbers between staff, since the number is the sign-in.
• An operator working for two organisations (a contractor licensed by two companies) uses one phone number for both; each organisation's licences grant access to its own equipment, and records stay separated per organisation.
• Removing someone — revoke their licence (field) or remove the user (console). Their historical records remain, attributed to them, as the audit trail requires.
• Accepting while your account is suspended — an invite can't be accepted while the organisation's subscription is suspended, or while PreStartGo has disabled the account. Nothing is created and the invite stays open, so once the subscription is recovered the same link works again, until it expires.

Troubleshooting