Google Workspace email signatures

Connect your organization's Google Workspace account so you can manage email signatures from Lynkle Teams.

Before you start

• A Lynkle Teams subscription with organization owner access.
• A verified Google Workspace domain with Gmail enabled.
• A Google Workspace super admin. This can be you, or someone you send a setup link to.

You can connect before creating cards. To create signatures, each person needs an existing public Lynkle card; pending cards and invitations are excluded.

Choose how to connect

In Lynkle, open Cards > Email signatures, select Connect email provider (or Manage connections), then select Connect beside Google Workspace. Lynkle asks Are you a Google Workspace super admin?

If another email provider is already connected, this window lists only connected providers. Open Settings > Integrations > Email signatures and select Manage connections instead.

• If you are, connect it yourself.
• If you aren't, send a setup link to a super admin.

Connect it yourself

1. Choose Yes, I'll set it up

   Lynkle shows a Client ID and an OAuth scope, each with a copy button.

2. Add Lynkle in Google Admin

   Select Open Google Admin. Under Manage Domain Wide Delegation, select Add new, paste the client ID and the scope, then select Authorize. If you can't find the page, select Show me where in Lynkle. If multi-party approval is on, another super admin must approve it.

   The scope to paste is:

   https://www.googleapis.com/auth/gmail.settings.basic
3. Sign in with Google

   Return to Lynkle and select Sign in with Google. Use your super admin account and approve the requested access.

4. Check the connection

   Google Workspace shows Connected with your domain.

Send a setup link to a super admin

1. Choose No, share a setup link

   Select Create setup link.

2. Copy and send the link

   Copy the link and send it to a Google Workspace super admin in your organization. They don't need a Lynkle account.

3. Wait for Connected

   Google Workspace shows Waiting for super admin until they finish. You'll get an email when it's connected.

A setup link expires 30 days after you create it and works once. To find it again, select View setup link beside Google Workspace. Select Cancel link to stop it working. To send a different link, select Cancel link, then Create setup link.

For super admins: complete a setup link

1. Open the link

   The page shows who asked you and which Lynkle team will be connected.

2. Add Lynkle in Google Admin

   Copy the client ID and scope from the page. Select Open Google Admin, select Add new, paste both values, and select Authorize.

3. Sign in with Google

   Select Sign in with Google and use your super admin account. When you see All set, you're done.

Google calls this permission domain-wide delegation. It lets a super admin authorize access without asking each team member to connect individually. The authorization covers your Workspace organization for that scope, not just cards selected in Lynkle. See Google's delegation guidance for details.

What access does Lynkle request?

There are two separate permissions:

Only enter the full Gmail settings scope shown above in the delegation entry. The read-only user permission is requested separately during sign-in; do not add it to that delegation entry.

Lynkle's connection check confirms the super admin's primary Gmail send-as address, or yours if theirs can't be checked and yours is in the same domain, without changing it. It does not create cards or enable directory synchronization. See Google's Gmail scope descriptions, Directory scope descriptions, and Gmail address lookup.

You do not need to create a Google Cloud project, create a service account, or provide Lynkle with a private key. Use the client ID displayed in Lynkle.

Choose your cards

Follow Team email signatures to select cards, customize a shared design, and deploy to Gmail. Use primary Gmail mailboxes in the exact domain shown on your connection; secondary domains are not supported by this connection. Each card keeps its own person's details. Pending cards and invitations are excluded, and mailbox suggestions must be verified before deploying signatures.

Rename the signature in Gmail

Gmail may label the installed signature My Signature. Lynkle can update its content, but Google's supported API does not expose a signature-name setting.

To use the Lynkle card handle as the name, open Gmail on the web, go to Settings > See all settings > General > Signature, and select the installed signature. Click the edit icon beside its name, enter the card handle shown in Lynkle, and select Save Changes at the bottom of Gmail settings. See Google's signature instructions.

Remove signatures

In Email signatures, select the cards, then select Remove signature (or Remove N signatures) and confirm. For each mailbox Lynkle deployed to, it sets the primary Gmail signature to empty and stops managing it.

If Gmail cannot be updated, Lynkle still stops managing the signature and lists the affected mailboxes. Clear those signatures in Gmail under Settings > See all settings > General > Signature.

Disconnect or reconnect

Open Email signatures, select Manage connections or Connect email provider, then open Manage beside the connected Google Workspace account, select Disconnect, and confirm with Disconnect email signatures. Lynkle keeps your cards and saved designs, but pauses the mailbox assignments. Existing Gmail signatures remain in place, and Google contact sync stays connected.

To reconnect, reopen that panel (or Settings > Integrations > Email signatures if another provider is connected) and select Connect beside Google Workspace. Then choose Yes, I'll set it up and select Sign in with Google as a super admin from the original domain, or send a new setup link. Reconnecting does not publish signatures or resume paused assignments. Review and deploy them again to resume management. You cannot switch an existing connection to a different domain.

Disconnecting in Lynkle does not remove Google's delegation entry or revoke your Google authorizations. If your super admin also wants to revoke access in Google Admin, review the exact client and any other integrations using it first.

Troubleshooting

• Domain-wide delegation is missing or Gmail access is rejected: check the delegation entry in Google Admin. Its numeric client ID must match Lynkle, and its scope must be https://www.googleapis.com/auth/gmail.settings.basic. Complete any required approval from a second super admin.

• You cannot find the client ID: open Cards > Email signatures > Connect email provider (or Manage connections). In the Email providers window, select Connect beside Google Workspace, then choose Yes, I'll set it up. If Google Workspace isn't listed, use Settings > Integrations > Email signatures instead. The number appears under Client ID.

• Google rejects the client ID: copy the number under Client ID in Lynkle. Do not paste an email address, Google Cloud project ID, or the ID from a Google sign-in screen.

• The connection fails after authorization: check the exact scope and any second super admin approval. Google says changes can take up to 24 hours.

• The setup link says it has expired or is no longer valid: the link was used, cancelled, replaced, or is older than 30 days, your team connected directly, or the person who sent it is no longer an active Lynkle Teams owner. Create a new setup link and send it again.

• The setup page says "Open the setup link again to continue.": open the original setup link again in the same browser, then sign in.

• Sign-in says your team is already connected to another domain: sign in with a super admin from the domain shown in the message.

• Sign-in says Lynkle couldn't check Gmail access: make sure Gmail is turned on for the super admin's account, or for the person who sent the link if their account is in the same domain.

• The Google Workspace connection button is unavailable: contact Lynkle support. You do not need to create your own service account.

• Your existing signature has not changed: choose Review and deploy, confirm the mailbox, and deploy the signature. Connecting and previewing alone do not publish it.

• Google blocks sign-in or access: ask your super admin to review Lynkle under Google's third-party app access controls. Delegation and sign-in approval are separate.

• The connection expires or reports an invalid request: reopen Lynkle's connection panel and start again in the same browser. Complete sign-in within five minutes; do not reuse an old callback link.

Connected confirms the setup check completed. It does not mean signatures have been deployed or every team mailbox has been verified.