Google Workspace integration overview (change request)

Overview

This article is a high-level overview of the steps to integrate Opensense with your Google Workspace environment. The integration needs Super Admin privileges, and includes five key elements for proper setup. For how signatures flow through Opensense, see How does Opensense work with Google Workspace?

Not a step-by-step guide

Work with your dedicated Implementation Engineer, or contact help@opensense.com, to complete the integration.

Integration components

The integration of Opensense with your Google Workspace environment requires:

1. Installing the Opensense Google Workspace Marketplace app
2. Setting up the Opensense Google API smart host
3. Setting up the Opensense Content Compliance rules
4. Setting up the Opensense loopback relay
5. Updating DNS entries

Opensense Google Workspace Marketplace app

The app enables:

• Single sign-on with Google for Opensense administrators
• Centrally pushing employee email signatures into Gmail, including replacing existing signatures
• Sourcing user data for email signatures (name, title, phone, and so on) from Google Directory

For the API scopes the app uses, see Google Workspace API scopes.

Smart host and loopback relay

Setting	Opensense Google API smart host	Opensense loopback relay
From	Google Workspace	Opensense
To	Opensense	Google Workspace
Transport	TLS-encrypted smart hosting	TLS-encrypted SMTP relay
Purpose	Applies centrally managed email signatures to in-scope emails	Delivers in-scope emails through the normal mail flow, after Opensense applies the signatures

Content Compliance rules

Rules let you scope the solution to specific users, groups, organizational units, and even specific emails. Only emails in scope trigger the Opensense Google API smart host and get Opensense-applied email signatures. A dash means that the rule has no such condition.

Rule	Opensense Enabled	Opensense Stamping
Contains the Opensense token [[+]] in the bodyApplies when	Yes	—Not listed
Sent by an in-scope user, group, or organizational unitApplies when	—Not listed	Yes
Doesn't contain the header value Opensense applies with a signatureApplies when	Yes, to avoid double signatures	Yes, to avoid double signatures
Isn't a Google notificationApplies when	Yes	Yes
Effect	Triggers the Opensense Google API smart host for signature application, and sets a message header	Applies the Opensense token through Google's disclaimer feature, enforcing Opensense signatures on all emails for in-scope users. Then triggers the smart host, and sets a message header.

Updating DNS entries

Opensense customers must update the required DNS entries in both external and internal DNS, if applicable. This ensures brand continuity, and improves deliverability. See Required DNS settings for Opensense.

What’s next

• How does Opensense work with Google Workspace?: how email flows through Opensense.
• Google Workspace API scopes: what the Marketplace app can access.
• Required DNS settings for Opensense: the DNS entries to add.

For further help, contact Opensense Support at help@opensense.com.