Routed Key Behaviors and Nuances

Prev Next

Overview

This section outlines important nuances and configurations for the Opensense Outlook Add-in, covering stamping, permissions, domain behavior, add-in deployment, and multiple signature selection. These details help optimize functionality and avoid unexpected issues when using Opensense across different scenarios.

Key Behaviors & Nuances

  • Stamping with Field Edits enabled

    • If the Outlook add-in is being used only to remove signatures while also allowing field edits, and you are also using stamping, the plaintext block in the Opensense Stamping mail flow rule will need to be adjusted.

Note

Any field in the stamping block that users can edit should be excluded from the plaintext block. (i.e., name, title, etc.)

  • Permissions on shared accounts

    • Any account linked to the primary account will automatically inherit permissions, enabling the add-in to function when switching the From address.

      • Note: if the mailbox is accessed directly, it must be explicitly added to the add-in's scope.

  • Sending As vs Sending on Behalf when routing through a solution like Opensense:

  • Domains not used with Opensense

    • If they switch to domains that are not within Opensense, and they do not want their current signature value to stick when they switch, please enable the add-in domain setting Clear Signature If No Domain.

  • Non-clickable preview for Plaintext Customers

    • If you use a plaintext block ONLY deployment, it will automatically insert a non-clickable visual preview of what the recipient will see. No setting is needed for this. See the example below.

  • Add-in is not centrally deploying to M365, or the application is no longer available in their Outlook

    • Download the manifest file:

    • Manually install the add-in:

Multiple Signature Selector

Opensense Support

For further assistance, contact Opensense Support:

  • Email: help@opensense.com

  • Knowledge Base: help.opensense.com