---
author_name: Boaz Wimmer, Hani Lachnish, Lindsay Bert
author_profile: https://github.com/LindsayBert  
keywords: tutorial
auto_validation: true
time: 120
tags: [ tutorial>beginner, type>tutorial, software-product>sap-business-technology-platform, topic>cloud, software-product>sap-build-work-zone--standard-edition ]
primary_tag: software-product>sap-build-work-zone--standard-edition
parser: v2
slug: cp-portal-cloud-foundry-create-custom-domain
canonical_url: https://developers.sap.com/tutorials/cp-portal-cloud-foundry-create-custom-domain
---

# Get Started with Creating a Custom Domain in SAP Build Work Zone, standard edition
<!-- description --> Using the SAP Custom Domain service, administrators of SAP Build Work Zone, standard edition can configure a custom domain for exposing a site instead of using the default domain. 

## You will learn
    - How to create and manage custom domains for SAP Build Work Zone, standard edition
    - How to configure custom domains using SAP Cloud Identity Services - Identity Authentication
    - Where to find documentation in order to complete the configuration

## Overview
Instead of using the default domain that is assigned to your subaccount, you can purchase a custom domain with a unique name that's easily recognizable by your users, making them more secure about accessing your site. For example, if your default domain is `subaccount.launchpad.cfapps.eu10.hana.ondemand.com`, you can purchase the domain `mycompany.com`, create a custom domain `prod.mycompany.com`, and securely expose your site under this custom domain. Using the same domain for a site as well as for all the embedded content including Identity Authentication, enables broader integration scenarios, by avoiding third-party cookies with the respective security drawbacks. Note, if you decide to use a custom domain, make sure that you update links and inform end users to update their bookmarks. If users want to still use the default `ondemand.com` domain, this is possible. Note that there is no option to block the default domain.


## Illustration of the custom domain configuration process
To make sure that your domain is trusted by way of activated server certificates and that all application data is protected, you must set up secure TLS/SSL communication. Then, make your application reachable via your custom domain and route traffic to it.

![Configuration Process](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/1-configuration-process-diagram.png)

