Google Workspace

With Google Workspace, Gensy writes each employee’s Gmail signature through the API. Employees have nothing to install. From the Starter plan up.

What you need

• To be the owner of the Gensy workspace: only the owner can connect or disconnect the integration. Disconnecting doesn’t clear signatures already set in Gmail and blocks Gmail deployments afterwards: use Unpublish all before disconnecting.
• A super admin account on the Google domain.
• Nothing to enable in your own Google Cloud console: Gensy uses its own service account.
• Domain-wide delegation (Google Admin console → Security → Access and data control → API controls) granted to Gensy’s service account, with the gmail.settings.basic, gmail.settings.sharing and admin.directory.user.readonly scopes. The service account’s client ID isn’t shown in the app: ask support for it.

The Google installation guide, in the app, details each step.

Connect

1. Open Settings → Integrations.
2. Click Connect Google Workspace and sign in with the super admin account.
3. Google only asks for your identity: this screen grants no access to Gmail and no token is kept. Gensy checks that the account is a super admin and shows the connected domain; otherwise, the tab says why. Connecting Google doesn’t change the deployment mode.
4. In Deployment, switch to Automated deployment mode and click Deploy All.

Proof of admin rights

Gensy checks when you connect that the account is a super admin. This proof is valid for 30 days and renews on its own, at most once a day, with every deployment to Gmail (deployment, schedule, removal, daily campaign sync); with no Gmail deployment for 30 days, it expires. Four situations block Gmail deployments:

• the proof is missing;
• the proof has expired (30 days without a Gmail deployment);
• the account is no longer a super admin, or no longer the one that consented;
• the delegation is missing the admin.directory.user.readonly scope.

The first three are fixed by reconnecting Google Workspace with a super admin account. The fourth is added in the Google Admin console; the check then resumes on its own, without reconnecting. Each case is explained by a banner in the Integrations tab, and the refusal shows in the deployment’s error window; a schedule or the campaign sync also raises an alert.

What employees see

The signature appears in the employee’s Gmail settings, with no action on their part. Gmail keeps the pushed version until the next deployment or the daily sync. Google Workspace employees are confirmed directly by the Gmail API.

Multiple domains

This works if the domains are managed in the same Google Workspace admin console.

If something goes wrong

• Authorization refused (invalid_grant) — Google refuses Gensy’s service account: check domain-wide delegation and its scopes in the Google Admin console.
• Missing or incomplete delegation — add Gensy’s service account and its scopes in the Google Admin console (Domain-wide delegation).