> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.spreadly.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to Set Up Client-Side Email Signatures for Google Workspace

| Email signatures sync periodically every hour. Changes can take up to an hour to appear in Gmail.

Spreadly lets you automatically set email signatures to your Gmail clients for your whole Google Workspace domain from templates. This article shows you how to give Spreadly access to your Gmail settings and test the connection with a single user. Once the test works, you can make different signatures available to different groups.


**Before you start**
* You need to have your domain verified within Spreadly. See [Setup a verify domains](https://help.spreadly.app/en/article/setup-domains-gxztts/) on how to add your domains.
* You need Google Admin permissions to manage domain-wide delegation.
* Pick a test user in your Google Workspace domain. You'll use this account to confirm the setup before you roll it out.


## Copy the access details from Spreadly
1. Open the [email signature setup in Spreadly](https://spreadly.app/app/team/email-signatures/setup?method=client\&client=google) and go to the **Give Spreadly access** section.
![](https://storage.crisp.chat/users/helpdesk/website/-/6/1/b/6/61b64ab3334f9c0/bildschirmfoto-2026-10-26-um-1_11dau6h.png =290xauto)
2. Click the copy icon next to **Client ID** to copy the value.
3. Click the copy icon next to **OAuth scopes** to copy the value. It should read `https://www.googleapis.com/auth/gmail.settings.basic`.


## Add the client ID in Google Admin
|| Use the scope exactly as copied. Spreadly can only change the Gmail settings of your users. It cannot read any emails.

4. Click **Open domain-wide delegation** in Spreadly. Alternatively, go to **Security** → **API Controls** → [Domain-wide Delegation](https://admin.google.com/ac/owl/domainwidedelegation) in the Google Admin console.
![](https://storage.crisp.chat/users/helpdesk/website/-/6/1/b/6/61b64ab3334f9c0/bildschirmfoto-2026-10-26-um-1_23x2si.png =517xauto)
5. Click **Add new** in the **API clients** section.
6. Paste the copied value into the **Client ID** field. Leave **Overwrite existing client ID** unchecked unless you're replacing an existing Spreadly client.
7. Paste the copied scope into the **OAuth scopes (comma-delimited)** field.
![](https://storage.crisp.chat/users/helpdesk/website/-/6/1/b/6/61b64ab3334f9c0/bildschirmfoto-2026-10-26-um-1_1fmvnpx.png =433xauto)
8. Click **Authorize**.

## Test the access

9. Return to Spreadly and select the user in the **Test user** field you want to test the integration for.
10. Click **Check access**. Spreadly confirms when it can access the Gmail settings of the user.
11. Click **Push to test** to add the email signature to Gmail for this test user only.


| The signature is now active for your test user. Open Gmail as the test user and write a new email to see it. Once it works, you can assign signatures to groups as described in the related article below.


## Troubleshooting

#### Check access doesn't confirm access yet
Access can take a few minutes to take effect. Wait a moment and click **Check access** again. If it still fails, confirm that you pasted the Client ID and OAuth scopes exactly and clicked **Authorize** in Google Admin.


#### The signature doesn't appear in Gmail
Signatures sync every hour. Wait up to an hour, then write a new email. Make sure the test user is part of your Google Workspace domain.


## Related articles
- [How to Distribute Email Signatures](https://help.spreadly.app/en/article/how-to-distribute-email-signatures-clxutf/)