Skip to content

Notifications

Read and act on your notifications, turn on push for a device, and, as an owner or admin, choose how each event reaches your team.

For owners, office staff and crewLast reviewed
On this pageBefore you start

The bell in the ONYX1 sidebar shows your unread count and opens a notifications panel on a computer. On a phone, the bell is in the top bar of every main page (not inside a record such as a job or customer) and opens the Notifications page; Notifications is also a row in the More menu. Everyone has their own list.

Before you start

  • People can read and act on the notifications available to their current role. A field role cannot read a job admin-note notification, including one created before the role changed.
  • Only the owner and admins can change how events reach the team, in Settings → Notifications.

Your notifications

  1. Select the bell on a computer, or on a phone select the bell or the Notifications row in More. The Unread view shows what is still unread by default.
  2. Select All to see your recent history, or Unread to return to the unread list. If a list has more than it can show at once, ONYX1 says Showing the latest N at the bottom.
  3. Select a notification to mark it read. On a computer it opens its details in a panel beside the list, with a link to the full record. On a phone it opens what it is about: a job or invoice opens as a new screen. On every device, queue notifications, such as digests, Xero invoices waiting for a job, and the nightly site-report roundup, open their filtered list. Timesheet approval and send-back notifications open the specific week. A send-back notice includes the reason, and its email has an Open the week link to that same timesheet.
  4. In the released Android app, a notification about a request you may decide (a purchase, for example) opens in a sheet showing the amount, who it is for, who requested it and any limit. Approve and Decline act on the request immediately, through the same approval ONYX1 uses everywhere else; Decline asks for a short reason first (optional for leave). Ask a question opens the full request, where the conversation is. Approve and Decline only appear while the request is still waiting for a decision from you, and a timesheet is only approved from its review screen. Once a request is decided, its notification opens the same sheet with no Approve or Decline and an Open full record button. On an iPhone, the same notification opens the record directly.
  5. With one or more notifications unread, select Mark all read (Read all on a phone) to clear them all at once.

With nothing to show, the list says You are all caught up.

What the icons mean

Each notification's icon shows what it is about, and its colour shows whether it needs you.

  • A shield is a safety item: safety documents, a site report such as a Pre-Start or Permit to Work, a compliance document, or flagged or quarantined equipment. A red shield is an incident.
  • A green tick is finished work: a completed task, or a job moved to Completed.
  • A clock is a timesheet, a calendar is leave, a receipt is a purchase and a briefcase is a job or task. A document is a quote, invoice, variation or job proposal.
  • A list is a roundup, a conversation or an ONYX1 Office result, such as a digest, the nightly site-report roundup, Xero invoices waiting for a job, an enquiry, a comment on an approval, or finished Office work.
  • A megaphone is an announcement from your owner or admin. Selecting it opens the announcement with Got it. See Send announcements to your team.
  • A bell is anything else, including ONYX1 Office status.

Amber means it needs you. A request waiting for your decision stays amber until it is decided, then turns grey. Other amber alerts, such as safety documents to approve or equipment due, turn grey once you have read them. Incidents stay red and finished work stays green.

In the iPhone app, these icons arrive with the next app update.

Turn on push for this device

In a browser

Push on this computer in the desktop panel and Push on this phone on the phone page are per-device switches. Each affects only the browser on the device where you select it.

  1. Open Notifications.
  2. Select the push switch and allow notifications when your browser asks.
  3. ONYX1 confirms with Notifications on for this device.

Select the switch again to stop push there. If the switch cannot be turned on, ONYX1 says why next to it: your browser has blocked notifications for ONYX1, the browser doesn't support push, or push isn't configured on this server. If notifications are blocked, allow them for ONYX1 in your browser settings and reload the page. In an iPhone or iPad browser that has not been added to the home screen, the switch stays Off and ONYX1 shows: iPhone: use the ONYX1 app. iPad: Share → Add to Home Screen. On an iPhone, get push alerts in the ONYX1 app from the App Store. On an iPad, push alerts work after you add ONYX1 from the browser to your home screen: tap Share, then Add to Home Screen, open it from there, and enable push again.

