Branding (B2C)

Login 3.0 can be customized with a look and feel that aligns with your organization's brand requirements and user expectations. Branding Login 3.0 collateral provides a consistent user experience for your customers and gives them peace of mind that they’re using a product from a trusted and secure provider. All branding configurations must be requested and handled by the UPBOND team.

Login 3.0 provides support for internationalization (I18N) and localization (L10N), both of which are important if you work on branding for an international clientele. Out-of-box collateral, such as the Login 3.0 Lock UI widget, comes ready-enabled for multiple language support, with built-in extensibility for adding more languages if what you require doesn’t already exist.

Best Practice

Almost all applications need Internationalization and/or Localization in one form or another. Login 3.0 makes it easy to add, but you need to account for it up front: retro-fitting localization, for example, can be a painful process if left too late.

When considering the items you want to brand, as well as how best to brand them, there are a number of things you'll want to review:

• Do you need to brand your login page?

• Do you need to localize your login page?

• How can you customize emails so that they're not just branded, but vary based on user preference?

• How will users know that they're still on your domain when they see your login page?

• What do you need to do to provide additional browser security (e.g., implement Extended Validation)?

• Where do you want to direct users in the event of errors?

Login 3.0 provides tremendous flexibility when it comes to customizing and configuring Login 3.0 pages such as Universal Login and Password Reset. So you can pretty much set up whatever UX look and feel you require. For many, the out-of-the-box experience—with perhaps a little alteration—is all that's required. However, for others, the value of their brand and brand awareness requires more extensive customization. This flexibility extends to not only Login 3.0 pages but via extensibility can also be applied to the email templates. Login 3.0 Custom Domain functionality further enhances consumer awareness by providing users with the confidence and peace of mind when it comes to safety and security. All customization requests must be submitted to the UPBOND team.

While Login 3.0 provides for default information when it comes to error situations, out-of-the-box information can be somewhat cryptic as the context that can only be provided by you is missing. Login 3.0 error page customization guidance can, however, help mitigate that by allowing you to provide information of a more context-specific nature via your own support organization.

Best Practice

To provide helpful resources for users who experience problems, you should also configure a friendly name and a logo, as well as provide the support email address and URL for your organization. Contact the UPBOND team to set this up.

Universal Login and Login Pages

Universal Login is the recommended method for authenticating users, and it centers around use of the Login page. You can customize the Login page to support your organization's branding requirements by requesting these changes from the UPBOND team.

Custom Domain Naming

By default, the URL associated with your tenant will include its name and possibly a region-specific identifier. For example, tenants based in the US have a URL similar tohttps://example.login3.com while those based in Europe have something that is of the fashionhttps://example.eu.login3.com. A Custom Domain offers a way of providing your users with a consistent experience by using a name that’s consistent with your organization's brand.

Only one custom Domain Name can be applied per Login 3.0 Tenant, so if you absolutely must have independent domain name branding then you will require an architecture where multiple Login 3.0 Tenants are deployed to production.

In addition, Custom Domain functionality offers you complete control over the certificate management process. By default, Login 3.0 provides standard SSL certificates, but if you configure a custom domain, you can use Extended Validation (EV) SSL certificates or similar to provide the visual, browser-based cues that offer your visitors additional peace of mind. Custom domain setup must be handled by the UPBOND team.

In general, we see customers having the most success when they use a centralized domain for authentication—this is especially the case if the company offers multiple products or service brands. By using a centralized domain, you can provide end users with a consistent user experience while also minimizing the need to maintain multiple production tenants in Login 3.0.

Email Template Customization

Login 3.0 makes extensive use of email to provide both user notifications and to drive the functionality needed for secure identity management (for example, email verification, account recovery, and brute force protections), and Login 3.0 provides a number of templates for these. Email template customization requests must be submitted to the UPBOND team.

Out of the box, the email templates used contain standard verbiage and Login 3.0 branding. However, you can configure almost every aspect of these templates to reflect the verbiage and user experience you want and make changes to things like the preferred language, accessibility options, and so forth.

Email templates are customized using Liquid syntax. If you are interested in customizing your templates based on user preferences, you will also have access to the metadata located in users' profiles, as well as any specific application metadata too.

Error Page Customization

If there are issues encountered during user interactive workflow (e.g., user sign up or login), Login 3.0 provides error messages that indicate what the problem is under the hood. The default messages are somewhat cryptic, especially to the end user, since they will likely be missing context that only you can supply. As such, we recommend customizing your error pages to provide the missing context-specific information directly to your users. Furthermore, customizing your error pages allows you to display your branding, not Login 3.0's, as well as provide useful information to your users as to what should be done next. This information might include a link to a FAQ or how to get in touch with your company's support team or help desk. Customization must be handled by the UPBOND team.

Best Practice

Out-of-the-box there is no user interface for customizing Login 3.0-provided error pages, but you can work with the UPBOND team to configure them or create and host your own error page, then direct Login 3.0 to use that page instead.