Skip to main content

CCURE

Updated

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

 

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 Prerequisites

These items must be completed before VTS begins the integration.

 

Access

  1. Supported CCURE Versions: 2.8, 2.9, 3.0 (SP5 service pack or higher required for API support)
  2. Create admin account in CCURE (suggested: ActivateUser)
  3. Whitelist VTS Activate IPs on CCURE firewall
  4. Ensure CCURE has the VTS TenEx Software Integration License 
    *may incur an additional fees
    • For versions 2.8 and above, the insertion script is: InsertLicenseOption /U /V /S:“LOCALHOST” /N:“Rise Buildings - Rise Software Integration - Integration” /A:“Rise Buildings” /G:713347a7-616c-40c7-83ec-bfea95218b42 /C:2 /P:0
    • Note: the command prompt must be run as an administrator in the correct directory. Usually, this directory is C:\Program Files (x86)\Tyco\Crossfire\Tools
    • Please refer to this video to run injection script
  5. Ensure Victor Web Services is installed and running (IIS required)
    *may incur an additional fees
    • Please refer to this guide to configure Victor Web Services.
  6. Enable “Allow multiple cards” in CCURE if HID is also used
  7. Ensure all users in CCURE have email addresses populated
  8. Provide Credential range
  9. Gather Credentials
    • CCURE admin username/password (send securely via OneTimeSecret)
    • Client ID (from CCURE environment config)
    • CHUID/Card Format used
    • Facility Code (if used)
    • Partition ID (if used)
  10. HID Prerequisites
  11. Ngrok Prerequisites

Visitors

  1. Provide Visitor 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.

Related articles