While this device shows On, select Send a test notification to send a test push to each browser push subscription registered to your account. Each result names the push service, not its endpoint, and shows accepted (HTTP status) when the service accepts the push; refused (HTTP status: reason) with a short reason when available, or refused (no HTTP status: reason) when the service gives no HTTP response; gone (HTTP status), subscription removed when the service no longer recognises that subscription; timed out when the request reaches its time limit; or Push sending is not configured on the server when ONYX1 has no push credentials. An accepted result does not confirm that your device displayed the notification.

In the ONYX1 app on iPhone or Android

The Notifications page shows the app's notification permission. When the status is Off and Turn on notifications is available, select it and allow notifications in the device permission prompt. When permission is granted, the status changes to On.

In version 2.1.0 and later of the Android app, on Android 8.0 or newer, notifications from the app arrive under the ONYX1 notifications category in your phone's notification settings. The category description is “Jobs, approvals and updates from ONYX1.” To turn it on or off, open Settings, Apps, ONYX1, Notifications and use the switch for ONYX1 notifications.

If the status is Off and the page says Notifications are blocked in iPhone or Android settings., select Open settings to change ONYX1's notification permission in device settings. If push is unavailable in this app version, the page says Push is not available in this version of the app. and has no action.

After you sign in, the app may also ask whether to turn on notifications for your jobs and approvals. Select Turn on to continue to the device permission prompt, or Not now to be reminded later.

Choose how each event reaches your team (owner and admin)

  1. Open Settings → Notifications.
  2. Under Summary digest, choose Off, Daily, Weekly or Monthly for a recurring email to admins, dispatchers and office covering jobs completed, invoices paid, overdue, and approvals waiting.
  3. To change a whole channel at once, use the All team events row above the table. Its In-app, Email and Push switches sit above the matching columns. Turning one on sets every team switch in that column on; turning it off asks you to confirm, then sets them all off. A column that is partly on shows off. These switches cover your team's event switches only. The Customers rows, which decide what ONYX1 emails your customers, and the summary digest keep their own settings, and people switched on under Xero job queue recipients keep getting those notices; the digest has its own Off setting under Summary digest.
  4. In the table below, find the event you want to change. Events are grouped as Jobs, Sales, Staff, Safety and Customers. Turn a switch on or off for In-app, Email or Push; a dash means that channel isn't offered for that event. Every change saves immediately.

The Customers group is different from the rest: those switches decide whether ONYX1 emails your customer (a quote or invoice sent to them, an overdue reminder, their copy of an approved site report), not your team. Every other group notifies people on your team.

The Jobs group includes Admin note added to a job. When an owner or admin saves a changed, non-empty private job note, every other active owner or admin gets an in-app notification and an email by default. The author is left out, and field roles never receive or read the note or its notification. If someone is deactivated or moved to a field role, they can no longer read an earlier admin-note notification and any queued email is skipped. Each notification links to the job and includes the saved note. Use the In-app or Email switch on this row to turn off that channel.

The Jobs group also includes Job labour hours running ahead of progress. ONYX1 sends it once a day, when a live job's colour changes to red or orange. Red goes to owners and admins, and orange goes to admins. See Job health: labour against progress.

The Staff group includes Company announcement from an owner or admin. It offers Push only: every announcement always appears in the bell, and the Push switch decides whether it also reaches phones.

The Staff group also has Your Office server went offline and Your Office server is back online, which go to the owner and admins of a workspace that uses ONYX1 Office. See Get told when your Office server goes offline.

The Safety group includes Subcontractor insurance or prequalification expiring or expired. It notifies active owners, admins, dispatchers and office staff through the channels enabled for them when the latest dated document is within 30 days of expiry, and again at expiry. Field roles do not receive these notices.

SMS and customer text messages aren't available yet; the SMS column shows a dash everywhere until then.

If no email sender is set up for your workspace, ONYX1 shows Email isn’t sending yet. above the table: the Email switches still work and queue messages, but nothing is sent until an email sender is configured. In-app notifications are unaffected.

See Job safety documents and owner approval for the safety-document events in this list, and Security settings for the policies that create some of the events under Safety.