ACT365 Access Control Integration
Overview
ACT365 is a cloud-based access control platform that enables flexible, secure physical access management. The Nexudus integration with ACT365 automates credential provisioning and access group assignments based on customer contracts, passes, bookings, and desk assignments.Key Features
- Cloud-based management: Manage access from anywhere through ACT365’s web platform
- Mobile access: Customers can use the Nexudus Passport app to unlock doors remotely
- Automatic provisioning: Access is granted and revoked automatically based on plan changes, bookings, and pass assignments
- Check-in tracking: Optionally use door events to check customers in/out
- RFID card support: Up to 4 RFID cards per customer for physical access
- Group-based permissions: Map your inventory (passes, resources, desks) to ACT365 cardholder groups
- Booking-based temporary access: Automatic access during reservation windows
Integration Type
Cloud-based — ACT365 operates entirely in the cloud with no on-premises server requirements.Capabilities
| Feature | Supported | Notes |
|---|---|---|
| Pass-based access | ✅ Yes | Customers receive access based on their active passes |
| Plan-based access | ✅ Indirect | Plans grant access through the passes they include |
| Resource-based access | ✅ Yes | Grants temporary access during reservations |
| Desk/unit-based access | ✅ Yes | Includes support for team billing contracts |
| Visitor access | ❌ No | Not supported by this integration |
| Booking guest access | ✅ Yes | Customers added as booking guests can access spaces during booking windows |
| Check-in tracking | ✅ Yes | Door events trigger automatic check-ins |
| Mobile app access | ✅ Yes | Nexudus Passport app integration |
| Remote door unlock | ✅ Yes | Customers can unlock doors without being physically present |
How It Works
Access Control Model
ACT365 uses a cardholder group model to manage access permissions:- Cardholders represent individuals in the system (mapped to Nexudus customers)
- Cardholder Groups define collections of doors that cardholders can access
- Sites organize door controllers within your ACT365 account
- Door Controllers manage individual doors or access points
Multi-Door Support
ACT365 uses cardholder groups to grant permissions to multiple doors. Instead of mapping each door individually:- In ACT365, create a cardholder group (e.g., “Coworking Space Access”)
- Add the relevant doors to that group in ACT365
- In Nexudus, map your pass/resource/desk to that group
- Customers with that pass automatically get access to all doors in the group
You must configure which doors belong to each group in the ACT365 platform. Nexudus assigns customers to groups, but the door-to-group mapping is managed in ACT365.
Prerequisites
Before connecting Nexudus to ACT365, ensure you have:- Active ACT365 account with administrator access
- API credentials obtained from ACT365 (username and password for API authentication)
- ACT365 site configured with door controllers installed and online
- Cardholder groups created in ACT365 for different access levels (e.g., 24/7 access, business hours only)
- Nexudus location configured with plans, passes, and resources
Configuration
Step 1: Connect to ACT365
- In the Nexudus dashboard, go to Settings > Integrations
- Find ACT365 in the list and expand the settings
- Enable the Enable ACT365 integration toggle
- Enter your connection details:
- Username: Your ACT365 API username
- Password: Your ACT365 API password
- Click Save to establish the connection
- Once connected, select your ACT365 site from the dropdown menu that appears
- The configuration panels will load, showing your door controllers, cardholder groups, passes, resources, and desks
The site dropdown will show all sites available in your ACT365 account. Once you select a site, Nexudus will load the door controllers, cardholder groups, and other configuration options for that specific site. If your ACT365 account manages multiple sites, cardholders will be assigned to “All sites” (Site ID 0) automatically. For single-site accounts, cardholders are assigned to your selected site.
Step 2: Configure Presence Tracking (Optional)
ACT365 can trigger automatic check-ins when customers unlock specific doors.- In the Door Controllers section, you’ll see all doors from your ACT365 site
- For each door, choose an action:
- Nothing: Door access is tracked in ACT365 but doesn’t affect Nexudus
- Check In: Unlocking this door checks the customer in
- Check Out: Unlocking this door checks the customer out
- Toggle: Unlocking switches between checked in and checked out
- Set the main entrance to Check In
- Set the exit door to Check Out
- Set internal doors to Nothing (access granted but doesn’t affect presence)
Check-in tracking requires event processing. Nexudus syncs door events every 12 minutes and triggers the appropriate check-in action based on your configuration.
Step 3: Map Passes to Cardholder Groups
Passes are the primary way customers receive access in Nexudus. Each pass can be mapped to an ACT365 cardholder group.- In the Passes section, you’ll see all passes configured for this location
- For each pass, select the ACT365 Cardholder Group that customers should be assigned to when they hold that pass
- 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 an ACT365 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
| Pass Name | ACT365 Group | Purpose |
|---|---|---|
| 24/7 Access Pass | 24/7 Members | Round-the-clock building access |
| Business Hours Pass | Business Hours | Access only during operating hours |
| Meeting Room Pass | Meeting Rooms | Access to meeting room zones |
Step 4: Map Resources to Cardholder Groups
Resources (meeting rooms, event spaces, etc.) can require specific access permissions for bookings.- In the Resources section, you’ll see all resources configured for this location
- For each resource, select the ACT365 Cardholder Group required to access that space
- 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
| Resource Name | ACT365 Group | Purpose |
|---|---|---|
| Conference Room A | Meeting Room A | Access to specific meeting room |
| Event Space | Event Hall | Access to event space for bookings |
| Private Office | Private Offices | Access to private office area |
Resource-based access is temporary and booking-specific. A customer only receives access during their booking window, even if they don’t hold a general access pass.
Step 5: Map Desks/Units to Cardholder Groups
Floor plan desks and units can grant access to specific areas when included in a customer’s contract.- In the Desks/Units section, you’ll see all desks from your floor plans
- For each desk, select the ACT365 Cardholder Group required to access that area
- 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
| Desk/Unit Name | ACT365 Group | Purpose |
|---|---|---|
| Private Office #101 | Private Office Floor 1 | Access to first-floor private office area |
| Dedicated Desk Zone A | Desk Area A | Access to dedicated desk zone A |
| Studio #5 | Studio Access | Access to individual studio unit |
Step 6: Save Configuration
- Review all mappings to ensure they’re correct
- Click Save to apply the configuration
- Nexudus will immediately start provisioning access for customers based on the new mappings
How Access is Managed
When Access is Granted
Nexudus automatically grants ACT365 access when:- Contract starts: Customer begins a contract on a plan → receives passes included in that plan → assigned to corresponding ACT365 groups
- Pass activated: Customer receives a pass directly (not via a contract) → assigned to the mapped ACT365 group
- Booking created: Customer books a resource → granted access to resource’s group 15 minutes before booking start time
- Desk added to contract: Desk is added to an active contract → customer receives access to the desk’s mapped group
- 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
Nexudus automatically revokes ACT365 access when:- Contract ends or cancelled: Customer loses passes from that contract → removed from corresponding ACT365 groups
- Pass expires: Pass validity ends or usage is consumed → removed from mapped ACT365 group
- Booking ends or cancelled: Booking time expires or is cancelled → access to resource’s group is removed
- Desk removed from contract: Desk is removed from contract → access to desk’s group is revoked
- Customer deactivated: Customer account is deactivated → all ACT365 access removed
- Check-in expires: If customer checks out or check-in expires, certain temporary access may be revoked
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
- Event processing: Door events are synced every 12 minutes for check-in tracking
If a customer should have access but doesn’t, the system automatically retries access provisioning. Check the Business Checkup page for any integration errors.
Mobile App Experience
Customers can use the Nexudus Passport mobile app to unlock doors remotely.Setup for Customers
- Customer downloads the Nexudus Passport app (iOS or Android)
- Signs in with their Nexudus credentials
- App detects ACT365 integration is active
- Customer can view available doors and unlock them remotely
Using Mobile Access
- Customer opens the Nexudus Passport app
- Navigates to Unlock Doors section
- Views list of doors they currently have access to
- Taps Unlock to remotely unlock a door
RFID Card Management
ACT365 supports traditional RFID access cards alongside mobile access. To assign cards:- Go to Operations > Customers
- Select the customer
- In their profile, enter card IDs in the Access Card ID field
- Separate multiple cards with commas:
123456,789012,345678(up to 4 cards) - Save the customer profile
- No card: Cardholder is disabled in ACT365 (mobile-only access)
- Card assigned: Cardholder is enabled for both physical and mobile access
- Card removed: Cardholder is disabled again (reverts to mobile-only)
Only numeric card IDs are supported. Non-numeric cards are automatically filtered out.
Troubleshooting
Customer has an active contract but can't access doors
Customer has an active contract but can't access doors
Possible causes:
-
Pass not mapped: The passes included in the customer’s plan are not mapped to any ACT365 cardholder groups
- Solution: Go to Settings > Integrations > ACT365 and map the relevant passes to cardholder groups
-
Pass expired or inactive: The customer’s pass has expired or hasn’t started yet
- Solution: Check the customer’s passes under their profile to verify validity windows
-
Cardholder not created: The customer wasn’t created in ACT365
- Solution: Check the Business Checkup page for integration errors, or manually trigger an update by editing and saving the customer’s profile
-
Access group permissions: The ACT365 cardholder group exists but isn’t assigned to any doors
- Solution: In ACT365, verify the cardholder group includes the correct door controllers
-
Card not assigned: Customer exists in ACT365 but is disabled (no RFID card)
- Solution: Assign an RFID card in the customer’s Access Card ID field, or ensure mobile access is working
Booking access not working
Booking access not working
Possible causes:
-
Resource not mapped: The booked resource is not mapped to an ACT365 cardholder group
- Solution: Map the resource to a cardholder group in Settings > Integrations > ACT365
-
Booking too far in future: Access is only granted 15 minutes before booking start time
- Solution: Wait until booking is within 15 minutes of start time
-
Booking not confirmed: Some resources require booking confirmation
- Solution: Confirm the booking if it’s in pending state
Mobile app showing no doors available
Mobile app showing no doors available
Possible causes:
-
No active access: Customer doesn’t have any passes or bookings that grant access
- Solution: Verify customer has an active pass or upcoming booking mapped to ACT365 groups
-
Cardholder disabled: Customer has no RFID card assigned and cardholder is disabled
- Solution: Assign a dummy RFID card or contact ACT365 support about enabling cardholders without physical cards
-
App not refreshed: Door list hasn’t updated after access was granted
- Solution: Customer should pull down to refresh the door list in the app
Check-ins not created from door events
Check-ins not created from door events
Possible causes:
-
Door action not configured: Door controller is set to “Nothing” instead of a check-in action
- Solution: Configure the door controller action in Settings > Integrations > ACT365
-
Event processing disabled: Setting
ACT365.DoNotProcessEventsis enabled- Solution: Ensure this setting is disabled in your business settings
-
Sync delay: Background task runs every 12 minutes
- Solution: Wait up to 12 minutes for the next event sync cycle
Integration connection failing
Integration connection failing
Cause: Your ACT365 API credentials have expired or are incorrect.Solution:
- Verify your username and password in the ACT365 admin portal
- Reconnect the integration with updated credentials
- Check that your ACT365 account has API access enabled
- Contact ACT365 support if credentials are correct but connection fails
Monitoring Integration Errors
Nexudus monitors your access control integration and alerts you to any issues that need attention.Business Checkup Dashboard
Access control integration errors are displayed on the Business Checkup page:- Go to Home > Important Items in the dashboard, or
- Navigate directly to dashboard.nexudus.com/dashboards/checkup
- Look for the Access Control Integration tile
- If there are errors, the tile will be displayed in red
What Gets Flagged
- Authentication failures: Expired credentials or invalid API tokens
- Provisioning errors: Failed attempts to create or update customer access
- Configuration issues: Missing or invalid cardholder group mappings
- Synchronization problems: Delays or failures in updating access permissions
- The customer affected
- The nature of the problem
- When the error occurred
- Suggested actions to resolve it
Nexudus automatically retries failed operations. If errors persist, check the Business Checkup page for detailed information and follow the suggested resolution steps.
Security Considerations
Data Shared with ACT365
When provisioning access, Nexudus shares the following information with ACT365:- Customer data: First name, last name, email address, mobile phone
- External ID: Nexudus customer ID (used to link records between systems)
- RFID cards: Card IDs from the Access Card ID field
- Billing information
- Payment details
- Contract specifics (only cardholder group assignments)
- Personal notes or custom fields
Credential Management
- Physical cards: Managed entirely in ACT365; Nexudus only assigns cardholder groups
- Mobile credentials: Nexudus triggers unlock commands but doesn’t handle credentials
- User passwords: Never shared with Nexudus; authentication to ACT365 is handled by ACT365
Related Documentation
Best Practices
Cardholder Group Organization
Create cardholder groups based on access levels, not products or plans:- ✅ Good: “24/7 Access”, “Business Hours”, “Meeting Rooms”, “Private Offices”
- ❌ Avoid: “Hot Desk Plan”, “Dedicated Desk Plan” (these are billing products, not access types)
Technical Details
For developers and IT administrators
For developers and IT administrators
API Architecture
- Base URL:
https://userapi.act365.eu/api/ - Authentication: Resource Owner Password Credentials (username/password)
- Token endpoint:
https://userapi.act365.eu/api/account/login - Token type: Bearer token (stored in session)
- Rate limiting: 30 requests per minute per username (semaphore-based across multiple servers)
Key Endpoints
- Cardholders:
/api/cardholder(GET, POST, PUT, DELETE) - Cardholder Groups:
/api/cardholdergroup - Doors:
/api/door - Door Groups:
/api/doorgroup - Sites:
/api/sites - Access Events:
/api/logeventsofcategory?category=7&fromafter={date}&maxlimit=100 - Doors for Cardholder:
/api/doorsofcardholder?cardholderid={id} - Remote Unlock:
POST /api/doorwith{Door: "{doorId}", Command: "Pass"}
Synchronization
- Access updates: Debounced by 5 seconds per customer to batch rapid changes
- Background task: Polls door events every 12 minutes for check-in tracking
- Event query: Uses
category=7for access events, queries fromlastEventDate + 1 second - Event limit: Maximum 100 events per request
- Distributed locking: Prevents race conditions in multi-server deployments
- User provisioning: Lazy creation on first inventory assignment
- Cardholder updates: Created/updated/deleted as inventory changes
- Access signature hashing: Prevents unnecessary API calls when access hasn’t changed
Site Assignment
- Multi-site accounts: Cardholders assigned to “All sites” (Site ID 0)
- Single-site accounts: Cardholders assigned to configured Site ID
- Site ID setting:
Act365.SiteIdbusiness setting
External IDs
- Customers:
ExternalIDset to Nexudus coworker ID (integer) - Visitors:
ExternalIDset toNEXVIS-{visitorId} - Lookup: Cardholders retrieved via
/api/cardholder?externalid={coworkerId}
Cardholder Model
RFID Card Management
- Card ID field: Comma-separated numeric IDs in
AccessCardIDfield (up to 4 cards) - Non-numeric cards: Automatically filtered out
- No cards: Cardholder disabled in ACT365 (mobile-only access via Nexudus Passport app)
- Card assignment: Cardholder enabled for both physical and mobile access
Business Settings Reference
| Setting | Purpose |
|---|---|
Act365.Enable | Integration enabled flag (“true”/“false”) |
Act365.Username | ACT365 API username for authentication |
Act365.Password | ACT365 API password for authentication |
Act365.SiteId | Site ID for cardholder assignment |
ACT365.DoNotProcessEvents | Disable event processing (“true”/“false”) |
ACT365.LastEventDate | Last processed event timestamp (ISO 8601) |
ACT365.Controller.Id_{doorId}.Action | Check-in action per door (Nothing/CheckIn/CheckOut/Toggle) |
Contract-Based Desk Access
- Desk access determined by active contracts:
coworker.ActiveContracts().SelectMany(x => x.Desks) - Team billing support: Customer receives access to desks in paying member’s contracts
- Multi-site organizations: Access groups managed per site
- Desk mapping: Each desk mapped to comma-separated cardholder group IDs
Access Update Logic
- Passes: Active passes from contracts + shared passes from paying member
- Check-ins: Passes from open check-ins (maintains access during session)
- Bookings: Resources with bookings starting within 15 minutes
- Booking guests: Resources from bookings where customer is a visitor
- Desks: Desks from active contracts (own + team billing)
- Cardholder groups: Aggregated list of unique group IDs
- Cardholder provisioning: Create/update cardholder with aggregated groups
- Card status: Enable if cards exist, disable if no cards (mobile-only)
Event Processing
- Event category:
7for access granted events - Event date format:
dd/MM/yyyy HH:mm(e.g., “25/12/2024 14:30”) - Event retention: Events processed from
lastEventDate, limited to last 24 hours if gap > 1 day - Pagination: Results returned in batches of 100
- Check-in trigger: Only “Open” actions with matching door controller configuration
Error Handling
- Authentication failures: Stored in business log entries
- Provisioning errors: Automatic retry with exponential backoff
- Business Checkup: Integration errors displayed on dashboard
- Distributed locks: Prevent concurrent updates to same customer