Overview
The Opensense Google Add-on brings email signature management directly into Gmail. Users can view and update their signature fields without leaving their inbox, and changes sync immediately to Opensense. When auto-push is enabled, updated signatures are automatically pushed back to Gmail.
The add-on appears automatically in the Gmail sidebar once deployed by a Google Workspace Super Administrator—no individual installation or configuration required, and no propagation delay.
Key takeaway
The Opensense Google Add-on lets users view and update their signature fields directly in Gmail, with changes syncing immediately to Opensense and optionally pushing updated signatures back to Gmail automatically.
How it works
When a user opens the add-on in Gmail, it displays the signature fields from their Opensense profile. Users can edit unlocked fields and click Update Signature to save changes. Updates sync immediately to Opensense with no propagation delay.
.png?sv=2022-11-02&spr=https&st=2026-03-18T15%3A47%3A47Z&se=2026-03-18T16%3A01%3A47Z&sr=c&sp=r&sig=juDunsT6x3Nh1DWkizUfV74cR16FUDr1S4sjdHS9PGA%3D)
When a user updates an unlocked field and saves, the sync with the original data source (such as Google Directory or Okta) is broken for that specific field. This prevents the user's changes from being overwritten on the next automatic directory sync.
If auto-push is enabled for the user's group, the updated signature is automatically pushed to their Gmail signature settings. Depending on the group configuration, the signature appears as either a plain text preview (PTP) or a visual preview.
Alias support
The add-on supports users with multiple email aliases. When a Google Workspace admin assigns alternate email addresses to a user's profile, a dropdown appears at the top of the add-on allowing the user to switch between addresses and manage signature fields for each one.
Each alias has its own profile in Opensense. Profile data is shared across aliases except for the email address, which matches the selected alias. When a user switches aliases in the dropdown, the fields update to reflect the relevant profile and assigned signature template.
To enable alias support, ensure Sync Aliases is enabled in the Opensense portal under Manage > Domain Settings > Directory/Sync > Google Workspace.
Key features
Auto-push
Auto-push automatically updates the user's Gmail signature when they save changes in the add-on. This is configured per group in the Opensense portal under Manage > Groups. Each group can use one of two push types:
Plain text preview (PTP): Displays a tokenized text block in Gmail that transforms into the full HTML signature when the email is sent through Opensense routing. This ensures signatures always reflect the latest template design and prevents users from modifying signature content before sending.
Visual preview: Displays the full HTML signature directly in Gmail signature settings. Users see the complete signature before sending, but this method is more susceptible to becoming stale when templates are updated, and users can modify the HTML before sending.
Signature Fields Only
By default, the add-on displays all fields from the user's Opensense profile. When Signature Fields Only is enabled, the add-on filters the view to show only fields that exist in the user's assigned signature template. This keeps the interface focused and prevents confusion when templates use a subset of available profile data.
This setting is configured in the Opensense portal under Manage > Domain Settings > Google Add-on.
Custom Compose Fields
Custom Compose Fields allow administrators to add preset input options that appear in the add-on for users to select. These can be configured as dropdowns, checkboxes, or free-form text inputs. The selected values populate specific fields in the user's signature.
When a user updates a Custom Compose Field and clicks Update Signature, that field's sync with the original data source is broken to preserve the user's selection.
Custom Compose Fields require setup in both the signature template and user profiles. The fields must be added to the user profile to appear in the add-on, and integrated into the HTML template to display in the signature. Contact the Opensense onboarding team during implementation or Opensense Support (help@opensense.com) if you are already launched to ensure proper configuration.
This setting is configured in the Opensense portal under Manage > Domain Settings > Google Add-on.
Field locks
Administrators can lock specific fields to enforce compliance. Locked fields are visible in the add-on but appear greyed out and cannot be edited. This ensures required information like legal disclaimers or standardized job titles remain consistent across the organization.
Sync protection
When a user updates any unlocked field and clicks Update Signature, the sync with the original data source (such as Google Directory or Okta) is intentionally broken for that field. This prevents the user's changes from being overwritten on the next automatic directory sync.
This behavior allows organizations to maintain large-scale directory sync while supporting controlled exceptions for individual users who need to customize specific fields.
Deployment options
The add-on can be deployed organization-wide or limited to specific groups or organizational units (OUs). This allows IT teams to roll out the add-on gradually, target specific departments, or provide selective access based on business needs.
Troubleshooting
Most issues with the add-on can be resolved with these steps:
Refresh the Gmail browser tab.
Clear your browser cache and reload Gmail.
Sign out of Gmail and sign back in.
If the add-on displays an error or does not load after trying these steps, contact Opensense Support at help@opensense.com.
Opensense Support
For further assistance, contact Opensense Support:
Email: help@opensense.com
Knowledge Base: help.opensense.com