Kadence Agent allows users to:
Check into desk, private office, and onsite bookings automatically when they arrive at the office
View current day bookings from their desktop system tray
Create automatic bookings for users on the day when they arrive to the office without one
Receive update notifications
Prerequisites
You must be a Global Admin or Building Admin
You’ll need public IP address(es) for each building
Kadence Agent must be installed and logged in on users' devices
Enable Automatic Check-In with Kadence Agent
1. Find Your Building’s Public IP Address
Kadence Agent uses your building's public IP to confirm user presence. You can find this by:
Option A: Web Search
Search "What is my IP" in any search engine
Copy the public IP address shown
Option B: Router Admin Page
Enter the router IP (e.g. 192.168.1.1) in a browser
Login with admin credentials
Locate the public IP under sections like "Status" or "WAN"
2. Enable Kadence Agent for a Building
Go to Buildings from the left-hand menu
Click the three dots (⋮) next to a building → Edit Building
Click the Kadence Agent tab
You can choose to inherit or override global settings related to Kadence Agent.
Toggle on Automatic Check-in
Enter your public IP address(es) (IPv4, IPv6, or CIDR range)
Click Save
Only desk, private office, and onsite bookings are currently supported for automatic check in.
Manage Kadence Agent Updates
How It Works
Manually installed apps: Users are notified and can install updates
MDM-managed apps: Updates must be pushed by IT; users don’t receive update prompts
To Enable Auto-Update (Admins)
Go to Settings → Company → Kadence Agent
Toggle Automatic App Updates ON (affects manually installed versions only)
Click Save
Automatic Booking with Kadence Agent
When enabled, Kadence Agent will automatically book and check in users who arrive onsite without a prior booking (if capacity and credits allow).
Enable Globally
Go to Settings → Company → Kadence Agent
Toggle Enable automatic bookings ON
Choose to apply settings:
Click Save
Enable Per Building
Go to Buildings → Edit Building
Go to Settings tab
Set to Override global settings
Toggle ON Enable automatic booking
Click Save
Please note, automatic bookings:
Will not override existing bookings
Will not book if resource is full or user lacks booking credits
May be impacted by shared public IPs and prevent accurate location detection
Manage Manual Check-In Settings
You can control whether users can manually check in per resource type:
Go to Settings → Resources
Click the resource type (e.g., Desk)
Toggle Manual Check-In ON or OFF
Click Save
What Happens if Manual Check-In is Disabled?
Auto-release, and early check-in/out are also disabled
If API integration is not in place, disabling manual check-in disables all check-in paths
Re-enabling manual check-in requires manually re-enabling related features.
Distribute & Install Kadence Agent
Option 1: Manual Installation
Click your profile picture → Kadence Agent App
Choose Windows or Mac version
Follow install prompts
The Kadence icon will appear in the system tray
Option 2: Microsoft Intune Distribution
Kadence Agent provides two MSI installer variants for enterprise deployment:
System MSI (x64.msi)
Install path:
C:\Program Files\KadenceAgentAuto-start scope: All users on the machine
Use case: Intune, SCCM, Endpoint Central — recommended for shared/hot-desk devices
Per-user MSI (x64-peruser.msi)
Install path:
%LOCALAPPDATA%\Programs\KadenceAgentAuto-start scope: Installing user only
Use case: Single-user laptops where admin rights are not available
Deploying the System MSI (recommended for Intune)
Download the system MSI from your Kadence account → Alternative versions (look for the [msi, system] variant)
In Microsoft Intune Admin Center, add a new Line-of-business app and upload the MSI
Set Install behavior to System
Set the install command to:
msiexec /i kadence-agent-latest-x64.msi /qnAssign to device or user groups
Monitor deployment
The agent will auto-start at next user login via a registry Run key (HKLM). No reboot is required.
Deploying the Per-user MSI
Download the per-user MSI (look for the [msi, per-user] variant)
Set Install behavior to User
Set the install command to:
msiexec /i kadence-agent-latest-x64-peruser.msi /qn
Important: Do not deploy the per-user MSI with System install behavior — the Windows Installer service cannot access user-profile paths when running as SYSTEM, causing the install to fail silently.
Upgrading from a previous version
The MSI handles upgrades automatically — deploying the new version will remove the old one and install the new one in a single transaction. No manual uninstall is needed. If the agent is running during the upgrade, it will be closed automatically and relaunched after the install completes.
If upgrading from agent versions prior to 9.1 that were deployed via the per-user MSI, a one-time clean install may be required.
Earlier versions had a mixed install context issue where files installed to C:\Program Files but registration was per-user, causing upgrades to fail. See the troubleshooting section below.
Option 3: Jamf Pro
Download app package via your Kadence account → Alternative versions
Upload the Kadence Agent to Jamf
Create a Policy to deploy the Agent
Validate the installation
Recommended: Suppress “Managed Login Items Added” notification
In Jamf Pro, go to Configuration Profiles
Click New
Configure the profile:
Level: Computer
Payload: Notifications
Add the following settings:
Bundle ID:
com.apple.btmnotificationagentApp Name: (leave blank)
Notifications: Disable
Critical Alerts: Disable
Scope the profile to a test device
Click Save
Option 4: Apple Business Manager (Coming Soon)
Currently unavailable until the app is listed in the Apple App Store. We’ll update once supported.
Frequently Asked Questions
Automatic Check-In
Can I disable manual check-in for specific resource types?
Can I disable manual check-in for specific resource types?
Yes. You can disable manual check-in by resource type following this guide.
What if API or Kadence Agent is not enabled?
What if API or Kadence Agent is not enabled?
Disabling manual check-in removes all check-in ability for users so we do not recommend this.
Does Kadence Agent collect IPs related to our user’s home network?
Does Kadence Agent collect IPs related to our user’s home network?
Every HTTP(S) request to any web service includes the client’s network address as part of the internet and HTTP standard - this is how servers know where to send responses. Kadence makes use of this standard behaviour only.
The client’s public IP is automatically available in the request metadata. Kadence evaluates that address in memory against the organisation’s configured allow-listed ranges, makes a check-in decision, and then discards it. The IP is never stored in databases or logs.
App Installation
Is the app free?
Is the app free?
Yes, included in all plans.
Who can download the app?
Who can download the app?
Any person with access to the Kadence platform.
Which devices are supported?
Which devices are supported?
Kadence Agent currently only supports PC and Mac (no mobile/tablet).
Can the Kadence Agent log users in automatically?
Can the Kadence Agent log users in automatically?
No, the Kadence Agent cannot currently log users in automatically. However it will retain log ins perpetually unless the user logs themselves out, the app is uninstalled, or the user is inactive for over 28 days.
What's the difference between the system and per-user MSI?
What's the difference between the system and per-user MSI?
The system MSI installs to C:\Program Files\KadenceAgent and auto-starts for all users on the machine (HKLM registry).
The per-user MSI installs to the current user's AppData\Local\Programs and auto-starts only for that user (HKCU registry).
Use the system MSI for shared devices and Intune/SCCM deployments; use the per-user MSI for single-user laptops.
Can I deploy the MSI silently?
Can I deploy the MSI silently?
Yes. Use msiexec /i kadence-agent-latest-x64.msi /qn for a fully silent install. Add /l*v C:\Temp\kadence-install.log for verbose logging if troubleshooting.
Updates
Will I get update notifications?
Will I get update notifications?
Only if automatic updates is enabled at the building and/or global level.
Can I opt out of updates?
Can I opt out of updates?
No, but you can manage your personal notifications.
Automatic Bookings
Will automatic bookings override existing bookings?
Will automatic bookings override existing bookings?
No, automatic bookings will never override existing bookings.
Will automatic bookings respect booking credits and capacity?
Will automatic bookings respect booking credits and capacity?
Yes, automatic bookings will respect booking credits and/or onsite capacity if they are enabled.
Troubleshooting
MSI upgrade removes the old agent but doesn't install the new one
MSI upgrade removes the old agent but doesn't install the new one
This affects upgrades from agent versions prior to 26.6 that were deployed via the per-user MSI.
Earlier versions had a mixed install context (files in C:\Program Files but registered as per-user), which causes Windows Installer to block the upgrade. To fix:
Uninstall the current agent
Delete any remaining files from
C:\Program Files\KadenceAgent,%LOCALAPPDATA%\Programs\KadenceAgent, and%AppData%\Kadence AgentRemove the registry value
co.kadence.kadence-agentfromHKCU\Software\Microsoft\Windows\CurrentVersion\Runif presentInstall the new version
This is a one-time issue — subsequent upgrades will work automatically.
SSO login loops repeatedly for standard (non-admin) users
SSO login loops repeatedly for standard (non-admin) users
This can occur on machines where an older version was installed with a mixed install context, leaving auth tokens in a path inaccessible to standard users. Follow the clean install steps above to resolve.
New installs with version 26.6+ use consistent install paths and are not affected.
Agent doesn't auto-start after a per-machine MSI install
Agent doesn't auto-start after a per-machine MSI install
Verify the registry key exists: reg query
"HKLM\Software\Microsoft\Windows\CurrentVersion\Run" /v KadenceAgent
If missing, manually add the Run key.
Per-user MSI fails silently when deployed via Intune as System
Per-user MSI fails silently when deployed via Intune as System
The per-user MSI must be deployed with User install behavior, not System. The Windows Installer service running as SYSTEM cannot access user-profile directories. Use the system MSI (x64.msi) for System-context deployments.
Need Help?
For support, reach out to:
📩 [email protected]
For more helpful articles see:
📚 Kadence Help Center













