Enterprise email signature management, from security review to purchase order
This page is for the people who have to approve the purchase rather than use the product: security, legal, procurement and the administrator who will own it afterwards. It says what exists, what is in the agreement, and how the rollout is planned at this size.
Sample company
Blocks
| Group | Mailboxes | Status |
|---|
Security and identity
What the security review will ask about
- SSO with SAML against your identity provider, so access follows joiners and leavers automatically.
- User provisioning with SCIM, including deprovisioning the same day someone leaves.
- Custom roles beyond the standard marketing and IT split, mapped to how your organisation divides the work.
- Scoped permissions inside your own tenant, listed in your admin console and revocable by you.
- Message bodies are never read, never stored and never routed through AutoSignature.
- Audit export of every administrative action, into your own logging or archive.
- A choice of data residency region, written into the agreement.
- Penetration test summary on request, and support through your own security questionnaire.
What is in the contract
- A signed data processing agreement with the sub-processor list.
- A 99.9 percent uptime SLA with service credits.
- Invoicing and purchase orders, on annual or multi-year terms.
- Named contacts on both sides and an agreed escalation path.
Scale of deployment
What changes above 600 mailboxes
- Unlimited mailboxes, unlimited brands and entities, unlimited template sets.
- Approval workflow before any template or banner reaches production.
- API and webhooks driven by HR events, so joiner, mover and leaver changes arrive without a human in the loop.
- Rollout history kept for a period you choose rather than a fixed one.
- Dedicated onboarding with a named contact through the first rollouts.
A rollout plan at this size
- Week one: connect the tenant in a read-only pass as the how it works page describes, map directory fields, find the people whose records are incomplete.
- Week two: design and approve the template set with brand and legal in the room once, not five times.
- Week three: deploy to a pilot group of one department, read the result in every client, adjust.
- Week four: widen by group, country by country or entity by entity, with rollback available at every step.
At this size the directory work, not the software, is usually what takes the time, which is why the first pass is read-only.
The questions a group of companies asks
- Several entities, one console: each entity has its own template set, its own disclaimer rule and its own brand.
- Several countries: disclaimer text and language follow the country, and the group structure follows your directory.
- An acquisition mid-year: the acquired company's tenant connects alongside yours, on either platform, before any migration.
- Agencies and managed service providers administering client tenants use the multi-tenant console.