## Prerequisites
 - You have entitled the Custom Domain Manager to your subaccount. For more information, see [Manage Entitlements Using the Cockpit](https://developers.sap.com/tutorials/btp-cockpit-entitlements.html).
 - You have entitled the SAP Custom Domain service (plan: custom_domains) to your subaccount. Every server certificate requires 1 unit of quota.
 - You have subscribed to the Custom Domain Manager in the SAP BTP cockpit. For more information, see [Initial Setup](https://help.sap.com/docs/custom-domain/custom-domain-manager/initial-setup?version=Cloud).
 - You have acquired the domain names to be used by your applications. Have a look at the [Prerequisites](https://help.sap.com/docs/custom-domain/custom-domain-manager/prerequisites?version=Cloud). 
 - You have entitled the SAP Build Work Zone, standard edition application to your subaccount. 
 - You have a tenant of SAP Cloud Identity Services.
 - You have access to the Domain Name System (DNS) management dashboard.
 - You have created an OIDC trust between your SAP BTP subaccount and your Cloud Identity Services tenant. For more information, see [Establish Trust and Federation Between SAP Authorization and Trust Management Service and SAP Cloud Identity Services](https://help.sap.com/docs/btp/sap-business-technology-platform/establish-trust-and-federation-between-uaa-and-identity-authentication?version=Cloud)
 - You have subscribed the SAP Build Work Zone, standard edition application to your subaccount. For more information, see [Initial Setup](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/initial-setup).
 - You have subscribed to the Custom Domain Manager in the same SAP BTP subaccount in which SAP Build Work Zone, standard edition application is subscribed. For more information, see [Initial Setup](https://help.sap.com/docs/custom-domain/custom-domain-manager/initial-setup?version=Cloud)
 - If you're using tunnelled access to access on-premise apps, you have to configure clickjacking protection as follows:
        - SAP S/4HANA Cloud - [Protect Against Clickjacking](https://help.sap.com/docs/SAP_S4HANA_CLOUD/4fc8d03390c342da8a60f8ee387bca1a/3d1ea8b1a0e145bb851d36d0da376e17.html?version=2502.VAL).
        - SAP S/4HANA - [Using an Allowlist for Clickjacking Framing Protection](https://help.sap.com/docs/SAP_NETWEAVER_AS_ABAP_751_IP/864321b9b3dd487d94c70f6a007b0397/966b6233e5404ebe80513ae082131132.html?version=7.51.17).
        - SAP IBP - [Protect Against Clickjacking](https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/0292066056f642f1a0f6d9135e39abaf/3d1ea8b1a0e145bb851d36d0da376e17.html?version=2502).
        - SAP BTP ABAP environment - [Protect Against Clickjacking](https://help.sap.com/docs/btp/user-interface-configurations/protect-against-clickjacking?version=Cloud).


### Define a default site

> A default site is the site that opens when no site ID is specified in the URL. The default site can be set per custom domain and doesn't affect all domains in a subaccount. Note that a custom domain must be mapped to a single point and that’s why it’s mapped to the default site and not to a specific site.

You define the default site in the Site Directory of your SAP Build Work Zone, standard edition subaccount as follows:

1. Go to your subaccount in the SAP BTP cockpit.

2. Click the **SAP Build Work Zone, standard edition** link.

3. Open the Site Directory in your SAP Build Work Zone, standard edition application.

4. Choose the site that you want to define as the default site.

5. Click the `...` icon on the site tile.

6. From the action menu, select **Set as Default**.

    ![Select default site](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/2-site-directory-new.png)


### Manage reserved and custom domains

> To make your applications reachable and secure under your own domain, use the **Custom Domain Manager** to create and manage your reserved and custom domains. The reserved domain should be your parent domain (for example, `prod.mycompany.com`). The custom domain is created based on your reserved domain (for example, `workzone.prod.mycompany.com`). 
The best practice is to use 3 different subaccounts for **Dev**, **QA**, and **Prod**. Therefore we recommend creating 3 reserved domains accordingly: Example: `dev.mycompany.com`, `qa.mycompany.com`, and `prod.mycompany.com`.


Then perform the custom domain configuration steps such as creating custom domains, server certificate etc, for all 3 subaccounts.

1. Open the SAP BTP cockpit, and log on to the **Custom Domain Manager**.

2. Choose the **Domains** tile.

      ![Reserved domains](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/3-reserved-domains.png)

3. Click **Add**  to add a domain name that you want to reserve for this landscape and associated extension landscapes. For example: `mycompany.com`.

    ![Select reserved domain](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/4-select-reserved-domain.png)

    Note that the domain name is now displayed in the list of **Reserved Domains**.

4. Switch to the **Custom Domains** tab and click **Create**, and select **for your Subaccount's SaaS Subscriptions**. 


    ![Select create](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/4a-create.png) 

5. A wizard opens displaying your subscribed applications, in their corresponding landscapes. Now do the following:

    - From the **Select Deployment Type** step,  select `SAP Build Work Zone, standard edition`  as the SaaS application and click **Next Step**.

    ![Select reserved domain](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/5-select-Saas-application.png) 

    - From the **Select Reserved Domain** step, select the desired domain from the list of **Reserved Domains** which in our case is `prod.mycompany.com`. Now click **Next Step**.

    ![Select domain](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/6-select-domain.png)  

    - From the **Create Subdomain Name** step, enter a single subdomain name, for example `prod` and click **Finish**. The result is a new custom domain. For example, `workzpne.prod.mycompany.com`

    ![Select subdomain](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/7-select-subdomain.png) 

6. Create a custom domain for every runtime destination. For example: `xyz200.prod.mycompany.com` (xyz200 in this example is the on-premise backend). The custom domain for the runtime destination must be part of this hierarchy, meaning it should be a **single** subdomain under the reserved domain, otherwise an error will occur. This is because SAP Build Work Zone code suppresses the subdomain (for example, `workzone.prod.mycompany.com`) used for the SAP Build Work Zone site when performing requests to on-premise backend applications.

    ![Custom domain for runtime destinations](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/8-custom-domain-for-runtime.png) 

    If you have content providers in multiple subaccounts (e.g. dev/test/prod), make sure that every subaccount has its own custom domain for the SAP Build Work Zone subscription and destination. The destination content could be similar, but the destination’s name should be different.
    
    Here's an example:

    | :------------- | :------------- | :------------- | :-------------
    | **Runtime Destination Domain**     | **DNS CNAME** | **SaaS Route**        | **SAP Build Work Zone Domain**
    | xyz200.prod.mycompany.com       | CNAME api.cf.eu10.hana.ondemand.com. | portal-prod-sapdelim-xyz200.launchpad.cfapps.eu10.hana.ondemand.com | workzone.prod.mycompany.com
    | xyz300.qa.mycompany.com    |  CNAME api.cf.eu10.hana.ondemand.com. | portal-qa-sapdelim-xyz300.launchpad.cfapps.eu10.hana.ondemand.com  | workzone.qa.mycompany.com.
    | xyz400.dev.mycompany.com     |  CNAME api.cf.eu10.hana.ondemand.com. | portal-dev-sapdelim-xyz400.launchpad.cfapps.eu10.hana.ondemand.com  | workzone.dev.mycompany.com.
   

7. Create a custom domain for SAP Cloud Identity Services. For example, `ias.prod.mycompany.com`.

The custom domains are created and displayed in a list, along with their corresponding landscape and status.


### Use custom domain in Identity Authentication

The purpose of this step is to configure a custom domain for your Cloud Identity Service tenant. Use the custom domain that you've created in step 2 above.  
 You'll use it later when establishing trust to your SAP BTP subaccount and in the Domain Name System (DNS) setup. 

 This configuration is strongly recommended when your browser is blocking third party cookies, to avoid cross-origin domain issues. 

For more information, see [Use Custom Domain in Identity Authentication](https://help.sap.com/docs/cloud-identity-services/cloud-identity-services/use-custom-domain-in-identity-authentication)

### Manage Transport Layer Security (TLS) configurations

This step is done in the Custom Domain Manager. You'll create new TLS configurations that can be used for one or mulitple server certificate activations.

1. Choose the **Server Identities** tile.

    ![Select TLS tile](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/10-TLS-tile.png)

2. Click **Create**.
    ![Create configuration](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/10a-create-TLS-configurations.png)

3. Enter a configuration name, for example `myTLS` and click **Next Step**.

    ![Configuration name](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/11-configuration-name.png)

4. From the **Client Authentication (mLTS)** step, you'll see that the client authentication is displayed as disabled by default. Therefore a user name and password are required for authentication. Click **Next Step**.

    ![Client authentication step](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/12-client-authentication.png)

5. The **Summary** information displays the entered configuration name and the status of the mTLS mode again. Click **Finish** to exit the wizard and manage the created configuration.

    ![Summary step](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/13-Summary.png)

For more information, see the **Custom Domain Manager** documentation: [Manage TLS Configurations](https://help.sap.com/docs/custom-domain/custom-domain-manager/manage-tls-configurations).

### Manage server certificates

This step is done in the Custom Domain Manager. You'll create a new server certificate for custom domains associated with the SAP Build Work Zone, standard edition application and runtime destinations. You will also create a certificate for your custom domains from a trusted certificate authority (CA). Make sure that the Cloud Foundry environment is enabled for your subaccount.

1. Choose the **Server Identities** tile.

     ![Server certificates tile](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/14-server-certificate-tile.png)

2. Choose **Create**.

     <!-- border -->!(14a-choose-create.png)

    > A wildcard certificate secures multiple applications of a domain. So a domain called `*.prod.mycompany.com` covers any application under the domain `prod.mycompany.com`, for example `workzone.prod.mycompany.com`, but not the domain `prod.mycompany.com` itself. 
    This also works with subdomains, so the subdomain `*workzone.prod.mycompany.com` covers any application under the subdomain `workzone.prod.mycompany.com`, for example, `myapp.workzone.prod.mycompany.com`, but not the subdomain `workzone.prod.mycompany.com` itself.

3. The wizard opens with the **Select Name** step in focus. Now do the following:

    - Enter the desired name, and then click **Next Step**.

        ![Alias and key size](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/15-select-name.png)

    - In the **Select Target** step, keep the landscape with the default value, which should be the main landscape (e.g. `cf-eu10`). Then click **Next Step**.

        ![Select target](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/16-select-target.png)

    - In the **Select Custom Domains** step, select the domains which you want to assign to the server certificate.

        ![Select domains](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/17-select-domains.png)

    - In the **Certificate Subject** step, keep the **CommonName (CN)** parameter with the default value, then click **Next Step**. 

        > Note that the `CommonName` can't be longer than 64 characters.

        ![Set subject](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/18-set-subject.png)

    - In the **Key Configuration** step, keep the default Key Type.

        ![Set keyconfiguration](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/18a-key-configuration.png)

    - In the **Summary** step, click the **Finish** button.
    
        ![Summary step](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/18b-summary-step.png)

4. Select the server certificate that you created to expand the details section. To order and install your new server certificate, you must first create the certificate signing request and then send this file to a trusted certificate authority of your choice to get it signed.

    ![Server certificate details](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/19a-server-certificate-details.png)

    ![Server certificates signature](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/19-server-certificate-signature.png)

5. Click **Get Certificate Signing Request** to copy the content and create the `.pem` file. You can also paste the content into a web page of your CA, if available.

6. On receiving the new server certificate and full certificate chain (including the root CA), choose **Upload Full Certificate Chain** to upload them.

    - In the **Add Certificate** section, insert the certificate chain into the text field and click **Next Step**.
    - Check the certificate and choose **Next Step**.
    - Confirm that the certificate is correct and click **Finish**.

7. In this final step, you must activate your new server certificate. 

    > This activation has to be done for one or more of the certificate’s SANs and the TLS configuration of your choice that you configured in the **Manage TLS configurations** section. The activation can be modified or removed at any time and will take a few minutes until it's effective in the landscape load balancer.

    - In the **Details** pane, click **Activate**.
    - Select the SANs you want to activate, and click **Next**.
    - Confirm the TLS configuration and click **Next**.
    - Review the summary and choose **Finish**.

The list of server certificates created are displayed and as long as they are active, they can't be deleted. Inactive certificates can be deleted by using the **Delete** button.

### Manage SaaS routes

This step is also done in the Custom Domain Manager. You'll select your existing SaaS subscriptions and create custom routes for them - in addition to their standard routes.

Before you do this step, make sure that you've written down the default URL of the SAP Build Work Zone, standard edition application.

Now you can map the application to your custom domain as follows:

1. Choose the **SaaS Routes** tile.

     ![Saas Routes tile](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/20-SaaS-routes-tile.png)

2. Click **Create** to open a wizard where you will map a route to your application.

    ![Create route](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/20a-create-route.png)


4. In the **Select Saas Subscription** step, select the **SAP Build Work Zone, standard edition** subscription and click **Next Step**.

    ![Select Work Zone subscription](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/22-select-wz-subscription.png)

5. In the **Edit Route** step, don't change the standard route and click **Next Step**.

    > Note: even if your subaccount is in an extension landscape, such as `EU10-004`, you should use the main landscape URL, which is part of the subscription to SAP Build Work Zone, standard edition.

    ![Edit route](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/23-edit-route.png)

6. In the **Select Custom Domain** step, select the desired custom domain from the list and click **Next Step**. In this example, select `prod.mycompany.com`.

    ![Select custom domain](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/24-select-custom-domain.png)

7. In the **Select a Hostname** step, click **Finish**. There's no need to add a hostname.

    The route mapping is created and is displayed as a list.

    If you're using tunnelled access to access on-premise apps, repeat the above steps for every runtime destination, but in the **Edit Route** step of the Manage SaaS Route procedure (step # 5), use the following format:

    - For the `ondemand.com` domain: `[subdomain of the subaccount]-sapdelim-[Runtime destination name].[service name (launchpad or workzone or workzonehr)].cfapps.[data center].hana.ondemand.com`

    - For the `workzone.cloud.sap` domain: `[subdomain of the subaccount]-sapdelim-[Runtime destination name].[data center].workzone.cloud.sap`
    

Example of a runtime destination mapping:

| :------------- | :-------------
| App Name            | `SAP Launchpad`
| Custom route        | `xyz200.prod.mycompany.com`
| Standard route      | `subprod-sapdelim-xyz200.launchpad.cfapps.us10.hana.ondemand.com` 


### Create a CNAME record

In this step, you'll create a `CNAME` record in the Domain Name Service (DNS) so that the custom domain points to the SAP BTP data center.

Example: 

:------------- | :-------------
| name        | `workzone.prod.mycompany.com`
| type        | `CNAME`
| data        | `api.cf.eu10.hana.ondemand.com`
| TTL          | `14400`

You also need to configure the Domain Name System (DNS) in order to route traffic to an application on your custom domain. For each custom domain that you use, you must create a CNAME mapping from the custom domain to its Cloud Foundry domain. For example, you must create a separate `CNAME` mapping for your runtime destination custom domain in case you're using tunnelled access to access your on-premise apps.

Example:

:------------- | :-------------
| name        | `<runtime destination>.prod.mycompany.com`
| type        | `CNAME`
| data        | `api.cf.eu10.hana.ondemand.com`
| TTL          | `14400`

For more information, see [Configure the DNS for a Custom Domain](https://help.sap.com/docs/custom-domain/custom-domain-manager/configure-dns-for-custom-domain).

> If your Cloud Foundry environment, API endpoint is on an extension landscape such as `eu10-004`, you need to map your DNS to the main landscape (e.g. `eu10`). This is because the SAP BTP service that your subaccount is subscribed to, is located in the main landscape. For more information, see [Custom Domains in Extension Landscapes](https://help.sap.com/docs/custom-domain/custom-domain-manager/custom-domains-in-extension-landscapes).

### Configure the redirect URL

In this step, (which is only relevant for subscriptions that were created prior to September 4th 2025), you'll configure an OpenID Connect application in the administration console of SAP Cloud Identity Services for the authorization code flow.

1. Sign in to the administration console for SAP Cloud Identity Services.

2. From the **Applications and Resources** tab, choose the **Applications** tile.

    ![Applications tile](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/27-applications-tile.png)

3. Choose the SAP Build Work Zone, standard edition <`your subaccount name`> application.

    > Note: Type the subaccount GUID in the search field to filter the list items. One of the applications, named `SAP BTP Subaccount <your subaccount name>` will refer to the trust between your SAP BTP subaccount and the SAP Cloud Identity Service tenant. The redirect URI for this trust, which is created automatically, will be for example: https://mysubaccount.authentication.eu10.hana.ondemand.com/login/callback/sap.custom.
      The second application, named `SAP Build Work Zone, standard edition <your subaccount name>`, will refer to the trust between your Cloud Identity Service tenant and the SAP Build Work Zone, standard edition subscription. **You need to add your custom domain to the redirect URI of this trust**.
    

4. Click the **Trust** tab.

5. Under **Single Sign-On**, choose **OpenID Connect Configuration**.

6. Manually enter the communication settings negotiated between Identity Authentication and the client as follows:

    - Name (mandatory)              Provide a name of your choice.
    - Redirect URIs (mandatory)     The redirection URIs to which the response can be sent. You can add up to 20 redirect URIs. Example: `https://workzone.prod.mycompany.com/` or `https://*prod.mycompany.com/`
        

    The above URI covers both login and logout flows, so there's no need to add also a URI to the Front-Channel Logout URIs.

    ![OpenID Connect Configuration](https://raw.githubusercontent.com/sap-tutorials/Tutorials/master/tutorials/cp-portal-cloud-foundry-create-custom-domain/26-openID-configuration.png)

7. **Save** your selection. Once the application has been changed, the system displays a message that the application <name of application> is updated.

### Select the domain for your subaccount

In this step, you'll select the custom domain for your subaccount in order to support SAP Mobile Start application navigation. 

1. Go to your subaccount in the SAP BTP cockpit.

2. Click on the **SAP Build Work Zone, standard edition** link.

3. Access the **Subaccount Settings** from the side navigation panel and open the **Custom Domain** tab.

4. Select the preferred custom domain for your subaccount from the list of available domains configured in the Custom Domain Service.

For more information, see [Subaccount settings](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/subaccount-settings).

### Use multiple custom domains

You can assign multiple custom domains to the same subaccount, each one opens the default site when no site ID is specified in the site URL.

To open different sites with two different custom domains, you need to add the site ID part to the URL. The site ID can also be customized to have a friendly name by using the site alias functionality.

For example, if the custom domains are `dev` & `prod`, you can open two different sites as follows:
`https://workzone.dev.mydomain/site/alias1?sap-language=en#Shell-home` and `https://workzone.prod.mydomain/site/alias2?sap-language=en#Shell-home` 

Another example is having two site aliases for one domain: `workzone.prod.mydomain`:
`https://prod.mydomain/site/alias1?sap-language=en#Shell-home` and `https://workzone.prod.mydomain/site/alias2?sap-language=en#Shell-home` 

For more information about using a site alias, see [Configure a Site Alias](https://help.sap.com/docs/build-work-zone-standard-edition/sap-build-work-zone-standard-edition/configure-site-alias).