On this page
Mute or snooze alert rules for yourself, author threshold rules on the organization's own datasets, and choose where thresholds for the shipped rule packs are changed.
For: organization owners and admins. Before you start: you hold the
manage_org_settingscapability, and the organization has at least one data source running — a rule pack only appears for a data plane the organization actually runs.
Steps#
- Open Settings > Alerts & brief ("Cài đặt > Cảnh báo & bản tin") at
/settings/alerts. The page lists, per data plane the organization runs, the rules in that plane's default pack. - For any listed rule, mute it so it stops reaching you, or snooze it for 24 hours or 7 days. There is no channel picker on this page, for yourself or for the organization: a rule an admin authors cannot choose transports on behalf of its members. Every member links their own channels and sets their own per-type preference at Settings > Notifications, covered in step 5.
- Create an alert rule on one of the organization's own confirmed datasets: pick the dataset, the measure, an optional breakdown and brand, how to judge it (the value in the month, or the change versus the previous month), the comparison operator and the threshold, then name the rule. This is the one threshold control on this page. A shipped rule pack's own threshold is changed in the playbook rule editor instead — a threshold change there requires a stated reason and is versioned. See Marketing playbooks.
- Confirm which external channels are even available. An owner or admin cannot turn on a channel nobody has configured, or one the platform operator has not allowed for this organization — ask the platform operator to enable it first; see Notifications.
- Every member, including an owner or admin, links their own channels (web push, email, Telegram, Zalo) and sets their own per-type preference at Settings > Notifications ("Cài đặt > Thông báo"),
/settings/notifications. There is no org-wide override of another member's inbox.
Verify#
- The rules listed on
/settings/alertsmatch the data planes the organization actually runs. - A muted or snoozed rule stops reaching you; an unmuted one resumes at its next evaluation.
- A rule created on the organization's own dataset appears in the list and fires the next time its dataset refreshes and the condition is met.
When something is wrong#
| Symptom | Likely cause | Fix |
|---|---|---|
| The morning brief item does not appear in the menu | The organization's active data planes have no reader declared yet, or an admin removed the menu item for the role | See "Morning brief item is missing" in Troubleshooting. |
| A rule you expect to see is missing from the list | The organization does not run the data plane that rule belongs to, or has not yet synced data on it | Connect the relevant source; the rule pack appears once the plane is active. |
| Muting a rule seems to stop it from ever firing | Muting only silences notification, not evaluation | The rule is still evaluated and recorded as fired — it is just not sent to you. |
| A channel is greyed out with a reason attached | The channel is not configured at the platform level, not allowed for this organization, or not yet linked by you | Read the stated reason; each is fixed in a different place — platform, organization, or your own account. |
| You cannot find a channel picker on this page | Channels are never chosen here, for a rule or for a person | Link a channel and set its per-type preference at Settings > Notifications (step 5). |
| You cannot find a threshold control for a shipped rule pack | Shipped rule-pack thresholds are edited in the playbook rule editor, not here | Open Marketing playbooks; to set a threshold on your own dataset, use step 3's form instead. |