# Email signature connection checklist

Use this checklist to connect your email provider and customize signature previews. Connecting does not deploy a signature or install an Outlook add-in.

## Before you connect

- [ ] You are a Lynkle Teams organization owner with an active subscription.
- [ ] Before creating signatures, the people you want to include have existing public Lynkle cards.
- [ ] Each card contains that person's work email address.

## Google Workspace

Follow the [Google Workspace guide](/docs/teams/email-signatures/google-workspace).

- [ ] Your Workspace super administrator has Gmail enabled.
- [ ] Open Cards > Email signatures > Connect email provider (or Manage connections). In the Email providers window, select Connect beside Google Workspace. Copy the number under Google client ID using its copy icon.
- [ ] Select Open Google Admin. Go to Security > Access and data control > API controls > Manage Domain Wide Delegation > Add new. Paste the Google client ID and copyable OAuth scope shown in the Lynkle window, then select Authorize.
- [ ] Complete any required second-administrator approval.
- [ ] Return to Lynkle and select Connect Google Workspace. Continue in the same browser tab, use the super administrator's primary email address and review the requested access, including read-only user information.
- [ ] After confirmation, select Return to email signatures. Open Manage connections and confirm Google Workspace shows Connected with the correct domain.

## Microsoft 365

Follow the [Microsoft 365 guide](/docs/teams/email-signatures/microsoft-365).

- [ ] Your organization uses Microsoft 365 with Exchange Online.
- [ ] Your administrator has an active Global Administrator role.
- [ ] Select Connect beside Microsoft 365, then Connect Microsoft 365 and complete administrator sign-in.
- [ ] Continue through the permission approval and installation steps.
- [ ] Select Approve Outlook sign-in and grant the signature retrieval permission for the tenant.
- [ ] Download the Outlook add-in manifest and deploy it to the intended users through Microsoft 365 Integrated apps.
- [ ] In the studio, choose Microsoft 365 and publish signatures to verified primary mailboxes. Keep the page open until every card shows a result.
- [ ] Compose a new HTML message as a selected user and check the signature. Ready for Outlook and Inserted in Outlook are separate states.

## Customize your signatures

Follow [Team email signatures](/docs/teams/email-signatures).

- [ ] Select the existing cards you want to include.
- [ ] Choose a shared layout, colors, border, elevation, and visible details.
- [ ] Review each person's preview and resolve any contact-detail choices.
- [ ] Remember that previewing does not save or deploy signatures. Deploying replaces each selected card's saved email signature design.
- [ ] Refresh previews if more than 30 minutes have passed.

Manage email signatures and contact sync separately in Lynkle. Disconnecting email signatures keeps your cards and saved designs, but pauses mailbox assignments. Contact sync stays connected. After reconnecting, review and deploy the signatures again. Reconnecting Microsoft 365 also stops new Outlook insertions until you republish. Signatures already installed in Gmail or inserted into messages remain unchanged.

## Deploy to Gmail

- [ ] Check the live previews, then select Review and deploy.
- [ ] Confirm each primary Gmail mailbox in the exact Workspace domain shown on your connection. Secondary domains are not supported by this connection.
- [ ] Confirm any existing-assignment replacement explicitly.
- [ ] Keep the page open until every card shows a result. Check for the Deployed status.
- [ ] Open a new message in Gmail on the web to check the result.
- [ ] If deployment fails, correct the issue and return to the design and select **Review and deploy** again.