Skip to main content

AMAG

Updated

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

  • 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
  • ACS Write: Create and manage ACS users in Activate
  • Tenant Self Serve: Manage your employee suite and building access in Activate

 

Visitor Management Overview (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 Prerequisites

These items must be completed before the VTS team can begin integration.

Access

  1. Create AMAG admin SQL user with read/write access
  2. Database names
    • Import DB (example: MultiMAX)
    • Export DB (example: MultiMAXImport)
  3. Facility code (if applicable)
  4. Credential Range and ensure sufficient licensing for access control, API usage, and Ngrok if applicable (note there may be an additional cost associated with this license, please contact your provider for more information)
  5. Card format selected (e.g., HID 26-bit, 48-bit, etc.)
  6. AMAG version 8.9, 9.0, 9.1, 9.2, 9.3 is required
  7. Email addresses added to cardholder profiles (required for syncing)
  8. Custom fields for UDFs and Cardholder Groups should be accessible or visible to the integration account
  9. AMAG Field Values
    • Server URL (MSSQL)
    • Username
    • Password
    • Company ID (property identifier in AMAG)
    • Customer Code (Facility Code for cardholder company)
    • Email Title Number (dropdown value in AMAG)
  10. HID Prerequisites
  11. Ngrok Prerequisites

 

Visitors

  1. Provide Visitor Credential Range
  2. Define any visitor-specific configurations (e.g., visitor credential expiry or auto-activation logic)
  3. 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 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.

Related articles