Genetec

Access Management Overview

• BLE: Open the app to use your mobile credential
• NFC: Tap and go access with your phone’s digital wallet
• ACS Read: Sync users from ACS

Visitor Management (Limited Availability, speak to your VTS contact for more information)

• Send visitor credentials to ACS

Required Client Participation

See below for required roles and expectations on your side. 

Role	Expectation
Executive Sponsor	Monthly and/or escalation participation only
Project Manager	Weekly participation
Integration Point of Contact	Integration & internal IT configuration support to work with VTS and integrator, complete Integration UAT onsite, knowledgeable infrastructure resource
Integrator	Client should expect to actively work with their integrator* to complete any items the client is unable to achieve on their own.
Testing Group	Works with Project Manager, Integration POC, and VTS to validate integration and triage issues
Friendly Tenant Testing Group	Recommended group of tenant users to test mobile access and onboarding prior to go-live.

*Client may incur additional fees from their integrator for this type of support — please confirm ahead of project start.

Client Quick Start Checklist

These items must be completed before VTS can begin configuration.

Access

1. Supported Genetec Versions: 5.9, 5.11, 5.12, 5.13
2. VTS Access to Genetec Security Center server with an admin operator account (username + password)
3.  Application ID for Genetec instance
4.  WebSDK and WebSDKStudioWindow installed
5. Required Genetec license: GSC-1SDK-VTS-ActivateRise 
   (note there may be an additional cost associated with this license, please contact Genetec for more information)
6. Email addresses added to cardholder profiles (required for syncing)
7. Custom fields for UDFs and Cardholder Groups should be accessible or visible to the integration account
8. Facility code provided (if applicable)
9. Card format selected (e.g., HID 26-bit, 48-bit, etc.)
10. Credential Range provided
11. HID Prerequisites
12. Ngrok Prerequisites

Visitor Management (if applicable)

1. Provide Credential Range
2. For projects where your operational procedures require assigning dedicated Access Control Groups (ACGs) to tenant staff or visitors, please ensure the following is configured in your physical access control system and shared with VTS:
   • ACGs are to be fully configured. These groups specify which doors visitors and staff can access within the tenant space.
   • ACG Naming Conventions:
     1. Tenant Floor Access - ACG names should reference the tenant floor they are intended for (e.g., `TenantX_Visitor Access_14th Flr`).
     2. Base Building/Lobby Access - Use a general property-level name (e.g., `PropertyName_Lobby Access` or `PropertyName_Visitors_Lobby Access`).
     3. New Building Contingency - If the project is for a new building and floors have not yet been assigned to tenants, create a generic ACG for the floors that will be occupied (e.g., `Visitor Access_14th Flr`). These can be renamed at a later time.