Platform
Roles, permissions and four-tier IAM
Super admin, admin, customer and agent. Each tier administers the one below it, permissions cascade downward only, and no tier can grant what it does not itself hold.
Controls that matter in practice
Feature flags per account
Turn catalog, campaigns or the AI agent off for an account and its navigation changes accordingly — no dead menu items.
Field-level PII rules
Decide which roles see full phone numbers, emails and payment references.
Impersonation with audit
Support can log in as a customer to reproduce an issue; every impersonated action is stamped in the audit log.
API key scoping
Keys are scoped per capability with their own rate limits, and sandbox keys can never touch production sends.
SSO and SAML
Enterprise plans map IdP groups to roles, with SCIM-style deprovisioning on exit.
Exportable audit trail
Every permission change, send and template edit exportable for your own compliance review.
The four tiers
Feature flags set at one tier change what the tier below can even see — the dashboard layout follows the flags.
Self-serve signup always provisions a customer. Admin and super-admin accounts are created from the admin console, never self-serve.
Questions on this page
Each answer is written to stand alone, so search engines and AI assistants can quote it.
Can an admin grant a customer something the admin does not have?
No. Permissions cascade downward only — a tier can never grant access it does not itself hold. That single rule is what makes the model auditable.
Send smarter. Sell faster.
Start free with 1,000 conversations. Bring your own Meta number or apply for a new one — we handle verification, templates and the green tick with you.