---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/mobile

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Create

# Create a branded landing page for single instances {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Create a branded pre-login landing page with a ServiceNow mobile login button or mobile deep links. These elements redirect users either to a specific area within the ServiceNow mobile app or to the login screen.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Nota:  
This feature is supported from ServiceNow mobile app version 19.0 and above.  
Nota:  
For the Xanadu version and earlier, this functionality is supported using the property sys_extension_point with the API name global.CustomPreAuthProperties. From Yokohama, you can use the preLoginLandingPage property and remove the property sys_extension_point with the API name global.CustomPreAuthProperties from the existing script.

The sys_extension_point with the API name global.CustomPreAuthProperties still works in the Yokohama version, even if the preLoginLandingPage property isn't defined. However, if both properties are defined, the property preLoginLandingPage takes
precedence. For more information about creating a branded landing page in the Xanadu version and earlier, see [Configure advanced app allowance with links to permitted apps](https://servicenow-prod.fluidtopics.net/AcqZWta_bxuRjVBvi9RKxA "Configure a scripted extension point with a list of mobile apps that can log in to the ServiceNow instance. When a user attempts to log in with an unauthorized app, the admin can add a link that redirects the user to an authorized app.").

## Procedimento

1. Navigate to Allsys_sg_properties.list.  
   The Mobile Properties list displays.
2. Select New to create a mobile property record.
3. Enter the name <kbd class="ph userinput">preLoginLandingPage</kbd> in the Name field.
4. Select JSON in the Type field.
5. In the Value field, enter the URL to be displayed to the user.  
   Enter the following script, `{"url":"<URL>"}`

   For example, the script would look as follows when using the ServiceNow home page: `{"url":"https://www.servicenow.com/"} `  
   Nota:  
   The URL must be a publicly accessible web page. These URLs include both ServiceNow and non-ServiceNow domains.
6. **Opcional:** To configure a different button label name other than the default name, Log in, do the following.
   1. In the Value field, enter the following script after the landing page URL, `"loginLabelTranslationKey":"<button label key>"`
   2. Copy one of the following predefined button label keys:

   Nota:  
   The predefined button key is translated according to the users preferred language settings on the app.
   {#branded-landing-page-create__table_kbx_pdg_4fc__entry__2}

   | Predefined button label key | Displayed button label name |
   |-|-|
   | `login_label_txt` | Log in |
   | `sign_in_label_txt` | Sign in |
   | `enter_label_txt` | Enter |
   | `access_account_label_txt` | Access account |
   | `continue_label_txt` | Continue |
   | `get_started_label_txt` | Get started |
   | `proceed_label_txt ` | Proceed |
   [ ]

   {#branded-landing-page-create__table_kbx_pdg_4fc}

   For example, the script would look as follows when using the ServiceNow home page with a button labeled Access account:` {"url":" https://www.servicenow.com/","loginLabelTranslationKey":"access_account_label_txt"}`
7. Select the Active field if you want this mobile property to be active.
8. Select the Is Public check box to make the web page available for public access.  
   Nota:  
   The Mobile App Config field disappears when you select the Is Public option.
9. In the Mobile Application field, select which mobile apps are to display the branded landing page.  
   Enter either <kbd class="ph userinput">Agent</kbd>, <kbd class="ph userinput">Request</kbd>, or the name of a custom app type created by users of Mobile Publishing. Leave the field empty to display the same branded landing page for all supported app types or variants.  
   Nota:  
   You can define the preLoginLandingPage property for different mobile apps, by creating additional mobile property records for each of the mobile apps. In each of these different preLoginLandingPage property records, you define specific values according to the requirement of each app.
10. Select Submit.

## O que Fazer Depois

You may want to change the login page to be compatible with the style of the branded landing page. For more information, see [Publish mobile apps with custom branding](https://servicenow-prod.fluidtopics.net/r5jwxrEpfVkTMuOTuiu7fg "The ServiceNow Mobile Publishing application enables you to publish secure and branded mobile applications. These mobile apps use your unique company identity and management method.") and [Next Experience theming for mobile](https://servicenow-prod.fluidtopics.net/GG3sQmGhRiT7X6ilupi_Ag "Use Next Experience theming to give your mobile apps color scheme consistent with your instance web experience.").

For more information on using deep links, see [Navigation links within a branded landing page](https://servicenow-prod.fluidtopics.net/W6KYpRUQaKy8PEbA9X5fOA "Learn about the different behavior of trusted or untrusted links on your branded landing page.") and [Deep linking for mobile](https://servicenow-prod.fluidtopics.net/UYdfDgHGQW3qgcGotMVsBw "Mobile deep links are linking formats that direct users to specific content and locations within a mobile app. These links can be placed in email notifications, text messages, push notifications, launcher screens, and input form screens. You can also configure a mobile app login URL for multiple SSO identity providers.").