WiseStamp for IT › Google Workspace › Step 9 of 12 — Go-Live Checklist
What WiseStamp requires, and what we recommend beyond it: the product requirement to mark an integration live is a single test email from any active employee with an assigned signature. The pilot-and-rollout process below goes further on purpose; treat it as recommended IT acceptance practice rather than a product requirement.
Pre-go-live: configuration sign-off
☐ Google Workspace directory connected; expected employees imported (Connect Your Directory).
☐ Synced fields (title, department, phone) verified against the directory.
☐ Deployment method configured:
☐ Auto-Inject enabled (Auto-Inject into Gmail), and/or
☐ Server-side route + SMTP relay + content compliance rule configured and enabled (Server-Side Deployment).
☐ (Hybrid) Both configured; duplicate-prevention confirmed.
☐ (Platform/Enterprise) SSO configured and tested, if in scope (SSO with Google Workspace (SAML)).
☐ Signatures assigned (Primary Signature set; groups assigned where used).
☐ (Server-side) SPF includes WiseStamp; DKIM record added and signing enabled; relay IPs allowlisted.
Stage 1 — Pilot group
Pick 5–10 users across the environments you support: Gmail web, Gmail mobile app, and — for server-side — at least one non-Gmail sender (other mobile mail app or CRM).
For each pilot user:
☐ User set to Active in WiseStamp.
☐ (Auto-Inject) Signature present in Gmail > Settings > Signature, and on a new message.
☐ New email shows the correct signature.
☐ Reply behaves as expected.
☐ Forward behaves as expected.
☐ Renders correctly to internal and external recipients.
☐ Images/logos load and are correctly sized.
☐ No duplicate signature (if duplicated, check for a manual signature in Gmail settings — Troubleshooting Reference).
☐ (Server-side) Signature appears from a non-Gmail device.
☐ (Server-side) Authentication results show SPF and dkim=pass.
☐ (Dark mode) Signature legible in dark mode.
Validation matrix (record results)
User | Client/Device | New | Reply | Forward | Internal | External | Duplicates? | Notes |
Gmail web | ||||||||
Gmail mobile | ||||||||
Non-Gmail (server-side) |
Stage 2 — Targeting and rules check (if used)
☐ (Server-side rules) Each rule applies to the intended senders, email types, recipient conditions.
☐ Rule priority order produces the intended result when multiple rules match.
☐ Group-based signature assignment maps the right signature to the right group.
Stage 3 — Full rollout
☐ Enough seats available for all employees to activate (Ongoing Admin Guide).
☐ New employee initial status set to Active and Inject to Gmail on activation set to On, if you want automatic activation+injection (Auto-Inject into Gmail, Ongoing Admin Guide).
☐ Activate remaining employees (bulk: select > Set status > Active); confirm injection On where used.
☐ Send the employee handoff communication (Employee Rollout Handoff).
Stage 4 — Post-go-live monitoring (first 1–2 weeks)
☐ Watch for "no signature" / "duplicate signature" tickets; triage with Troubleshooting Reference.
☐ (Server-side) Confirm mail flow healthy; no delivery delays or rejections from routing.
☐ Confirm new hires in the directory appear in WiseStamp on the next daily sync.
☐ Confirm leavers removed from the directory are removed/deactivated on the next sync.
☐ Keep super admin access available for rapid response.
Rollback / safety
Server-side: if mail stops or is rejected, disable the content compliance rule to bypass routing, then contact support (Server-Side Deployment, Troubleshooting Reference).
Auto-Inject: set Injection Off (bulk or per user) to stop pushing signatures (Auto-Inject into Gmail).