■

A custom domain URL is a virtual address that can include your company subdomain (e.g. intranet.socialive.com). Your users can then use this URL to access the intranet.

During your org's implementation, your consultant will ask for the domain you want to use. Our team will then set up your URL, which will create a number of unique DNS records. We then send your team those records to have populated into your DNS settings. 

While you are able to change the URL at any time, Simpplr does not recommend changing it often. All your intranet URLs will be tied to the domain set up here, and if changed, this would break any URLs set up, and it's a manual process for Simpplr to adjust each URL. Contact Support if you'd like to begin the process of changing the URL.

The custom domain setup is done on Simpplr's account. There are a series of steps that need to be executed to set this up, and there is a dependency on the customer's IT team as well.

To explain the process/steps, let's use intranet.example.com as the custom domain we wish to use for accessing Simpplr One platform.

Below are the high-level steps required to get the custom domain setup implemented. Again, Simpplr will complete these steps for you. The only steps you'll need to take are deciding what to use for your custom domain name and implementing the NS records that Simpplr provides:

1. Simpplr team will create a Public Hosted Zone with name intranet.example.com in our AWS account under the Route53 DNS service. This step will generate NS (Name Server) records.
2. Simpplr team will share the NS records with the Customer team (your team).
3. Customer team (your implementation team or IT admin) will add the NS records to your DNS server under the parent domain example.com. Once completed, any request for intranet.example.com will resolve via Route53.
4. Simpplr team will request a Public SSL certificate using AWS Certificate Manager, specifying intranet.example.com as the Fully Qualified Domain Name (FQDN). For ownership validation, we will opt for domain validation, which will generate CNAME records.
5. Simpplr team will add the CNAME records in the intranet.example.com hosted zone on AWS Route53. Once validated, AWS will activate the certificate.
6. Simpplr team will use the SSL certificate while provisioning the rest of the infrastructure for the customer in AWS.
7. AWS Certificate Manager: Handles SSL certificate revalidation automatically.

As you can see, the only action required from the Customer team is to add the NS records for intranet.example.com in your DNS service. The remaining steps will be managed entirely by the Simpplr Team.