Recipient groups
A standing distribution list with a To or Cc role per member, two sources for a member, and what the system checks before it deletes a group.
A recipient group is a standing distribution list. A scheduled report references the group rather than copying from it — so adding a person to the group changes every report that uses it immediately, without opening any of them.
It lives in settings, under Recipient groups, and is restricted to administrators.
A group member
| Field | Note |
|---|---|
| Name | Optional |
| Email address | An address or a phone number is enough — not both |
| Phone | A member with only a phone is a recipient like any other; the number is normalized to the international format on save |
| Role | To or Cc |
| Channels | Email, SMS, WhatsApp |
The same person cannot be both "To" and "Cc" in one group.
A member with no contact details for a selected channel is marked on screen: they will be skipped on send, and the skip is recorded.
Two sources, and the difference is kept
A member comes either from a search in the directory service, or from manual entry — for an address the directory does not hold: a shared mailbox, an external party, a distribution list. The group remembers which of the two each member came from, because it has to be able to say which of its addresses nobody can re-verify.
Deletion
Before the confirmation dialog opens, the screen asks the server which scheduled reports reference the group, and lists them by name.
If the check itself could not run — because there is no database connection, for instance — the screen says so explicitly instead of showing a reassuring zero. A group vanishing under a report that keeps running and mails nobody is exactly the failure this screen exists to prevent.
How a group is used is covered in Scheduled reports.
Updated
This page is the file content/docs/en/v1/report/recipient-groups.mdx