Ana MNotifications
Integration model

Stable contracts. Replaceable providers.

Ownership and access

Resource Responsibility
Organization Integrator namespace, shared templates, provider defaults and settings.
Tenant Isolated recipients, messages, sender connections, drafts and overrides. Tenant identifiers do not encode application roles or subscription plans.
Backend API key Scoped to organization or tenant. Tenant headers use explicit ref:, id: or slug: forms.
Browser grant Short-lived, recipient/principal/resource-bound capability. Never substitute a backend key in your product frontend.

Templates and numbers

Shared organization templates are defaults. Tenant versions are explicit overrides. A message pins the selected version, sender connection and encrypted credential revision at acceptance. A later edit cannot rewrite a message that was already accepted.

Connect the provider account and number separately from publishing a template. Readiness, approval, activation and default selection are distinct states. Unsupported rich template types fail explicitly. SMS needs no Meta approval; WhatsApp template rules depend on the channel/provider.

Reliability

Durable PostgreSQL jobs and an outbox run through the same service runtime locally and in production. Use idempotency keys per intent, source versions to fence stale changes and revision checks for updates. Do not retry uncertain external writes with a new key. Read current state before reconciliation.

Observe queued → sent → delivered/read, as supported by each provider, or explicit failure/suppression. SMTP acceptance does not imply inbox delivery. An email-open pixel does not prove human reading.

Simulation versus delivery

The console reads modes from the authenticated capabilities endpoint. fake delivery uses the same routing and durable API with simulated delivery adapters; it does not prove external delivery. Controlled testing may send real traffic only to explicitly allowed contacts.

Sender management calls are real even when message delivery is fake. Previewing a draft is local rendering; creating/submitting a provider template contacts that provider. The console requires confirmation before mutations and identifies these operations.

Operations and privacy

/healthz checks process liveness; /readyz checks readiness. Neither proves a worker processed a delivery. Operator metrics use their separate collector authentication. Logs, traces and Sentry use technical codes and correlation IDs, never message text, contacts, grants or provider secrets.

The console keeps backend credentials only in memory, uses no analytics and masks secrets in displayed responses. Disconnect before sharing the screen. Production consumer applications should expose only their authorized backend and resource-bound browser APIs.