Agency
Agency tenant isolation: what the API denies
On the MAILTIG Agency plan each client is a separate tenant. Automated probes denied cross-tenant reads, changes and deletes. Whitelabel is plan-gated.
By MAILTIG editorial. Reviewed by Engineering (Tenant isolation) on 5 November 2026. Next review due 4 February 2027. 6 minute read.
Each MAILTIG client is a tenant. Contacts, mailboxes, campaigns, inbox and credits do not leak across workspaces. That is how the Agency plan is built.
What stays inside a tenant
Users, role assignments, sending identities, lists, sequences, threads and credit balances belong to one workspace. An agency portfolio can look across tenants it owns. It cannot mix sending identities.
On 4 November 2026 an automated cross-tenant probe denied every read, change and delete aimed at another workspace. That is an internal check, not an independent audit.
What the Agency plan adds
Client workspaces, role templates, monthly snapshots and whitelabel require the Agency plan. Whitelabel covers product name, logo, colour, support email and a custom host when the feature is on.
There is no shared sending pool between clients. If you need one mailbox to send for several clients, that is a process mistake MAILTIG will not paper over.
What this is not
Tenant isolation is not SOC 2. It is not a penetration test. The security page lists those reviews as outstanding. Isolation here means the API refused the probe we ran.