Skip to main content
Activity & Alerts is one unified feed. Notification Preferences is where each user decides how that feed reaches them: which channels, which severities, which categories, and when the platform is allowed to interrupt them.
Preferences change delivery, not what gets recorded. Every event still lands in the feed and the Activity Log. Muting a category only stops the ping, not the record.

​
The delivery model

Every event has three attributes that decide whether you get notified:
  1. Severity - Info, Low, Medium, High, Critical (see the unified severity ladder)
  2. Category - Field Alerts, Weather, Scout, Tasks, VRA, Verification, Team
  3. Field / group scope - which fields the event belongs to
Your preferences map each combination to a set of channels. The defaults are safe for most users; override anything that does not fit your workflow.
Critical and High severities always deliver immediately on at least one channel, regardless of your other settings. Quiet hours, digests, and category mutes cannot suppress them. This is a platform-level guarantee for field safety and yield protection.

​
Channels

In-app is always on and cannot be disabled. It is your permanent record. All other channels are opt-in.

​
Default delivery matrix

These are the platform defaults. Every row is editable per user.

​
Setting up your preferences

1

Open settings

Click your avatar → Notification Preferences. Preferences are per-user, not per-estate.
2

Verify your channels

Confirm your email, phone number for SMS, and any connected Slack, Teams, or push devices. Unverified channels cannot receive Critical or High.
3

Adjust the severity matrix

For each severity row, tick the channels you want. Critical and High require at least one channel; the UI enforces this.
4

Configure category overrides (optional)

Some categories deserve tighter or looser routing than the severity default. Example: send every VRA lifecycle event to Slack for the ops room, but keep Team events in-app only.
5

Set quiet hours

Choose a start and end time in your local zone. During quiet hours, Medium and below hold until the window closes. Critical and High always deliver.
6

Choose digest cadence

Daily digest time and weekly digest day. Digests only include items below your immediate-delivery threshold.

​
Category overrides

Overrides let you route a single category differently from the severity default. Common patterns:
Category VRA → route all severities to #ops-room Slack channel. Individuals still get their normal severity routing on other channels.
Category Team and Scout completions → digest only on Saturday and Sunday. Field Alerts and Weather stay on the normal schedule so real risks still ping.
All categories → digest only, except Critical which routes to SMS. Result: one daily email plus SMS for anything urgent.
Rule card rice_blast → SMS on every severity for this user for the next 14 days. Everyone else keeps normal routing. Auto-expires.

​
Quiet hours

Quiet hours are a local-time window during which Medium, Low, and Info deliveries hold and release together when the window ends. Critical and High are exempt.
  • Default: 22:00 to 06:00 local
  • Weekend override: extend by up to 3 hours on Saturday and Sunday
  • Travel-aware: quiet hours follow the device time zone, not your home zone. If you land in a different region, the window shifts automatically.
If your role includes an on-call rotation, the platform disables quiet hours during your on-call window automatically. This is set by the estate admin, not by the individual user.

​
Digest schedule

Digests are AI-summarized rollups of everything below your immediate-delivery threshold. Digests link back to the feed for one-click drilldown. They never contain Critical or High items; those already delivered immediately.

​
Team and estate-level defaults

Estate admins can set recommended defaults for a team. New members inherit them on first login. Individuals can still override any row.
1

Open estate settings

Estate → Notification Defaults.
2

Set the recommended matrix

Adjust the severity × channel matrix that new members will start with.
3

Lock any rows (optional)

For compliance or safety, admins can lock specific rows so individuals cannot disable them. Example: lock Critical → SMS on for every user. Locked rows show a padlock icon in the user’s settings.

​
What preferences do NOT control

  • Whether an event happens - preferences never affect the risk engine, alert engine, or Activity Log.
  • What Verification captures - every operation still cross-checks. See Verification Model.
  • The unified severity ladder - severity is computed from the rule card, not from your preferences.
  • Compliance floors - locked rows and the Critical / High delivery guarantee override any user setting.

​
Troubleshooting

Check that your phone number is verified. Carriers occasionally reject long-form SMS; the platform falls back to a shortened link. If the failure persists, the platform automatically escalates delivery to Push and Email and shows a red badge in your settings.
The workspace token may have expired. Estate admin reconnects the workspace under Integrations. During disconnect, all Slack-only routes fall back to Email so you still get the message.
Move Info to weekly digest only, and consider muting the Team category if you do not manage other users. Info to weekly is the platform’s recommended baseline; the default is Info-in-app for transparency, not for volume.
Settings → Delivery Log shows every send, including channel, timestamp, and delivery receipt (where the channel supports one). Useful for confirming that a Critical alert reached you before an incident.

​
Guardrails

This module follows the shared guardrails template. The agent and every non-agent write path must respect these rules.