Desktop
Cadence Desktop is an optional companion for consented audio capture during a Cadence meeting. It is signed, auto-updating, and available for supported macOS and Windows devices.
Before you deploy
Use this guide when your organization manages employee devices through endpoint management. Your Cadence admin must first enable Desktop for the people and meetings where it is allowed.
Installing Cadence Desktop does not start recording. Each meeting still requires in-product pairing and consent. People can see the recording state and stop or revoke capture.
Supported installers
| Platform | Device architecture | Installer | Recommended management path | | --- | --- | --- | | macOS | Apple silicon or Intel | Signed and notarized DMG | Deploy the vendor DMG in an MDM workflow that supports disk images. If a PKG is required, package the released app in your approved internal workflow and validate it on a clean managed Mac before broad release. | | Windows | x64 or ARM64 | Signed MSI | Deploy the released MSI through your Windows endpoint-management tool using its standard MSI detection and uninstall handling. |
Get the current installer from Settings → Audio or the signed Cadence download channel. Record the file name, signature, and installer source in your change record.
System and network requirements
- A supported 64-bit macOS or Windows device matching the installer architecture.
- Permission to install managed software and allow the Cadence app to run.
- Network access to Cadence and the signed download/update channel. Do not block update checks without a replacement update process.
- An active Cadence account and a meeting eligible for your organization’s audio-capture policy.
Recommended rollout
- Assign the current installer to a small pilot group of approved, managed devices on every operating system and architecture you support.
- Preserve the vendor signature. Do not re-sign, modify, or repackage the Windows MSI. For a macOS PKG wrapper, preserve the signed app and validate Gatekeeper behavior after packaging.
- Confirm Cadence Desktop opens, relaunches, and pairs from Settings → Audio.
- Run a consented test meeting. Verify the recording state, then verify stop and revoke.
- Promote by ring only after the pilot passes on each operating system in scope.
MDM configuration notes
macOS
- Scope the DMG/app deployment to supported Mac hardware and a pilot smart group first.
- If your MDM accepts only PKGs, test install, launch, relaunch, and update on a clean managed Mac after packaging.
- Do not bypass macOS security prompts with a broad exception; use your normal managed-app policy.
Windows
- Upload the signed MSI as a line-of-business or Win32 app through your endpoint tool’s standard MSI flow.
- Use the MSI product code or your tool’s MSI detection to avoid reinstall loops.
- Pilot x64 and ARM64 packages separately where both device types exist.
Updates and troubleshooting
Cadence Desktop includes an auto-updater. Keep the update path available and test each release in a pilot ring before broad assignment.
| Symptom | Admin check |
|---|---|
| Installer will not run | Confirm the device architecture matches the package and that it came from the signed Cadence channel. |
| App does not launch after macOS deployment | Confirm the signed app was preserved in the DMG/PKG workflow and test on a clean managed Mac. |
| App installs but cannot pair | Confirm the user can sign in, Desktop audio is enabled for the organization, and the user is in an eligible meeting. |
| Recording does not begin | Installation is not consent. Confirm meeting pairing and consent, then check the visible recording state. |
| Update does not apply | Confirm the device can reach the update channel and endpoint policy is not blocking the signed update process. |
Change-control checklist
- Current installer downloaded from the approved Cadence channel.
- Installer signature verified by the endpoint-management team.
- Clean-device pilot passed for every OS and architecture in scope.
- Launch, relaunch, pairing, consented recording, stop, and revoke verified.
- Auto-update behavior verified before broad release.
- Rollback or uninstall procedure documented in the endpoint-management change.