Notification Preferences

Overview

PreStartGo tells the right people when something needs them — a failed pre-start, an invalidated check, a licence about to lapse, an assigned service job. This article covers the channels those notices travel on, what each person can tune, and the one rule that overrides all tuning: critical safety notices always get through.

The channels

What each person tunes

Preferences are personal and per notification type — one person muting a push silences nothing for anyone else.

• In the console, under Settings → Notifications (open Settings from the menu under your name): an email switch for each type that has an email. Every type still lands in your console feed; a browser can't receive push.
• In the mobile app, on the profile's notifications screen: push toggles per type.

Untouched settings follow sensible defaults per type; a saved choice sticks.

Organisation email rules

Separately from each person's own switches, your organisation can set email rules in the console under Admin → Organisation → Email notifications. A rule says when this happens — a pre-start fails, a defect or a critical defect is raised, equipment is locked out, a lockout bypass is used, or a service is due — who gets the email, and how often: immediately, or in a daily or weekly digest.

• Rules only add people. They email extra recipients on top of each role's built-in notifications, and never remove anyone from emails they already get.
• Recipients can be named console users, everyone holding a role or above, or outside email addresses such as a service company. Outside addresses get an unsubscribe link in every email. People who only use the phone app have no email address, so they can't be added.
• Who can change them — Contributors and above can see the rules; Administrators and the Account Owner can change them.

The critical exception

Types marked critical — an invalidated check, a critical defect bypass, a failed pre-start reaching supervisors — ignore preference toggles entirely, are delivered at high priority (they break through phone focus modes where the OS allows), and carry one further backstop: if push provably can't reach the person's phone, the platform falls back to SMS to their number.

That's deliberate. A safety-critical notice isn't something the platform lets anyone accidentally mute — the tunable channels are for everything else.

SMS, precisely

SMS is intentionally narrow, not a parallel feed:

• The critical fallback above — automatic, no configuration.
• Sign-in codes for the mobile app.
• Licence notices (granted, revoked, expiring) can go by SMS for organisations carrying the SMS notifications add-on — useful for workforces that live in SMS rather than push.

There is no general per-type SMS toggle, and no SMS copy of the whole feed.

Who gets notified of what

Recipients are resolved by responsibility, not broadcast. The pattern worth knowing: a failed pre-start notifies the supervisors licensed for that machine's group — the people who can actually act — and never the operator who submitted it (they were standing there). Where a machine has no group to resolve supervisors from, the notice escalates to the organisation's managers rather than reaching no one.

Equipment alerts (failed checks, low fuel) also land as alerts on the console dashboard — a worked queue with acknowledge/dismiss, separate from the personal notification feed. And Tracker-equipped machines add their tracking alerts — zone entry/exit, power loss, offline — through the same machinery.

Push reliability

Delivery is tracked per device. If pushes haven't landed on your phone for a fortnight, the app shows a warning banner rather than letting the silence pass unnoticed — the usual causes are notification permission revoked, or an OS "optimisation" freezing background delivery.

Edge cases

• A shared phone — preferences and delivery follow the signed-in person, and sign-out clears the device's registration for them.
• New phone — signing in registers the new device automatically; nothing to configure.
• Muted a type and missed things — the in-app feed always has the full history; toggles affect delivery, never the record.

Troubleshooting