Skip to main content
Notifications is where you control which emails AquaOps sends you, on top of what’s already visible in-app.

Purpose

Use this page to turn on or off the two email notification types AquaOps currently supports: an email whenever a new chemical alert is created, and an optional periodic compliance digest email. Nothing here changes what shows up in-app — the Alerts list and the Compliance module always reflect current state regardless of your email preferences. This page only controls whether AquaOps also emails you about it.

Who this applies to

These are personal, per-user preferences, not organization-wide settings. Each user sets their own values, and they only affect email sent to that user — there’s no admin control that overrides them for other people. Anyone can open this page; it isn’t gated behind a permission the way most other Settings pages are. That said, actually receiving a compliance digest also depends on your permissions (see Compliance digest below) — turning the setting on doesn’t guarantee delivery if you don’t hold the right access.

Where to find it

Go to:
Notifications lives in the Account group of the Settings sidebar, alongside Kiosk PIN, Security, and Help — it’s account-level, not organization-level configuration.

Chemical alerts

The Chemical alerts card has a single checkbox: Email me for chemical alerts. It’s on by default for every user. When enabled, AquaOps emails you whenever a new chemical alert is created for a location you can see — one email per chemical record’s worth of new breaches, summarizing every field that broke on that test. This is the same email_alerts_enabled preference and the same delivery behavior documented in Alerts: recipients are exactly the users who could already see the alert in-app (active users with chemical_records:view or org:manage, scoped to location), and email delivery is best-effort — if it fails or is skipped, the alert still appears in the in-app list regardless. Turning this off doesn’t hide anything from the Alerts list; it only stops the email.

Compliance digest

The Compliance digest card lets you choose how often you get a rollup email of compliance activity: Off, Daily, or Weekly. It’s off by default — this is opt-in, unlike chemical alert emails.

What it contains

Each digest summarizes, for the locations you have access to:
  • closure incidents opened in the period
  • closure incidents resolved in the period
  • closure incidents still open
  • corrective actions overdue
  • pool/days missing a required test
The email is a simple text summary of those five counts with a link back into AquaOps — it doesn’t list individual incidents. AquaOps only sends the digest when there’s actually something to report — a fully quiet period produces no email at all, so an empty inbox on a given day doesn’t mean the check didn’t run.

Frequency behavior

A daily cron job evaluates every subscribed user once a day:
  • Daily subscribers are eligible every run and get a digest covering the preceding 1 day.
  • Weekly subscribers are only eligible on Mondays and get a digest covering the preceding 7 days — not a running daily drip, one email a week.

Who actually receives it

Setting a frequency here isn’t enough on its own. The digest mirrors the same visibility rules as the in-app Compliance pages: you only receive it if you also hold compliance:view, compliance:manage, or org:manage. If you don’t hold one of those, you can still set a frequency here, but no email will actually go out. Content is scoped the same way the in-app pages scope it — org:manage holders get an organization-wide summary; everyone else’s summary is limited to the locations their role gives them access to. A user with a non-org:manage role and no location access at all is skipped entirely, even with a frequency selected. Like chemical alert emails, digest delivery is best-effort — if outbound email isn’t configured, no digests go out, silently, rather than the feature erroring.

Best practices

  • leave chemical alert emails on if you’re responsible for a location — it’s the fastest way to notice a new breach without keeping the Alerts list open
  • turn on the compliance digest (daily or weekly) if you’re accountable for closure incidents, corrective actions, or testing cadence but don’t check the Compliance module every day
  • choose Weekly over Daily for the compliance digest if you only want a periodic gut-check rather than a running drip — remember weekly digests only go out on Mondays
  • if you enable the compliance digest and never receive one, confirm you actually hold compliance:view, compliance:manage, or org:manage and have location access — the setting won’t error, it just won’t produce mail without that
  • don’t rely on the digest for anything time-sensitive; use the live Compliance module and Alerts list for that, and treat the digest as a periodic summary only

Suggested screenshots

  • the Notifications page showing both cards (Chemical alerts and Compliance digest)
  • the Compliance digest frequency dropdown open, showing Off/Daily/Weekly
  • an example chemical alert email
  • an example compliance digest email