Overview
Deploying a signature pushes it to users' Gmail accounts using the Gmail Settings API via Domain-Wide Delegation. Users do not need to do anything — the signature appears in their Gmail automatically.
Info
Deployment uses Google's Gmail Settings API. SignatureHQ writes to the Default signatureslot in each user's Gmail settings. Existing manually-set signatures are overwritten for affected users.Creating assignments
Before deploying, you must tell SignatureHQ who should receive a given signature. Open a signature and click Deploy → Manage Assignments.
There are five assignment target types:
Everyone
All users in your domain. Use as a catch-all default.
Organisational Unit (OU)
All users in a specific Google Workspace OU, e.g. /Sales.
Google Group
All members of a specific Google Group.
Custom Group
Your own user groupings, created in SignatureHQ independently of Google.
Individual user
A single specific user. Highest priority.
Priority rules
A user can match multiple assignments. SignatureHQ uses the highest-priority match:
| Type | Priority |
|---|---|
| Individual user | 100 |
| Custom Group | 75 |
| Google Group | 50 |
| OU | 25 |
| Everyone | 0 |
Tip
Use Everyone as your base assignment, then add OU or Group assignments for departments that need a different signature. The most specific rule wins.Running a deployment
- 1Open a signature and click Deploy.
- 2Review assignments and the estimated user count. The Deploy button is disabled if no assignments are configured, then enables automatically as soon as you add an assignment.
- 3Click Start Deployment. SignatureHQ queues per-user jobs and processes up to 10 at a time.
- 4A live progress bar appears. You can navigate away — the deployment continues in the background.
Monitoring & errors
The dashboard shows a 7-day deployment trend chart. For per-deployment details, click any deployment in the history table to see individual user results.
- Success — signature was written to the user's Gmail account
- Skipped — user's winning assignment points to a different signature
- Failed (403) — DWD is not configured or the user is outside your domain — check Settings → Workspace
- Failed (429) — Gmail API rate limit hit — SignatureHQ retried automatically with exponential backoff