Deliver CentralCSP alerts by email to up to 10 workspace members. Recipient rules and what happens when members change.
Last update:
An email channel sends each alert to a list of 1 to 10 addresses. It is the only channel type with no platform-side setup; the constraint is on who can receive.
Prerequisites
- The website Manager role in CentralCSP.
- Every recipient must be a workspace member with access to the website. An outside address is rejected when you save.
1. Add the channel
- In the dashboard, go to Alerts > Configuration > Add channel.
- Name the channel and choose the Email type.
- Enter the recipient addresses, comma separated, up to 10.
- Save.
2. Test the channel
Select Test on the new channel. A sample alert built from a fake CSP violation is sent immediately. If it lands in spam, have recipients mark it as not spam before wiring real rules to the channel.
How recipients are resolved
Recipients are stored as workspace members, not as address strings, and resolved when each alert is sent. Two consequences worth planning around:
- A member who changes their email address keeps receiving alerts at the new one.
- A member who loses access to the website is silently dropped from the list. If nobody is left, the delivery fails.
For a distribution list, a shared inbox, or an on-call alias, email is the wrong type: use a Webhook channel or a chat destination such as Slack instead.
Next steps
- Create a rule that delivers to this channel.
- Channels overview for auto-disable behaviour and limits.
- Delivery history to audit what was sent.