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 one of your API keys is created or revoked. |
| 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. |
| 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.
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 and password resets;
- 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.