Unable to use sender across more than one account

Hi Ron,

Unfortunately, for on-premise installations (7.2 version equals to 11.25 SaaS), an email can't be reused in multiple accounts. Because the email is used to uniquely identify a sender, and a sender can only be a member of one account. Imagine the scenario when a sender received a pending transaction, it would be tricky which inbox will receive it if the email belongs to multiple accounts.

Based on the foregoing, you can consider to create an alias email address to use in the other account: [email protected] when normal is [email protected].

If we focus on the latest SaaS environment 11.35, then the Sub-Account feature might be a potential solution for this "sender across multiple accounts" use case, where multiple accounts with different settings and customizations can be merged as sub-accounts under a main account. Senders, as long as be granted with roles with certain permissions, can logically be associated with multiple sub-accounts.

Duo

Hi Duo,

Thanks for your reply that helps answer our question.  But it does lead me to an alternate question.  If we have had a single account in operation for a couple of years, and to that account we have added hundreds of senders, is it possible to remove those senders from that account?  Or will it prevent us from doing so if they have transactions associated with them?

The reason I am asking this is our business line has contemplated a workaround where we assign a fixed email address as the default sender on all transactions going forward on that old account and then on our new account we take advantage of being able to specify the sender, where that capability is needed more.  But in order for this to work we have to either delete all senders from the older account or somehow transfer the senders from the old account to the new account.

In case you are curious why we need separate accounts it is because each has its own branding requirements, email requirements, etc, and it is just better for us that these two use cases maintain separate accounts - if we can find a way past this sender constraint.

Thoughts? Thanks!  

Ron

Hi Ron,

Thanks for the detailed explanation!

Since you have your own on-premise installation, you should have the access to backoffice, where there's a function allowing you to merge sender into a new account. All existing and ongoing transactions / templates will be carried as well. 

If you decided to follow this path, since it's not related to the SaaS integration, we can continue the discussion in a private thread. Please kindly create a support ticket ([email protected]) and CC me, and ask for the detailed steps how to merge senders in backoffice.

Duo

Hello again,

We have recently made a change of direction for new internal clients where we will be using OneSpan SaaS instead of our own OneSpan On-Premise instance.  So I am wondering, how would the sender concept work with SaaS?  I am assuming we would not be able to set a sender to an email address of our own domain since the emails will be coming from your own server, is that correct? Or does SaaS handle senders differently as it pertains to the FROM email address of the invitation email coming from you?  In our on-prem environment we were able to have the sender email be the from email but that might be because we have our own email server here.  Just curious what the SaaS behavior is.

Thanks!

Hi Ron,

It's always great to hear from you!

If we are talking about the "from" header in an email notification, yes, with the default setup, emails will be sent from OneSpan Sign’s domain (either @esignlive.com or @onespan.com, from my understanding). On top of that, you got two choices #1 either to provide your own SMTP server #2 or to configure DKIM and have OSS sends on behalf of your domain. You can also check below dev blog for more details:

https://www.onespan.com/blog/onespan-sign-developers-email-templates-part-2

Duo