Email notifications
The email notifications Beliq sends, their defaults, who receives them, and how to unsubscribe. Managed per user in the dashboard.
Beliq sends two kinds of email: account-critical mail that always goes out, and optional notifications you control per category. You manage the optional ones in the dashboard under Settings, at /o/{orgSlug}/settings. Preferences are saved per user, so they follow you across every organization you belong to.
Notification categories
| Category | Default | Who receives it |
|---|---|---|
| Security alerts | On | You, when you create or revoke an API key. Turning them off sends you one notice. |
| Quota warnings | On | Org owners and admins, at 80% and 100% of the monthly quota. |
| Webhook health | On | Org owners and admins, when a webhook endpoint is auto-disabled. |
| Failed requests | Off | Org owners and admins who opt in. Flood-controlled. |
| Ruleset changes | On | Org owners and admins, when a breaking change lands on a validation ruleset your organization has used recently, and before a retained ruleset version it still runs stops being served. |
| Billing updates | On | The org owner: renewals, receipts, and plan changes. |
| Product updates | Off | You, when you opt in. Occasional product news. |
Two of these follow you personally (security alerts and product updates); the rest are per organization and reach the owners or admins of each org who have them enabled. Billing updates go to the org owner.
Security alerts are addressed to whoever performed the action, not to whoever holds the key. An admin who revokes a developer’s key is the one who gets the mail. Keys that a membership change revokes send no mail at all: removing a member, or changing their role so they can no longer create keys, revokes the keys they created, and that is recorded in the organization’s audit log under Settings. The owner and admins read it there.
The ruleset changes notice is how a breaking-change announcement from ruleset versioning reaches you by mail. It goes out once the new ruleset is serving, only to organizations whose documents were validated against the outgoing ruleset in the last 180 days. It says what requests without a Beliq-Ruleset header run against now, given your organization’s default channel, and it names the exact Beliq-Ruleset header value that pins the outgoing ruleset.
The same category brings two reminders before a retained ruleset stops being served, 60 days and 14 days before its last day. They go only to organizations whose documents were validated against that retained version after its successor took over. Each says what happens after the last day: an exact pin on the version returns an error, and the previous channel validates against the current ruleset instead.
Account-critical email always sends
Some mail is not a preference. Beliq always sends it regardless of your notification settings, because it concerns access to or the state of your account:
- sign-in codes, password resets, and the notice that your password changed;
- a notice when security alerts go from on to off, with the subject “Security alerts were turned off for your Beliq account”, so you hear about it even if someone else turned them off;
- the confirmation code for deleting your account;
- organization invitations;
- payment failures and subscription changes (ended or suspended).
These carry no toggle. Everything in the table above does.
Unsubscribing
Account-critical email has no unsubscribe, since turning it off would mean missing a password reset or a failed-payment notice.
Managing your preferences
- Open the dashboard and go to Settings (
/o/{orgSlug}/settings). - Under Email notifications, toggle any category.
- Changes save immediately and apply to your account everywhere.
Related
- Webhooks: the delivery mechanism behind webhook-health alerts.
- Authentication: API keys, whose creation and revocation trigger security alerts.
- Team and roles: the owner and admin roles that scope org-level notifications.