One email platform for the whole network

Headquarters keeps control of the brand. Every franchise, store or entity sends from its own isolated workspace — its own contacts, domain and sending reputation.

See the live interface See licences

The problem with one shared account

A network usually ends up with one of two bad options. Either every entity shares one marketing account — one badly targeted campaign can damage the sending reputation of the whole network, and nobody can tell who sent what. Or every entity buys its own tool — headquarters loses the brand, the templates and any common view of what is being sent.

Notifuse is built for the middle: one deployment, many isolated workspaces, governed from the centre.

Headquarters sets the frame

Templates and their translations are prepared centrally, so every entity sends on-brand email in its own language. Permissions decide who can do what in each workspace: a local manager runs their campaigns, headquarters keeps the settings and the integrations.

Each workspace has its own database, contacts, campaigns and custom domain for tracking and unsubscribe pages. Entities do not see each other's data.

Store A

emails.store-a.com

Store B

emails.store-b.com

User Permissions
Grant access by feature
Contacts
Read
Write
Broadcasts
Read
Write

One entity's mistake stays its own

With Amazon SES tenant isolation, each entity can send under its own reputation and suppression list. A campaign that goes wrong in one store can be paused there — it does not take the rest of the network down with it.

And because workspaces are isolated, a local team can be given exactly the access it needs, and no more.

An example

Illustrative scenario — not a customer case.

A retail network with 40 locations deploys Notifuse once, on its own servers. Headquarters prepares the templates and the two languages the network uses. Each store gets a workspace with its own contacts and its own domain, and sends its local campaigns. Headquarters can see the frame it set; stores cannot see each other's lists. When the network grows past the workspaces in its licence, it moves to a Custom licence instead of changing tools.

Access is governed with single sign-on and granular permissions, and admin actions are kept in audit logs. Details are on our security page.

Licences for networks

Start free with three workspaces. Studio covers five, Agency and Enterprise fifteen — with permissions, SES tenant isolation and template translations, plus single sign-on and audit logs on Enterprise. More than fifteen workspaces, or a network-wide rollout? That is a Custom licence, quoted per deployment.

Paid licences include private email support, Monday to Friday — first reply within two business days, one when production is blocked.

Compare licences