​

Genetec Access Control Integration

​

Overview

​

Key Features

• Cloud-based management: Manage access through Genetec Security Center’s web interface
• Automatic provisioning: Access is granted and revoked automatically based on plan changes, bookings, and pass assignments
• RFID card support: Single RFID card per customer with facility code configuration
• PIN code support: Optional PIN codes for keypad access
• Group-based permissions: Map your inventory (passes, resources, desks) to Genetec cardholder groups
• Booking-based temporary access: Automatic access during reservation windows
• Partition support: Multi-site organizations can configure default partitions

​

Integration Type

• Network Bridge: Secure tunnel through https://bridge.nexudus.com/{device_id}/WebSdk/
• Port Forwarding: Direct connection to http://public_ip:4590/WebSdk/ (requires firewall configuration)

​

Capabilities

​

How It Works

​

Access Control Model

• Cardholders represent individuals in the system (mapped to Nexudus customers)
• Cardholder Groups define collections of doors that cardholders can access
• Credentials are physical access methods (RFID cards, PIN codes) linked to cardholders
• Partitions organize entities within multi-site Genetec deployments

​

Multi-Door Support

1. In Genetec Security Center, create a cardholder group (e.g., “24/7 Building Access”)
2. Add the relevant doors to that group in Genetec
3. In Nexudus, select that group from the dropdown when mapping your pass/resource/desk
4. Customers with that pass automatically get access to all doors in the group

​

Prerequisites

1. Genetec Security Center installed on-premise with administrator access
2. API credentials (username and password for API authentication)
3. Network connectivity — Either:
   • Network Bridge configured: Device ID from your Nexudus Network Bridge installation
   • Port forwarding configured: Public IP address with port 4590 forwarded to your Genetec server
4. Genetec system configured with door controllers installed and online
5. Cardholder groups created in Genetec for different access levels (e.g., 24/7 access, business hours only)
6. Nexudus location configured with plans, passes, and resources
7. (Optional) Default partition GUID if using Genetec’s partition feature for multi-site organizations

​

Configuration

​

Step 1: Connect to Genetec

1. In the Nexudus dashboard, go to Settings > Integrations
2. Find Genetec in the list and expand the settings
3. Enable the Enable Genetec integration toggle
4. Enter your connection details (fields appear when toggle is enabled):
   • Genetec server address: Choose one of the following:
     • Network Bridge: https://bridge.nexudus.com/{DEVICE_ID}/WebSdk/ (replace {DEVICE_ID} with your Bridge device ID)
     • Port Forwarding: http://YOUR_PUBLIC_IP:4590/WebSdk/ (replace YOUR_PUBLIC_IP with your public IP address)
   • Genetec username: Your Genetec API username
   • Genetec password: Your Genetec API password
   • Default partition (optional): The GUID of the default partition for new cardholders (for multi-site Genetec deployments)
5. Click Save to establish the connection
6. Once connected successfully, the configuration panels for passes, resources, and desks will load below

​

Step 2: Map Passes to Cardholder Groups

1. In the Passes section, you’ll see all passes configured for this location
2. For each pass, select a Genetec access group from the dropdown menu
   • The dropdown shows all cardholder groups available in your connected Genetec system
   • Groups are automatically retrieved when you save the connection settings
3. Leave blank if a pass should not grant physical access

• When a customer has an active contract on a plan that includes passes, they automatically receive those passes
• If the pass is mapped to a Genetec cardholder group, the customer is added to that group
• When the pass expires or is consumed, access is revoked
• Time-limited passes (e.g., day passes with validity windows) automatically grant and revoke access at the appropriate times

​

Step 3: Map Resources to Cardholder Groups

1. In the Resources section, you’ll see all resources configured for this location
2. For each resource, select a Genetec access group from the dropdown menu
3. Leave blank if resource bookings should not grant physical access

• When a customer books a resource, Nexudus grants them access 15 minutes before the booking starts
• Access is automatically revoked when the booking ends
• If the booking is cancelled, access is removed immediately

​

Step 4: Map Desks/Units to Cardholder Groups

1. In the Desks/Units section, you’ll see all desks from your floor plans
2. For each desk, select a Genetec access group from the dropdown menu
3. Leave blank if desk assignments should not grant physical access

• When a desk is added to a customer’s contract, they receive access to the mapped group
• Access is granted when the contract starts and revoked when it ends
• Team billing support: If a customer uses team billing (merged billing), they also receive access to desks included in the paying member’s contracts

​

Step 5: Save Configuration

1. Review all mappings to ensure they’re correct
2. Verify group selections match your intended access levels
3. Click Save to apply the configuration
4. Nexudus will immediately start provisioning access for customers based on the new mappings

​

How Access is Managed

​

When Access is Granted

1. Contract starts: Customer begins a contract on a plan → receives passes included in that plan → assigned to corresponding Genetec cardholder groups
2. Pass activated: Customer receives a pass directly (not via a contract) → assigned to the mapped Genetec cardholder group
3. Booking created: Customer books a resource → granted access to resource’s group 15 minutes before booking start time
4. Desk added to contract: Desk is added to an active contract → customer receives access to the desk’s mapped group
5. Booking guest added: Non-customer is added as a guest on a booking → granted access to resource’s group for the booking duration

​

When Access is Revoked

1. Contract ends or cancelled: Customer loses passes from that contract → removed from corresponding Genetec cardholder groups
2. Pass expires: Pass validity ends or usage is consumed → removed from mapped Genetec cardholder group
3. Booking ends or cancelled: Booking time expires or is cancelled → access to resource’s group is removed
4. Desk removed from contract: Desk is removed from contract → access to desk’s group is revoked
5. Customer deactivated: Customer account is deactivated in Nexudus → cardholder is deactivated in Genetec

