Skip to main content

Notification settings

The Settings → Notifications area is the tenant-level configuration for the notification system. Per-user preferences are at Notifications → Preferences.

/settings/notifications — Tenant settings​

Permission: notifications.settings.manage.

One form covering:

  • Tracking — open / click pixels (on/off)
  • Delivery mode — Capture (no outbound), Live (full outbound), Live allowlisted (outbound to allowlisted recipients only — used in staging)
  • Sender identity — From name and From address used on outbound mail
  • MX precheck — whether to verify recipient MX records before send
  • Body retention days — how long notification bodies are kept queryable for audit

Save / Reset buttons commit or discard changes.

/settings/notifications/activity — Message activity​

A searchable log of every message ever sent. Filter by recipient, type, date. Click a row to open a sheet showing:

  • Recipients
  • Delivery events (queued, sent, delivered, bounced, complained)
  • View body button — PII-audited, accessible only with the right permission
  • Resend — when the original send is recoverable

/settings/notifications/deliverability — Deliverability KPIs​

Permission: notifications.message.view.

7 / 30 / 90-day windows of email deliverability metrics:

  • Total sent
  • Delivered
  • Bounced
  • Complaint rate
  • Click rate

Plus a top-bouncing-templates table and a daily volume area chart. Use when investigating "why isn't my notification arriving" complaints.

/settings/notifications/policies — Delivery policies​

Role-based notification delivery defaults. The table shows each category with:

  • Always-on flag — locks the category for opt-out (employees can't disable)
  • Roles / channels covered

Four baseline always-on categories ship with FrontLine and cannot be unlocked: compliance_approvals, auth_security, legal_hr, compliance_required. Custom policies can be added for tenant-specific categories.

/settings/notifications/suppressions — Suppression list​

The bounce / complaint suppression list synchronised with the upstream email provider. Per row: email address, reason (Bounce, Complaint, Manual), date added.

  • Auto-entries are protected — they require a force flag to remove (because deleting an auto-suppression typically just causes the next send to bounce again).
  • Manual entries can be added (e.g., a recipient who asked to never be contacted).
  • Delete prompts for confirmation.