Improvement to email sending mechanics
Whenever a message is triggered to send out from our system (task emails, notification alert emails, etc) the FROM email address could be set by the user in their communication settings.
This meant that our system emails, from: firstname.lastname@example.org could be masked with whatever the client's email address was, e.g. from: email@example.com. This kind of behaviour can trigger email domain spam filters and then our emails become quarantined or blocked.
Rather than setting email sender name and address to what's been configured in the app, we set the sender name, but the address remains firstname.lastname@example.org.
Changing it from
Note: some system emails may not have a reply to address
SSO can now accept multiple Entity ID/Audience IDs (Azure AD)
We have existing SSO functionality one a one-to-one relationship, one account to one idp app.
We have some customers who are set up with multiple accounts because they have different locations with different Xero instances that need to be integrated on a one-to-one basis.
We have enhanced our SSO code to now allow for various Audience URI/EnitityID’s from the same IDP. This means that in the setup on the client’s side, they can simply add multiple enterprise apps (Azure AD) with different Indentifier/Entity IDs.
E.g. if there were multiple accounts, the client could add the details after the “/saml“ section using this naming structure,
“https://login.hrassured.com/app/saml?client=<enter unique details here>“.
which then can be added to this section against the client's account