WiseStamp for IT › Google Workspace › Step 1 of 12 — Setup Overview
Audience: IT manager / system administrator. You will need Google Workspace super administrator rights for most setup steps.
The deployment methods
WiseStamp applies signatures either client-side (before send) or server-side (after send). You can combine them (hybrid).
Client-side options
Option | What it does | Best for | Plan |
Google Workspace App + Auto-Inject | Admin deploys the WiseStamp app to the domain; signatures are pushed directly into employees' Gmail settings the moment they’re activated | Organization-wide client-side rollout | Basic+ |
Chrome Extension | Per-user browser extension; supports multiple signatures; works in Gmail and Outlook web | Users who need multiple signatures or browser-based control | All plans |
Google Connect | OAuth connection that inserts one signature into one Gmail account | Individuals; one signature per Gmail address | All plans (incl. Legacy Free) |
Server-side
Server-side (Gmail routing) | |
When applied | After send, in transit through WiseStamp’s cloud |
Coverage | All devices and clients (desktop, mobile, web, CRM) — nothing installed for users |
What you configure | A send route + SMTP relay + content compliance rule in the Google Admin Console |
Plan | Platform or Enterprise |
Hybrid
Hybrid runs client-side and server-side together. The client-side signature applies first; the server-side service only appends a signature when it does not already detect a WiseStamp signature, preventing duplicates. Hybrid requires Platform or Enterprise.
Which method should I choose?
Need signatures on every device and client (mobile, CRM, non-Gmail senders) with nothing installed per user? → Server-side. Platform or Enterprise.
Want centralized client-side deployment that writes the signature straight into Gmail for all staff? → Auto-Inject via the Google Workspace App. Basic+.
Need both Gmail-visible signatures and guaranteed coverage everywhere else? → Hybrid. Platform or Enterprise.
Just individuals or a few users, or on a plan without server-side? → Chrome Extension (multiple signatures) or Google Connect (one signature, one account).
Trade-off: server-side guarantees coverage and removes per-user dependencies, but routes outbound mail through WiseStamp and requires Gmail routing + compliance-rule changes. Auto-Inject avoids mail-flow changes but only covers Gmail (the signature lives in the user’s Gmail settings).
Plan requirements at a glance
Capability | Minimum plan |
Google Workspace integration + Auto-Inject | Basic |
Chrome Extension / Google Connect | All plans |
Auto-sync employee details from directory | Basic |
Server-side deployment + signature rules | Platform |
Single Sign-On (SAML) | Platform |
Roles & permissions | Platform |
See Google Workspace IT Admin Guide for the full tier matrix.
Order of operations
Confirm prerequisites — Google Workspace setup, plan tier, super admin rights, network/IP allowlist and DNS (for server-side). → Prerequisites Checklist
Connect your Google Workspace directory — imports and syncs employees. Required for centralized deployment. → Connect Your Directory
Deploy signatures using your chosen method:
Auto-Inject (client-side) → Auto-Inject into Gmail
Server-side via Google Workspace → Server-Side Deployment
(Optional, Platform/Enterprise) Configure SSO for admin sign-in. → SSO with Google Workspace (SAML)
(Optional) Scope which employees sync by OU/department. → Scope Employee Sync
Activate employees and validate. → Go-Live Checklist
Hand off to employees and move to ongoing operations. → Employee Rollout Handoff, Ongoing Admin Guide
Key dependency: connecting the directory does not by itself put signatures on email. You must also enable Auto-Inject and/or configure server-side.
What WiseStamp accesses on your domain
Google Workspace App (directory + Auto-Inject): installed domain-wide from the Google Workspace Marketplace; used to import employees, sync details, and inject signatures into Gmail.
Google Connect: per-user OAuth to write the signature into that user’s Gmail settings.
WiseStamp states its Google integration adheres to the Google API Services User Data Policy, including Limited Use requirements.
The exact Google OAuth scopes are confirmed — see Permissions Reference.