​

Cardholder Activation Status

• Active: Cardholder has at least one group assignment and credentials configured
• Inactive: Cardholder has no group assignments or credentials have been removed

​

Access Update Timing

• Immediate updates: Contract changes, pass assignments, and customer deactivations trigger access updates within seconds
• Booking lead time: Booking access is granted 15 minutes before the booking start time
• Background processing: Access updates are queued in background jobs to handle high volumes efficiently
• Distributed locking: Prevents concurrent updates to the same customer across multiple servers

​

RFID Card and PIN Management

​

Assigning RFID Cards

1. Go to Operations > Customers
2. Select the customer
3. In their profile, enter the following:
   • Access Card ID: The card number (e.g., 12345)
   • Key Fob Number: The facility code (e.g., 100)
4. Save the customer profile

• Genetec uses the Wiegand Corporate 1000 format by default
• Format: WiegandCorporate1000CredentialFormat(facilityCode, cardNumber)
• Both facility code and card number are required

​

Assigning PIN Codes

1. Go to Operations > Customers
2. Select the customer
3. In their profile, enter a PIN code in the Access PIN Code field (e.g., 1234)
4. Save the customer profile

• PIN codes are separate credentials from RFID cards
• A customer can have both a card and a PIN code
• PINs are stored as “Keypad” credential type in Genetec
• Removing the PIN code from Nexudus deletes the PIN credential in Genetec

​

Credential Management Logic

1. Creates cardholder: If the customer doesn’t exist in Genetec (lookup by email)
2. Updates cardholder: Updates first name, last name, and email if cardholder exists
3. Manages card credential:
   • If card ID is present: Creates or updates the “UndecodedWiegand” credential
   • If card ID is removed: Deletes the card credential
4. Manages PIN credential:
   • If PIN is present: Creates or updates the “Keypad” credential
   • If PIN is removed: Deletes the PIN credential
5. Updates group memberships: Adds/removes cardholder from groups based on passes, bookings, and desk assignments

​

Troubleshooting

​

Monitoring Integration Errors

​

Business Checkup Dashboard

1. Go to Home > Important Items in the dashboard, or
2. Navigate directly to dashboard.nexudus.com/dashboards/checkup
3. Look for the Access Control Integration tile
4. If there are errors, the tile will be displayed in red

​

What Gets Flagged

• Authentication failures: Invalid credentials or connection errors
• Provisioning errors: Failed attempts to create or update customer access
• Configuration issues: Missing or invalid cardholder group mappings
• Credential errors: Failed attempts to create or update cards/PINs

• The customer affected
• The nature of the problem
• When the error occurred
• Suggested actions to resolve it

​

Security Considerations

​

Data Shared with Genetec

• Customer data: First name, last name, email address
• Credentials: Card IDs, facility codes, PIN codes
• External ID: Nexudus uses the customer’s email as the lookup key

• Phone numbers (unless part of customer name fields)
• Billing information
• Payment details
• Contract specifics (only cardholder group assignments)
• Personal notes or custom fields

​

Network Security

• HTTPS encryption: All communication uses HTTPS (SSL/TLS)
• Basic authentication: Username and password sent with each request (over HTTPS)
• API keys: Nexudus uses dedicated license keys for Genetec API access
• Distributed locking: Prevents race conditions and concurrent updates to the same customer

​

Credential Management

• Physical cards: Managed in both Nexudus and Genetec; always assign through Nexudus
• PIN codes: Stored in Nexudus and synced to Genetec
• User passwords: Never shared with Nexudus; authentication is handled by Genetec

​

Related Documentation

• Access Control Overview
• Passes Configuration
• Plans & Contracts
• Resource Bookings
• Check-ins

​

Best Practices

​

Cardholder Group Organization

• ✅ Good: “24/7 Building Access”, “Business Hours Access”, “Meeting Room Zones”, “Private Office Areas”
• ❌ Avoid: “Hot Desk Plan”, “Dedicated Desk Plan” (these are billing products, not access types)

​

Naming Conventions

• Create descriptive cardholder group names in Genetec that make them easy to identify in the dropdown
• Avoid overly long group names that are difficult to read in the admin panel
• Document group-to-door mappings in Genetec for future reference

​

Card Management

• Use consistent facility codes across all cards at a location
• Keep facility code and card number separate (don’t combine into Access Card ID)
• Document your facility code for future card provisioning
• Test new cards immediately after provisioning to ensure proper configuration

​

Partition Configuration

• If using Genetec partitions for multi-site organizations, configure the Default Partition setting
• Partition GUID should match your primary partition in Genetec Security Center
• All cardholders created by Nexudus will be assigned to this partition

​

Access Signature Optimization

• Nexudus uses access signatures to avoid unnecessary API calls
• An access signature is a hash of all groups a customer should have access to
• If the signature hasn’t changed, Nexudus skips the update
• This optimization reduces API traffic and improves performance

​

Technical Details

{
  "Id": "guid",
  "Name": "First Last",
  "FirstName": "First",
  "LastName": "Last",
  "EmailAddress": "email@example.com",
  "State": "Active",
  "Groups": [],
  "Parents": ["guid1", "guid2"],
  "Credentials": ["credentialGuid1", "credentialGuid2"]
}

{
  "Id": "guid",
  "CardHolder": { "Id": "cardholderGuid" },
  "Type": "Keypad" | "UndecodedWiegand",
  "State": "Active"
}

{
  "Id": "guid",
  "Name": "Group Name"
}

{
  "Response": {
    "Result": {
      // Actual entity data here
    }
  }
}

{
  "Results": [
    {
      "Guid": "entity-guid",
      "Name": "Entity Name"
    }
  ]
}