Multiple portals will look like two different websites from the customers’ point of view. Once a customer is signed up on a portal, he/she can use the same credentials to log into the other portal as well, depending on how the URLs are exposed. You would be able to determine the portal access by changing the user permissions in Admin -> Portals -> settings.
Please navigate to Admin -> email notifications -> requester notifications -> click on insert placeholder and include the placeholder for product-specific URL. This would allow customers to navigate to the support of the appropriate product.
Tips for a better login page and process
1. Make it clear where to login
When users come to a website or app, and already have an account it should be immediately clear where they go to login. Rather than providing a ‘Login’ or ‘Sign in’ link (the term ‘Sign in’ is probably more common place than ‘Login’, but users generally understand either) it’s better to show the input fields, so that users can login directly from a page.
2. Differentiate login from registration
On an increasing number of websites the login input fields (email and password) are very similar, if not exactly the same as the registration input fields (email and password). It’s important therefore to clearly differentiate the two, and to minimise the chance of users accidently attempting to login in via the registration form. One way to do this is to get users to input their password twice on registration (always a good idea since passwords are masked on entry), or to only show one form at a time.
3. Allow users to login with an external account (e.g. Facebook)
Why force users to have to remember another set of login details when it’s now so easy to let them login via an external account, such as a Facebook, Google or LinkedIn account? Of course not everyone is likely to be happy doing this, but it’s a great way to let users easily login to your website or app with an account that they use day in, day out.
4. Use email address, rather than username
This is a particular usability frustration of mine – namely websites asking users to login with a username, rather than their email address. I have two main emails addresses (my personal and work addresses), but many, many different usernames for various websites. Since usernames have to be unique, invariably a preferred username has been taken, so users end up registering with a new username that they are never going to remember.
5. Let users see their password (if they want to)
A common problem when users attempt to login is mis-typing their password. This is all too easy to do as the password field is of course masked. A useful feature is to allow users to see the password they have entered (if they want to) by providing a show password checkbox. This checkbox should of course be unchecked by default (i.e. the password is always masked by default).