This article explains how shared mailboxes work with Templafy Email Signature solutions.
Prerequisites
|
Overview
A shared mailbox (or shared inbox) is a mailbox that multiple users can use to read and send email messages. A typical use case would be a support@company.com mailbox. Typically, a shared mailbox is delegated to a user through the Office 365 Admin Center. This allows users to automatically get shared mailboxes in their Outlook client by being authenticated with their own user. In some cases, shared mailboxes are manually added by the users with the shared mailbox credentials.
Solutions
The support for shared mailboxes within Templafy is complex and depends on the requirements of the organization. A crucial differentiation is if the organization needs users to get the User Profile of the shared mailbox or if they need a separate email signature design for the shared mailbox. In some cases, they might need both. Per this, Templafy provides the two solutions below to work with Shared Mailboxes.
Solution A - Additional User Profiles
Prerequisites
|
Rely on additional User Profiles that includes the information related to the secondary mailbox (shared mailbox), set up manually by the end-user.
- Add the additional User Profile.
- Switch to the right signature based on the profile related to the sending mailbox.
Multiple User Profiles can be created if there are multiple shared mailbox signatures.
NoteIf a specific template for the shared mailbox is required, a dropdown field in the User Profile can also be used to get the design of a shared inbox synchronized into Outlook. The advantage of this method is that it allows the user to create multiple User Profiles with different shared signatures. |
Below is a breakdown of advantages and disadvantages of Solution A - Additional User Profiles:
Advantages
- Allows for the user to have many different shared inbox signatures by creating multiple profiles.
- Provide flexibility to have different signatures for the end users to personalize the signature of the shared mailbox based on the sending user.
- Also allows to cover the use case of Executive assistants sending on behalf of their attached executive.
Disadvantages
- Relying on the end user to set these signatures up from their User Profiles.
- It requires manual user action to select the related profile based on the sending mailbox set.
Solution B - Signature Based on the Sending Mailbox
Prerequisites
|
The email signature server can be used to attach email signatures for shared mailboxes. Per this, the signatures will be added based on the sending mailbox. The downside being that users won't see previews of their email signatures or be able to switch between signatures, and all the shared mailbox users must be provisioned into Templafy, onboarded, and have the O365 signature enabled for them.
NoteTemplafy Email Signature Add-ins can be deployed for this solution; however, the user would have to manually delete the signature of their default profile in an e-mail composition/reply to allow Email Signature Server to stamp the shared mailbox signature.
|
Below is a breakdown of advantages and disadvantages of Solution B - Signature Based on the Sending Mailbox:
Advantages
- Works on all devices by simply using the From email to determine signature to use.
- (If no add-ins are deployed) Fully automated without having the end user needing to select anything themselves.
Disadvantages
- Requires deployment of Templafy Email Signature Server.
- No email signature preview for the shared mailbox.
- All shared mailbox users must be provisioned into the Templafy tenant and have a valid User Profile.
Use Cases
It's possible to have a hybrid setup where some users will be relying on the solution Additional User Profiles and others relying on the solution Signature Based on the Sending Mailbox.
- For Executive assistants, it's better to use the Additional User Profiles solution as it allows them to switch between signatures based on the emails sent.
- For users sending from system mailboxes, it's better to use the Signature Based on the Sending Mailbox solution as it allows them to automatically get the right signature based on the mailboxes used without having to switch manually between profiles.
- For enforcing the shared mailbox signature automatically with less flexibility for the end users, it's better to use the Signature Based on the Sending Mailbox solution.
- For providing the flexibility to the users to insert the dedicated shared mailbox specific signature semi-automatically, it's better to use the Additional User Profiles solution.
"Send on Behalf" Emails
The Outlook permission, "send on behalf", allows a delegate to send a message from a mailbox or group (the From address looks like this: <Delegate> on behalf of <MailboxOrGroup>
). In order to attach the Templafy email signature of the <MailboxOrGroup>
, only Solution A above can be used.
Accessing Shared Mailboxes Using Email Signature Web Add-in
Automatic insertion of email signatures is not possible on shared mailboxes using the Email Signature Web Add-in. Automatic insertion refers to getting a signature without interacting with the Templafy Email Signature task pane. The following dialogue will appear if a shared mailbox is opened:
Clicking on Insert signature will open the Templafy Email Signature task pane as shown below. The logged in user's signature will then be inserted to the email. Solution A can then be used to switch the signature to use a different user profile:
If another user then logs in to the shared mailbox, they will see the signature of the first logged in user. This is because the shared mailbox is authenticated through the first logged in user and automatic authentication is not supported. In order for the second user to use their own signature, they must interact with the Templafy Email Signature task pane and log in. Then, Solution A can be used for the second user.
NoteThe VSTO Email Signature Add-in stores email signatures locally in Outlook, allowing for automatic insertion within shared mailboxes. |
Comments
Article is closed for comments.