Deploy signatures to Gmail with Google Workspace

With Google Workspace deployment, CloudCard writes each person’s signature directly into their Gmail settings. Nobody has to copy and paste.

Before you start

• You need to be a CloudCard admin of the organisation.
• A Google Workspace admin for your domain needs to install the CloudCard Email Signature Management app from the Google Workspace Marketplace.
• The people who should get a signature need the Email Signature role in CloudCard. See Email Signature users and seats.
• Gmail must be turned on for those people in the Google Workspace Admin console.

1. Open the Google Workspace page

1. In the left-hand menu, click Company Settings.
2. Click Email Signature, then click Automated Signature Deployment. This takes you to Integrations, filtered to Email Signature.
3. On the Google Workspace card, click Set up Marketplace app.

2. Connect Google Workspace

The page shows two steps under Set up Gmail signature deployment.

1. Click Install from Google Workspace Marketplace and install the CloudCard Email Signature Management app for your domain. You need to be a Google Workspace admin to do this.
2. Back in CloudCard, click Connect & complete OAuth. Sign in with Google and allow CloudCard to manage Gmail signatures.

When the connection works, you return to the page with Connected next to Google Workspace. CloudCard checks the connection with one of your eligible users. If something isn’t set up yet, a message starting “Connected to Google, but the Marketplace app is not fully set up” explains what’s missing.

3. Deploy signatures

1. Under Signature template, choose the template to use.
2. Click Deploy Gmail signatures.

CloudCard queues a signature for everyone with the Email Signature role and shows how many were queued. The counts at the top of the page update as each one is processed: Eligible users, Queued, Deployed, Failed and Skipped.

Gmail signatures are a snapshot. When someone’s card or your signature settings change, click Deploy Gmail signatures again to update everyone.

Read the Deployment Log

The Deployment Log lists each person, their Gmail address, the template and the result.

• Queued: waiting to be sent to Gmail.
• Deployed: the signature is now in that person’s Gmail.
• Failed: Gmail didn’t accept it. The Last error column says why. Fix the cause, then click Retry on that row.
• Skipped: CloudCard didn’t try, because the person is inactive, is no longer in the organisation or no longer has the Email Signature role. The status names the reason.

A common failure is “Gmail is not enabled for this Workspace account”. See Gmail signatures fail with “Mail service not enabled”.

Disconnect Google Workspace

1. At the top of the Google Workspace page, decide whether to tick Also remove deployed Gmail signatures.
   • Ticked: CloudCard clears the signature from everyone it deployed to.
   • Not ticked: existing signatures stay in Gmail.
2. Click Disconnect and confirm.

The Deployment Log is cleared when you disconnect.

Still stuck? Contact support.