---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Configure visit requirements

# Configure visit requirements {#ariaid-title1}

Release version: Australia  
Updated March 15, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Configure requirements that visitors must fulfill for their visit to your organization.

## About this task

Visit requirements let you control what information visitors must provide before they check in. You can set different rules based on the location, visitor type, and other conditions.

As an admin, you create visit requirements to define the check-in steps visitors go through.

Each requirement can include the following types of additional information:

* Extra questions to collect information from the visitor
* Policies or documents the visitor must read and agree to
* Files the visitor must upload, such as a photo

You can also set conditions so that only certain visits trigger a requirement. For example, you might require a photo ID only for visitors arriving at a highly secure campus.

## Before you begin

Role required: sn_wsd_visitor.admin

## Procedure

1. Navigate to AllWorkplace Visitor ManagementAdministrationVisit requirements.
2. On the Visit requirements list, select New.
3. On the form, fill in the fields.  
   {#configure-visit-requirements__table_ekn_czm_p3c__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the requirement. |
   | Is initial requirement | Option to display the requirement on the visit creation page. If this option is selected, the requirement is displayed on the visit creation page to the host and receptionist. Initial requirements are displayed first in the Workplace Services Kiosk self-registration flow. For more information about self-registration, see [Self-register as a visitor](https://servicenow-prod.fluidtopics.net/4a5jJbrMRB5_x2uJiOnTJg "Register as a visitor by providing your details such as your name, purpose of the visit, and host."). Initial requirements are used by the Workplace Concierge agentic workflow to create visits. For more information, see [Workplace Concierge agentic workflow](https://servicenow-prod.fluidtopics.net/vrGWTXZ1HQggP6gufdA3qw "Use the Workplace Concierge agentic workflow to register visitors from existing communication tools like emails, calendars, or the Virtual Agent."). If this option is not selected, the requirements appear later in the visit creation process based the conditions set in the Apply if section. For example, a visitor name and email are initial requirements, while a visitor license plate or VIP status can be considered non-initial requirements. |
   | Order | Order of the requirement in the pre-check tasks. |
   | Active | Option to set the record to active. |
   [Table 1. Visit requirement form]

   {#configure-visit-requirements__table_ekn_czm_p3c}
4. In the Apply if field, add conditions for when the requirement is applicable.  
   The Apply if field is only available if Is initial requirement is not selected.

   For more information about conditions, see [Condition builder](https://www.servicenow.com/docs/access?context=c_ConditionBuilder&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).

   To include workplace locations within a parent location, you must add conditions to dot-walk from the nested locations to the parent location.  
   To include all floors, areas, and spaces in Building A, add the following conditions.
   * <kbd class="ph userinput">Workplace Location is Building A</kbd> OR
   * <kbd class="ph userinput">Workplace Location.Floor.Building is Building A</kbd> OR
   * <kbd class="ph userinput">Workplace Location.Area.Building is Building A</kbd> OR
   * <kbd class="ph userinput">Workplace Location.Space.Building is Building A</kbd>
   {#configure-visit-requirements__ul_dcl_p4r_t3c}
5. Save the record.  
   The visit requirement record is created.
6. On the Additional information related list, select New.  
   You can also select New on the Document to acknowledge or Document to upload related list.
7. On the form, fill in the fields.  
   For a description of the field values, see [Additional requirement form](https://servicenow-prod.fluidtopics.net/c~mVju6OktulhZ6eoXnsoQ "The Additional requirement form specifies visitor information that is required while adding a visitor.").
8. **Optional:** On the Acknowledgment tab, in the Policy field, select a policy record.  
   The acknowledgment tab is displayed if the Requirement type is <kbd class="ph userinput">Document to acknowledge</kbd>.
   For more information about creating policies, see [Create a visitor policy](https://servicenow-prod.fluidtopics.net/d_PxG7MzrwkoFkEB4xBNUw "Define a policy that must be accepted by a visitor prior to their arrival. Send email notification to the visitor about the policy and enable them to accept the policy by replying to the email​.").
9. **Optional:** On the Field mapping tab, select a Target table and Target field to map the additional information.  
   For example, Company information can be mapped to the Organization field of the Visitor \[sn_wsd_visitor_visitor\] table.
10. Select Submit.
{#configure-visit-requirements__steps_rkg_vym_p3c}

## What to do next

Create more records for additional information based on your preference. You can view the created records in the related lists of the Visit requirement record.
**Related concepts**   

* [Configuring Workplace Visitor Management for Workplace Services Kiosk](https://servicenow-prod.fluidtopics.net/dX3qRiJvA0kiaWNeOHSJ~w "You can configure pages, check-in flows, check-out flows to integrate Workplace Visitor Management with the Workplace Services Kiosk.")  
**Related tasks**   

* [Install Workplace Visitor Management](https://servicenow-prod.fluidtopics.net/XrIAdtIJSYQVuJahs5r~cg "Install the Workplace Visitor Management application from ServiceNow Store applications. Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.")
* [Create a visitor policy](https://servicenow-prod.fluidtopics.net/d_PxG7MzrwkoFkEB4xBNUw "Define a policy that must be accepted by a visitor prior to their arrival. Send email notification to the visitor about the policy and enable them to accept the policy by replying to the email​.")
* [Create a record producer for visitor management](https://servicenow-prod.fluidtopics.net/RrFTtLz8CtCxuA7iyGgGtA "Make visitor-related services available to employees as a self-service option. Create a record producer to display these services as catalog items in the Workplace Services catalog.")
* [Configure a visitor type](https://servicenow-prod.fluidtopics.net/jMovxkKzYCk9v8ty4rrvnw "Create a visitor type that can be used to categorize visitors for your hosts or reception staff.")
* [Create a visitor badge template](https://servicenow-prod.fluidtopics.net/1scs3aoOJevzxSS~rwmY5g "Create an HTML template that can be used to print badges for your workplace locations.")
* [Configure the frequency of email notifications](https://servicenow-prod.fluidtopics.net/fnM08XXv85M~kIWXl56UaQ "ServiceNow provides two scheduled jobs in the Workplace Visitor Management application that automate email notifications for visitor registration and policy confirmation. This topic explains how to locate these jobs and adjust their execution frequency to meet your organization's notification requirements.")  
**Related reference**   

* [Quick start test for Workplace Visitor Management](https://servicenow-prod.fluidtopics.net/3agloaK0y02C73p6jnI_6g "Validate Workplace Visitor Management after any configuration change such as an upgrade or after developing a functionality. Copy and customize these quick start test when using your instance-specific data.")

*[\>]: and then


