Multibrand Update

As part of product release Deskpro 2018.1, we've made a number of significant changes and improvements to the way multibrand works in Deskpro.

We've made it easier to connect users and user records to specific brands. Essentially, brands now act in a way that feels more like they are separate. From a user perspective, it is now not so apparent that Deskpro is powering multiple brand portals or helpdesks.

Here are some of the most important changes:

Users only get emails from a brand they're associated with

For example, if you send a reset-password email to a user from Agent interface, the user now gets emailed from an address that belongs to the brand they're associated with, and get a reset link to that specific brand portal.

User authentication behaves differently across brands

For example, if you want to enable registration on BrandA but disable it on BrandB, you can now do that. If a user exists in the Deskpro database, they cannot log in to BrandB unless they are specifically associated with the BrandB. This means that you can further limit the user's interaction and exposure to BrandB.

It is now possible to enable and disable authentication sources on a per-brand basis

For example, you can have "Login with LDAP" enabled on BrandA but not BrandB. Multiple default User Source apps now operate across brands on a per-brand basis.

Emails sent to the helpdesk result in user records being created

Email addresses now have brands associated with them, so new user records can set the proper brand on any new accounts.