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 administrator account with an active Gmail mailbox. Lynkle uses that account's primary Gmail address to check delegated access.

You can connect before creating cards. To create signatures, each person needs an existing public Lynkle card; pending cards and invitations are excluded. Keep Lynkle open in the same browser while completing Google sign-in.

Connect Google Workspace

1. Open your email signature connections

   In Lynkle, open Cards > Email signatures. Above the card list, select Connect email provider. If you already have a provider connected, select Manage connections instead.

   A window titled Email providers opens. It contains a Google Workspace row and a Microsoft 365 row. You do not need to select any cards first.

2. Copy the Google client ID

   In the Email providers window, select Connect on the right of the Google Workspace row. This expands the setup instructions inside the window; it does not start Google sign-in yet.

   Under the label Google client ID, you will see a long number with a copy icon beside it. Select that copy icon. This is the ID you will paste into Google Admin in the next step. The OAuth scope appears directly below it with its own copy icon. Leave this window open and select Open Google Admin to open Google Admin in a separate browser tab.

   If the row says Reconnect, select that button to reveal the same setup instructions. If it says Connected and shows your correct domain, setup is already complete; go to Choose your cards.

   If the number is missing or the window says This provider is not configured, contact Lynkle support. You do not need to find or create an ID in Google Cloud.

3. Authorize Lynkle in Google Admin

   Sign in to Google Admin as a super administrator. Open Security > Access and data control > API controls > Manage Domain Wide Delegation, then select Add new. If that client ID is already listed, review its existing entry instead of adding a duplicate.

   Paste the client ID from Lynkle. Copy the OAuth scope from the Lynkle window and paste it into OAuth scopes in Google Admin:

   https://www.googleapis.com/auth/gmail.settings.basic

   Select Authorize and check that the saved entry contains the correct client ID and scope. If multi-party approval is enabled, a second super administrator must approve the request. Wait for authorization to finish before starting the Lynkle sign-in step.

4. Sign in with your administrator account

   Return to the Lynkle browser tab. In the expanded Google Workspace section of the Email providers window, select Connect Google Workspace in step 2. Google sign-in continues in the same browser tab. Use the primary email address of your Workspace super administrator account to sign in, then review and approve the requested access, including read-only user information. Lynkle checks your administrator status and confirms that Gmail delegation works.

5. Check the connection

   When Lynkle confirms the connection, select Return to email signatures. Open Manage connections and check that Google Workspace shows Connected with the correct domain. Connecting does not deploy or change signatures.

Google calls this permission domain-wide delegation. It lets an administrator 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 reads the administrator's primary Gmail send-as address 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, select Connect or Reconnect, then Connect Google Workspace using a super administrator from the original domain. If the connection shows Reconnect needed, use Reconnect. 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 IT team 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 second-administrator approval.

• You cannot find the client ID: open Cards > Email signatures > Connect email provider (or Manage connections). In the Email providers window, select Connect or Reconnect beside Google Workspace. The number appears under Google client ID only after that section expands.

• Google rejects the client ID: copy the number under Google 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-administrator approval. Google says changes can take up to 24 hours.

• The administrator's mailbox cannot be verified: use the super administrator's primary email address and confirm that Gmail is enabled for that account.

• 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 Workspace administrator 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.