Admin & feature-change alerts
When one admin changes something significant — flips a feature, edits security policy, changes who has access — every other admin gets an email about it in real time. It's how a team of admins stays honest with each other without anyone having to watch the activity log.
Who gets notified
An alert goes to every other active admin of the organization — Principals, IT Admins, and any Enterprise Admin over the org (one level up, e.g. the diocese that owns the school). The admin who made the change is never emailed about their own action.
- Enterprise admins are looped in. If a diocese admin edits one of its schools, that school's local admins hear about it — and vice-versa, a local change is visible to the diocese. Enterprise reach is a single parent hop; an enterprise two levels up isn't notified.
- Pending invitees are skipped. An enterprise admin who hasn't accepted their invitation yet won't receive org-change alerts until they do.
- It never blocks the change. Alerts are sent in the background — if email delivery hiccups, the admin's action still goes through and nothing breaks. You'll just have missed that one notification (the change is still in the activity log).
What triggers an alert
Two kinds of change fire an email. Settings changes arrive as a before → after table (⚙️ in the subject); access changes arrive as a plain sentence (👤 in the subject).
Feature & security toggles
- Features: AI email analysis, Online Kindness, Password Manager (and its MFA requirement), Require-MFA-for-all, automatic campaigns (and pausing / auto-approving them), enterprise-controls-campaigns, Public Hall of Fame, login-email-change alerts, link-check policy, community-alert threshold, and simulated vendor services.
- Security settings: link-check policy, domain monitoring, the weekly spoof scan, and dark-web scan frequency.
- Key staff / leadership: the Principal, faith leader, business manager, IT contact, or front-office names and titles (plus the Principal's and IT contact's email) — so you hear when someone, including an enterprise admin, edits your org's setup.
Who-has-access changes
- The primary admin is transferred, or steps down.
- A member is promoted into or out of an admin role (Principal / IT Admin / Enterprise Admin).
- An admin's fine-grained permissions change.
- A role is removed from someone, or a member is deactivated.
- The Org Reporter instant-alert permission is granted or revoked.
- An enterprise administrator is added or removed over the org.
What the email looks like
The subject names the change, the org, and who did it — e.g. "⚙️ AI email analysis toggled at St. Mary's (by Jane Doe)" or "👤 Primary admin changed at St. Mary's". The body shows exactly what changed (a from → to table, or a one-line summary), a Review the activity log button, and a link to manage your notification preferences. Deactivating someone who held several roles at one org sends a single alert, not one per role.
Turning it on or off
These alerts are on by default. To change that, go to Admin → Platform Features → 🔔 Notifications, and under Report activity emails toggle "Admin & Feature Changes."
- Preferences are per-organization. If you administer more than one org, set them separately for each.
- Opting out anywhere wins. If you hold several admin roles and turn the alert off under any one of them, you stop receiving that org's alerts — a single "off" is respected everywhere.