Alerts & Notifications
One rule governs every alert Fren One sends:
You are notified only about what you can access, at the same scope.
If a page is closed to you, so are its alerts. If a surface is open to you for only two channels, you're alerted only about those two. This applies to the workspace inbox, the notification bell, email and push.
Two filters, not one
Every alert passes two filters.
| Filter | Who sets it | What it does |
|---|---|---|
| Access (outer) | The workspace, through your level, grants and verifications | Decides what you're allowed to be told about. Mandatory. |
| Preferences (inner) | You, in Manage notifications | Decides what you want to be told about, from what's left. |
Your preferences can only narrow the set: you can't opt in to alerts about a surface you can't open. The workspace inbox is filtered the same way.
Who gets what
| Alert | Who's on the list |
|---|---|
| Moderation and channel health (raids, mass reports, agent removed, agent permission problems) | The verified admins of that specific channel, plus the Owner and Admins. Follows your verification, so it decays with it. |
| Ticket alerts (new tickets, ageing tickets, cross-channel queue activity) | The Owner and Admins, anyone holding + Tickets, and the verified admins of the channel the ticket belongs to. |
| X signals (opportunities, high-value mentions, follower moves, reputation risk) | The Owner and Admins, and anyone holding + X. A Member without + X gets nothing about X, in the inbox, the bell, or by email. |
| Workspace governance (billing, AI credit thresholds, access requests, member and channel state) | The Owner and Admins. |
| Discord channel purge reports | The Owner and Admins only. See Ignored Channels. |
| Everything covered by universal member read | Every workspace member. A channel admin gets these only for the channels they're verified on. |
| Personally addressed notifications (your invitation, a report someone shared with you, a nudge to re-verify) | You, regardless of what else you can see. |
Shared destinations: Slack, Discord and Telegram
Shared destinations (a Slack channel, a Discord channel, or a Telegram group or direct message) don't follow anyone's access level. Each delivers whatever the Owner or an Admin routed to it.
Whoever can read the Slack channel, Discord channel, group or chat can read the alert, so choose destinations for sensitive alerts carefully. See Integrations for how routing is configured.
When access changes
A change of access affects what happens next, not what already happened.
- Future delivery stops immediately. Remove a grant or let a verification lapse, and the matching alerts stop at once.
- Delivered history stays. Notifications already in someone's bell or already emailed are not retracted.
- Old links may land on a locked screen. A notification from before the change may link to something the person can no longer open. They'll see the ordinary locked page, or the request access screen.
When a verification pauses, you keep every read surface and every alert that follows your level. Only that channel's moderation alerts stop, until you re-verify.
Next steps
- Who Can Do What: the access the alerts are derived from
- Capability Grants: the grants, and what each adds to your alert list
- Integrations: routing alerts to Slack, Discord and Telegram