Alerts
An alert rule watches a table for a condition, badges the records that match, and sends the alert. It is for the things nobody will notice by looking: a date coming due, a required value still missing, a record with no active link.
Alerts are different from Notifications, which tell you that something happened. An alert tells you that something is still true and needs attention.
Where to find it
| Screen | Where it lives | What it is for |
|---|---|---|
My alerts — /alerts | the sidebar | the open alerts for you, and your delivery preferences |
Alert rules — /admin/alerts | Settings → Data model → Alert rules | the rules themselves |
Viewing each needs its own permission, and both pages say so plainly when you lack it.
My alerts
Your open alerts, grouped and paged. Filter by Level, by Rule, by Past due, and Show snoozed to include the ones you have put off. Each alert names its rule and says how long it has been open.
Your delivery preferences
My alert preferences is where you choose how you hear about them:
| Setting | What it does |
|---|---|
| Channels per level | pick the channels for Info, Warning and Danger separately |
| Immediately or Daily digest | get each one as it happens, or one summary a day |
| Digest time | when the daily summary arrives |
| Quiet hours | a start and an end during which nothing is delivered |
| Record alerts | whether the alerts attached to records reach you |
Digest time and quiet hours use the space's scheduling time zone, not your browser's — so a digest arrives at the same local moment for everybody in the space.
Alert rules
Each rule has a Name, a Target (the table it watches), a Type (the condition), a Level, a Schedule, and an audience.
The condition types
| Type | What it looks for |
|---|---|
| Date coming due | a date field approaching |
| Value is missing / Value is present | an empty or filled field |
| Value equals / greater than / less than | a comparison |
| No active link | a record with no live link of some type |
| Advanced filter | the full AND/OR filter grammar, when none of the above fits |
| Required value missing | a system rule — see Required Data |
Level
Info, Warning or Danger. The level is what your channel preferences key off, so it decides how loudly an alert arrives, not just how it looks.
Who gets it
For everyone or Only for me. A rule can be Global (every space) or scoped to This space; a global rule can be overridden here or left inherited with use the space default.
Schedule, and running it now
The rule's schedule says how often it is evaluated — the row reads every N seconds. Last run says when it last happened. Run now queues an evaluation and tells you when the next check will be: evaluation queued; the next check is within N seconds. It never claims to have run instantly.
Enabling, snoozing, deleting
- Disable stops the rule without losing it.
- Snooze rule… silences it in this space for a chosen period or until a time you pick. The confirmation is explicit that this snoozes every alert from that rule in this space — not just the one in front of you. Un-snooze reverses it. A snooze needs a note, and there can be a maximum number of days (
0means no limit; empty inherits the space default). - Delete removes the rule and clears its open alerts — the confirmation says both.
The empty state explains the feature
A space with no rules does not show a blank page. It says what a rule is for: a rule watches a table for a condition — a date coming due, a missing value, a record without an active link — badges the records and sends the alert. The same is true of an empty alert list: alerts appear here when a rule finds something that needs attention.