By default, organizations that use HelloID can access their HelloID instance by going to a URL like this: https://companyname.helloid.com/
If your organization wants to use a custom URL such as https://helloid.companyname.com/, you will need to work with HelloID support to get everything set up. This article will lead you through gathering what we need and getting in touch with us.
What is needed to configure a custom HelloID URL?
A Custom URL
In order to use a custom URL for your HelloID instance, you first need to know what that URL will be. Typically, this will be a subdomain of your organization's domain, such as "login.companyname.com" or "helloid.companyname.com". Come up with a URL that's right for your organization and make note of it.
Communication with HelloID is done over HTTPS. As such, we will need a PFX certificate for the domain specified in the URL. This can be either a wildcard certificate or domain certificate for the requested website. Have this certificate on hand and ready to provide to us.
A DNS Configuration
In order for traffic to be routed to HelloID via your custom URL, you must add a CNAME entry to your DNS that points to HelloID. Depending on where your organization is located, you have a few different choices of server to target.
- For customers with users working in American regions, we advise adding a CNAME record with the value: dns-wus-01.helloid.com
- If your users are based in Europe, we advise adding a CNAME record with the value: dns-we-01.helloid.com
- If you're users require a global presence you can add a CNAME record with the value: dns-global-01.helloid.com
Note: Using the global DNS server will direct our traffic manager to determine the nearest HelloID server.
Example CNAME record to add:
Getting in touch
Once you've taken care of the URL, certificate, and DNS entries, you can get in touch with us by contacting either your account representative or HelloID support.