--- 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 --- # Differences between Workplace Visitor Management versions # Differences between Workplace Visitor Management versions {#ariaid-title1} Release version: Australia Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Workplace Visitor Management version 2.0.0 introduces significant architectural, data model, portal, security, and feature changes compared to earlier versions (1.19 or earlier). {#visitor-mgmt-v1-v2-differences__entry__2} | Workplace Visitor Management 1.19 or earlier | Workplace Visitor Management 2.0.0 or later | |-|-| | Visitor identity is stored on registration records, coupling identity to a single visit. | Adds the sn_wsd_visitor_user table as a dedicated identity store, but identity is still stored on the registration record. The table enables reuse across multiple visits. | | Visitor type is is a field (visitor_type) on the sn_wsd_visitor_vistor_registration record. | Visitor type is an entity in the sn_wsd_visitor_type table, including a built-in Internal type for employee visitors. The visitor_type field on the registration record is deprecated. | | Uses the sn_wsd_visitor_m2m_location_policy table to link locations to policies and capture policy acceptance. | Policies are part of visit requirements, which can then be applied to workplace locations. For more information about creating visit requirements, see [Configure visit requirements](https://servicenow-prod.fluidtopics.net/I75pEG_X7FJjh5Gram0AkQ "Configure requirements that visitors must fulfill for their visit to your organization."). | | Uses the sn_wsd_core_html_signing_template table for badge templates. Policy signing uses only a signature-pad flow. | Extends the sn_wsd_core_html_signing_template table to support HTML-based policy signing templates in addition to badge templates. | | Has no dedicated auth state table for the public visitor portal. | Introduces sn_wsd_visitor_auth to track OTP, passcode, and session state for the public visitor portal. | | Uses a location field on visit, invitation, and registration records. | Adds a workplace_location reference field across all affected tables. The original location field remains but is deprecated. Integrations that read the old field require updates. | | The sn_wsd_visitor_visit table has a basic set of fields. The recurrence end date is stored using the internal key endDate in the legacy recurrence engine. | Extends sn_wsd_visitor_visit with recurring pattern fields, workplace_location, draft state, and occurrence editing. Replaces the legacy recurrence engine with an rule-based engine; the internal key changes from endDate to until. | | The sn_wsd_visitor_visitor table includes license_plate, parking_type, vip, and photo fields. | Removes license_plate and parking_type from sn_wsd_visitor_visitor. Adds custom-field sync to registration records. | [Table 1. Data Model changes] {#visitor-mgmt-v1-v2-differences__entry__20} | Workplace Visitor Management 1.19 or earlier | Workplace Visitor Management 2.0.0 or later | |-|-| | Has no dedicated host portal. | Introduces a host experience in the Employee Center with upcoming and past visit tabs, co-host visibility, visitor photo display, and visit or occurrence editing. | | Has a basic receptionist view. | Delivers a redesigned receptionist portal with real-data integration, multi-select, drag-and-drop, and a condition builder for badge printing. | | Has no public-facing visitor portal. | Introduces a public visitor portal with login, OTP authentication, and per-portal CSS branding support. | | Has a kiosk UI with self-registration and a pre-arrival check-in flow. Several kiosk UI sections and lists are present. | Redesigns the kiosk with an additional-info page and a condition builder for badge printing. Removes the V1 kiosk UI sections and lists. | [Table 2. Portals and user experience] {#visitor-mgmt-v1-v2-differences__entry__30} | Workplace Visitor Management 1.19 or earlier | Workplace Visitor Management 2.0.0 or later | |-|-| | Supports recurring visits using the legacy recurrence engine. | Replaces the legacy recurrence engine with a rewritten rule-based engine, and adds occurrence-mode management. | | Does not support draft visits. | Allows visits to be saved as drafts before submission. | | Supports only visit creation; existing visits can't be edited. | Supports editing existing visits and individual occurrences. | | Supports co-hosts with a co-host field and widget on visit records. | Adds a reference qualifier to the co-host field that excludes visitors. Co-host rows are displayed on the host portal. | | Supports a pre-arrival check-in flow on the kiosk, but visitors cannot complete visit requirements through it. | Extends the pre-arrival check-in flow to allow visitors to complete visit requirements before arriving. | | Visit cancellation cascades to related registrations but not to invitations. | Extends cancellation cascade to invitations and sends an email when an occurrence is cancelled. | [Table 3. Feature changes] {#visitor-mgmt-v1-v2-differences__entry__44} | Workplace Visitor Management 1.19 or earlier | Workplace Visitor Management 2.0.0 or later | |-|-| | Visitor notifications can be suppressed by global notification settings. | Enables force_delivery on all visitor notifications so they are sent even when global notifications are turned off. | | Emails include the location name, and parking and license plate information. | Adds the full address (street, city, state, and zip code) for campus and building locations to emails. | | Renders dates and times in the recipient's time zone using a configurable format, but date and time strings are not localized. | Wraps date and time strings in `gs.getMessage()` to support localization across languages. | | Emails include policy accept and decline buttons. | Removes policy accept and decline buttons from emails. Policy acceptance is handled through the requirements flow and signing templates. | [Table 4. Email and notifications] **Related concepts** * [About visit-related tables](https://servicenow-prod.fluidtopics.net/8Eskdrl0KMGqlGG~nRjYAg "The Workplace Visitor Management application uses three interconnected tables to track everything that happens during a visit from the invitation to the departure. Knowing what each table does helps you configure the application, troubleshoot issues, and know where to look when you have to audit visit activity.") **Related reference** * [Components installed with Workplace Visitor Management](https://servicenow-prod.fluidtopics.net/S5jcc4n7UJL2o7tfQl1L7w "Several types of components are installed with the Workplace Visitor Management application, including tables, user roles, and business rules.") * [Properties installed with Workplace Visitor Management](https://servicenow-prod.fluidtopics.net/eD0VPb7ivBE5VGAkigBiwA "There are several properties available with Workplace Visitor Management.") * [Kiosk Check-in Flow Configuration form](https://servicenow-prod.fluidtopics.net/a_KP8sst1xPRzNQNfYGkWg "Use the Kiosk Check-in Flow Configuration form to create a check-in flow for the Workplace Services Kiosk.") * [Kiosk Check-out Flow Configuration form](https://servicenow-prod.fluidtopics.net/Zn9sq0w~MKy9_IsRWDumpg "Use the Kiosk Check-out Flow Configuration form to create a check-out flow for the Workplace Services Kiosk.") * [Kiosk Page Configuration form](https://servicenow-prod.fluidtopics.net/UdOY8Qs6uzNjxXbX~RHnJA "Use the Kiosk Page Configuration form to create pages for the Workplace Services Kiosk.") * [Kiosk Page Customizations](https://servicenow-prod.fluidtopics.net/h4imIOnbK5VE1oBMZAiUNQ "The Page Configurations created for the Workplace Services Kiosk can be further customized by using their related lists.") * [Location Policy form](https://servicenow-prod.fluidtopics.net/de~ypFNFo7dT3cjt51aEZw "Use the location policy form to assign a visitor policy to a workplace location, apply the policy to internal/external visitors and configure whether the policies require signatures.") * [New visit form](https://servicenow-prod.fluidtopics.net/LXLjiPVYlqtDbHAJ4F3wyQ "Use the New visit form to select a purpose, location, date and time for your visit. Additionally, add visitors and optional co-hosts") * [Additional requirement form](https://servicenow-prod.fluidtopics.net/c~mVju6OktulhZ6eoXnsoQ "The Additional requirement form specifies visitor information that is required while adding a visitor.")