Introduction
This article outlines how to integrate Opensense with your Google Workspace environment. This integration requires Super Admin privileges and consists of five (5) elements necessary for proper setup.
Integration Requirements
The integration of Opensense with your Google Workspace environment requires the following:
Installation of the Opensense Google Workspace Marketplace application
Set-up of the Opensense Google API smart host
Set-up of the Opensense Content Compliance Rule(s)
Set-up of a Opensense Loopback relay
Update DNS Entries
Installation of the Opensense Google Workspace Marketplace Application
The application enables:
Single Sign-On with Google for Opensense administrators
The ability to centrally push employee email signatures in Gmail (including replacing existing signatures)
Sourcing user data for email signatures (name, title, phone, etc.) from Google Directory
Set-up of the Opensense Google API Smart Host
Enables TLS-encrypted smart hosting of emails from Google Workspace to Opensense to apply centrally managed email signatures.
Set-up of the Opensense Content Compliance Rule(s)
Rules allow the solution to be scoped to specific users, groups, organizational units, and even specific emails. Only emails in scope will trigger the Opensense Google API smart host and have Opensense-applied email signatures.
First Rule: Opensense Enabled
This rule will only apply if:
The email has the Opensense token in the body:
[[+]]The email does not contain a header value applied by Opensense when a signature is applied (eliminates the opportunity for double signatures)
The email is not a Google notification
If the email matches all of the above conditions, it will trigger the Opensense Google API smart host for signature application and will set a message header.
Second Rule: Opensense Stamping
This rule will only apply if:
The email is sent by an in-scope user, group, or organizational unit
The email does not contain a header value applied by Opensense when a signature is applied (eliminates the opportunity for double signatures)
The email is not a Google notification
This rule will apply the Opensense token via Google disclaimer functionality, enforcing Opensense signatures on all emails for in-scope users.
If the email matches all of the above conditions, it will trigger the Opensense Google API smart host for signature application and will set a message header.
Set-up of the Opensense Loopback Relay
Enables TLS-encrypted transport of in-scope emails via SMTP relay from Opensense back to Google Workspace. Emails are delivered through the normal mail flow process after Opensense applies email signatures.
DNS Entries Update
Opensense customers are required to update the following DNS entries to both external and internal DNS (if applicable). This ensures brand continuity and improves deliverability.
Required DNS Settings for Opensense
Opensense Support
For further assistance, contact Opensense Support:
Email: help@opensense.com
Knowledge Base: help.opensense.com