Opensense seamlessly integrates with Google Workspace to deliver secure, dynamic, and consistently branded email signatures—without requiring end-user configuration or disrupting the native Gmail experience. Our platform leverages Gmail’s native Content Compliance routing and signature injection capabilities to provide flexibility, control, and scale for organizations of all sizes.
Google Workspace Signature Deployment Methods
1. Signature Stamping via Gmail Content Compliance
Opensense uses Gmail’s Content Compliance engine to route qualifying emails through our cloud platform, where signatures and banners are applied automatically and securely—after the user sends their message.
How it works:
A Global Admin sets up a Content Compliance rule targeting specific users and/or groups.
When a qualifying user sends an email, Gmail routes the message to Opensense over TLS encryption.
Opensense:
Adds the correct HTML email signature and marketing banner (if applicable)
Appends a custom header to prevent duplicate processing
The modified message is securely returned to Gmail and delivered to the recipient by your corporate email server.
Users see no difference in their Gmail interface—signatures are applied post-send and are consistent across all devices and clients (web, mobile, third-party apps).
2. Plain-Text Signature Injected into Gmail Settings
Opensense also supports injecting an editable plain-text signature block directly into each user’s Gmail settings using the Gmail API. This version of the signature appears in the Gmail compose window and is automatically used at send time.
Edits are only accepted for unlocked fields within the Opensense portal. If changes are made to a locked field within the plain text block, those changes will be rejected in the transformation of the email signature.
Two ways this can be deployed:
Self-Service (MySig): Users visit a personalized URL (e.g. smart.opensense.com/mysig) to input their data manually and save as it their signature wherever they send email.
Opensense Gmail Pusher Tool: Opensense can be used to push the plain-text block to the user’s Gmail signature settings.
This method:
Inserts a patented plain-text block with the users data pre-populated
Reflects directory values (name, title, phone, etc.)
Allows custom fields for user input (pronouns, certifications, etc.)
Ensure perfect placement of the signature
Key Features
Centralized control of email signatures without user effort
Dynamic fields populated from Google Directory (name, title, department, etc.)
Patented plain-text signature block with real-time update capability
No inbox access—Opensense never stores or reads email content
Compatible with all email environments (web, mobile, and third-party apps)
Works with both stamping and/or Gmail settings injection depending on your use case
Opensense Google Workspace Architecture
Messages flow securely through Gmail and Opensense with no change to original delivery path or user experience.
Opensense Support
For further assistance, contact Opensense Support:
Email: help@opensense.com
Knowledge Base: help.opensense.com