---
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


---

# Tutorial: Use Location Filter criteria

# Tutorial: Use Location Filter criteria {#ariaid-title1}

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

Describes steps to use location filter criteria in the authentication policy and restrict access to the users based on the location.

## Vorbereitungen

Role required: adaptive_auth_admin

Plugin required: Zero Trust - Location Based Access (<kbd class="ph userinput">com.snc.zero_trust_location_access</kbd>).

Property: Enable the Adaptive authentication property.  
Hinweis:  
Administrators can only create the policy based on location filters if the location is available for the current user session.

The following procedure describes how to create and use the location filter criteria in an authentication policy.

## Prozedur

1. Navigate to AllAdaptive AuthenticationFilter CriteriaLocation Filter.
2. Select New.
3. On the form, fill in these fields.  
   {#use-location-filter-criteria__table_tz3_bww_vnb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name to identify the criteria. |
   | Description | Short description of the criteria. |
   | Application | Scope of the application. |
   [Tabelle : 1. Location Filter Criteria form]

   {#use-location-filter-criteria__table_tz3_bww_vnb}
4. In the Locations sections, under the Locations for criteria tab, double-click to Insert a new row.
5. Specify the locations.  
   For example, use some of the APAC regions to control the logins of the users coming from APAC.

   Based on the criteria set in the example, you can control logins from <kbd class="ph userinput">Indonesia</kbd>, <kbd class="ph userinput">China</kbd>, and <kbd class="ph userinput">Malaysia</kbd> for your instance.
6. Select Submit.
7. Use the filter criteria created in any of the authentication context (Pre, Post, MFA) and Session Access.  
   To know more about the configuration based on authentication context and session access, see:
   * [Location Filter in Pre Authentication Context](https://servicenow-prod.fluidtopics.net/cyEDwqUqoRYRb2~Nyt_LTQ "Use the location filter criteria created in the Pre Authentication Context.")
   * [Location Filter in Post Authentication Context](https://servicenow-prod.fluidtopics.net/ECZS6sDML8SE3vgcrgf1Yw "Use the location filter criteria created in the Post Authentication Context.")
   * [Location Filter in MFA Context](https://servicenow-prod.fluidtopics.net/vTH8S2wyftdcUBjKmxrrGg "Use the location filter criteria created in MFA Context.")
   * [Location Filter for Session Access](https://servicenow-prod.fluidtopics.net/~ErFBXvyKv8_NrXjxc2dJg "Use the location filter criteria created in Session Access to reduce roles based on the location of the user.")

   {#use-location-filter-criteria__ul_cf3_ykz_jxb}

   You can use the Property ID - Error message to be displayed to the user when login fails due to authentication policy failure (<kbd class="ph userinput">glide.auth.policy.ui.error.message</kbd>) to customize the error
   message.