Notifications
Notifications
The Notification Settings page is the place to decide who in your organization (or outside it — accountants, ops contractors, the on-call inbox) receives automated emails from e-bon, and which categories of notifications each address gets. It is org-wide: the list applies to the whole organization, not to your individual user. There are no per-user mute controls and no SMS or web-push channels — email is the only channel and the recipients are configured here.
Open Notification Settings
Open the Portal sidebar and choose Settings → Notifications. The page lives at /portal/settings/notifications and renders the SettingsNotifications component.
GET /api/v1/org/settings/notifications and PATCH /api/v1/org/settings/notifications both require Owner or Admin and return 403 Forbidden for the Operator role. If the Settings → Notifications entry is missing from your sidebar, ask your organization owner to grant you the right role.Choose notification categories
e-bon groups every automated notification it sends into one of five categories. Each subscriber chooses any subset of these — including all five or none — and only receives the categories they are subscribed to.
| Category | What it sends |
|---|---|
| Reports | Z report summaries and overdue alerts. |
| Alerts | Device offline and paper-low notifications. |
| Billing | Invoice generation and payment status updates. |
| Device Events | Device status-change notifications. |
| Analytics | Weekly sales digest and analytics rollups. |
The category set is fixed — you cannot add custom categories from the Portal. For programmatic, real-time event push (e.g. “fire a webhook on every receipt.created”) use Webhooks instead; webhooks and notification emails are independent and can run in parallel.
Add a subscriber
Type an email address
The Email address field sits at the top of the page (placeholder email@company.com). It is validated client-side against a standard email regex: invalid addresses surface “Invalid email address.” on submit; an address that is already on the list shows “This email is already added.” The address is normalised to lowercase before being stored.
Click Add recipient
The button is disabled while the field is empty; pressing Enter in the input has the same effect. The new subscriber appears immediately in the Notification Subscribers card below, subscribed to all five categories by default. You can also add multiple addresses one after another before saving.
Fine-tune the categories
Each subscriber renders as a card with the email at the top and a grid of five checkboxes — one per category — under it. Tick or untick to opt the subscriber in or out of that category. The label and the short description of each category sit next to the checkbox so you do not have to remember what “Alerts” means versus “Device Events”.
A small ghost button All categories at the bottom-right of each card toggles the whole set on or off in one click — handy when you want a recipient to receive only Billing or only the weekly Analytics digest.
Click Save changes
Nothing is sent to the server until you click Save changes at the bottom of the card. The success toast “Notification settings updated.” confirms the persist; failures surface a red banner with a Retry button at the top of the card.
400 Validation error. If you want to fully unsubscribe an address, remove it instead of unticking every category.Remove a subscriber
Click the small × at the top-right of any subscriber card to start the removal flow. A confirmation modal opens with the line “<email> will no longer receive notifications.” and two buttons:
- Cancel — closes the modal, the subscriber stays.
- Remove — removes the subscriber from the in-memory list. Note: the change is not yet persisted at this point — you still need to click Save changes at the bottom of the card to commit the removal to the API. Closing the page without saving discards every unsaved add, edit and removal.
If you remove a subscriber by accident, hit your browser Back button or refresh before saving and the original list is reloaded from the server.
Migrate legacy Z-report emails
Older organizations that pre-date the subscriber model used a single zReportEmails list — a flat list of addresses that received Z report emails only. The first time you open this page on such an org, the API auto-migrates that legacy list: every email becomes a subscriber with all five categories enabled. The migration is read-only until you save — no records are written until you click Save changes, so you can review and trim the auto-subscribed addresses first.
Continue with related settings
- Webhooks — push real-time events (
receipt.created,device.offline,report.generated, …) to your own HTTPS endpoints. Use webhooks for machine-to-machine integration; use the notification settings on this page for human inboxes. - Organization — company name, billing address and locations.
- Profile — your personal account, password, role badge.
- Billing & plans — manage the organization’s subscription. Billing-related emails are governed by the Billing category above.
- API keys — credentials POS partners and external systems use to call the e-bon API.
Locations
Manage every shop, restaurant or office in one place — add locations, assign devices, compare performance and give each manager scoped access from the e-bon Portal.
Fiscal operations
Plain-language guide to fiscal receipts, X and Z reports, ANAF artifacts, cash operations and storno reversals — and where each one lives in e-bon.