Clients
Recent activity
| When | Client | Who | What |
|---|
Tenant
Everyone in the Google tenant with an address in these domains is managed. Each Gmail "send mail as" address in these domains gets its own signature.
Service account key
No key uploaded.
One-time Google setup for this tenant
- In console.cloud.google.com, create (or pick) a project and enable Gmail API and Admin SDK API.
- IAM & Admin → Service Accounts → create one, then Keys → Add key → JSON. Upload that file above.
- In the tenant's admin.google.com: Security → Access and data control → API controls → Manage Domain Wide Delegation → Add new.
Client ID:(upload key first)
Scopes: - Wait a few minutes, then click Test connection.
- In INKY, set Email Signatures → Layout → New mail: None (INKY keeps replies and forwards). Use layouts with no images for replies and forwards so they don't attach anything.
New-email signature
Gmail adds this to new emails only (Google doesn't let admin tools set reply/forward signatures). Replies and forwards keep INKY's text signature.
Edit HTML template
Variables: {{name}} {{firstName}} {{lastName}} {{title}} {{department}} {{email}} {{displayEmail}} {{phone}} {{phoneDigits}} {{mobile}} {{mobileDigits}} {{company}} {{website}} {{websiteUrl}} {{address}} {{imageUrl}} {{imageWidth}} {{tagline}}. Optional block: {{#phone}}…{{/phone}}.
Preview (sample person)
Go-live lock
This tool sets the new email signature in Gmail. INKY keeps doing replies and forwards. Pushing stays blocked until INKY's new-mail signature is off for the people you push to, or they'd get two signatures on new emails.
Users
Names, titles and phones come from the Google directory. Click a row to override them for that person. Suspended users are skipped.
| Name | Addresses | Title | Work | Mobile | Status |
|---|
Results
Backups
Before every push, each person's existing Gmail signature is saved here. Restore puts them all back.
| When | Signatures |
|---|