Connect Google Workspace to SignStampd
A Google Workspace super administrator must approve access in the Google Admin console. Review the steps and permissions here before you start. Personal @gmail.com accounts are not supported.
You can try the signature builder without signing in. Connecting your directory is only needed for team deployment.
What access are you granting?
Read your user directory
https://www.googleapis.com/auth/admin.directory.user.readonlySignStampd uses directory names, job titles, email addresses, organizational units, and administrator status to manage team signatures.
Manage basic Gmail settings
https://www.googleapis.com/auth/gmail.settings.basicSignStampd uses this permission to update the signature on a user's primary sending address. Google grants access to basic Gmail settings more broadly; this is not a signature-only permission.
These scopes do not grant access to read email messages or send mail. SignStampd does not route messages through its servers. Domain-wide delegation applies across the domain; selecting an organizational unit in SignStampd controls deployment, not the underlying Google authorization.
Google's Gmail permission reference · How SignStampd handles data
Set up and test one signature
- Sign in with your Workspace super administrator account. The dashboard displays SignStampd's service account Client ID and the two scopes above.
- Open the Google Admin console. Go to Security → Access and data control → API controls → Manage Domain Wide Delegation. Choose Add new, paste the Client ID and scopes from the dashboard, then authorize.
- Return to SignStampd and verify the connection. Google says authorization changes can take up to 24 hours, though they usually take effect sooner. Your organization may require a second super administrator to approve the change.
- Choose and customize a template. Check that names and titles in your directory are current. Save a copy of your existing Gmail signature before testing; SignStampd replaces the current signature field.
- Apply it to your own account first. Select one user on the Push page, apply the template, then check the result in Gmail on the web and send a test message. Check signature defaults if it does not appear when composing.
- Roll out to the team. Select the intended users or organizational units and review push results. Enable auto-apply if you want new hires in the selected scope to receive the template on the daily sync. Existing users need a new push when you change their template.
Before you choose a paid plan
- The trial lasts 14 days from account setup. No card is required and it does not charge automatically.
- Subscriptions cost $2 per Workspace user per month. Checkout uses the synced directory count, not only the people selected for a signature push. Review the count on Billing before subscribing.
- Gmail mobile behavior can differ when a user has set a separate mobile signature. Test your team's devices before rollout.
- These are editable Gmail signatures. Use an appropriate compliance solution if you need to enforce a footer on every outgoing message.
Help and removing access
For setup questions, email admin@signstampd.com with your team size and where you got stuck. Do not send passwords or service account keys.
To revoke access, remove the SignStampd client entry from Domain Wide Delegation in the Google Admin console. This stops future updates; it does not restore signatures already applied. Cancel a subscription separately through SignStampd's Billing page.
Start your 14-day trial