---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Specify a login landing page

# Specify a login landing page {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

By default, users see their homepage upon login. You can specify a different login
landing page by using a system property or the content management system.

## Vorbereitungen

Role required: admin

## Warum und wann dieser Vorgang ausgeführt wird

To specify a login landing page for all users, change the property value on the
sys_properties table.

## Prozedur

1. Type <kbd class="ph userinput">sys_properties.list</kbd> in the navigation filter.
2. Locate the glide.login.home system property.
3. In the Value field, enter the name of the page that all users see upon login.  
   Use \<page name\>.do; you may omit the
   http://''instance''.service-now.com/ portion of the
   URL. To determine the page name or the URL of a page in the system, you can
   point to a link. Some possible pages are welcome.do and
   incident.do.

   To specify a dashboard landing page, set the property to
   $dashboards.do?dashboard=\<SYS_ID\>. Replace
   \<SYS_ID\> with the sys_id of the dashboard.

   To direct users to service portal, set the property to
   /sp  
   Hinweis:  
   This property is system-wide, so setting it affects all users. To set a login specifically for users with no roles, you can apply these same steps and use the glide.entry.loggedin.page_ess property.

   You can also specify a login landing page with the content management system.