--- title: Morse Watchmans KeyWatcher slug: km-keywatcher createdAt: 2026-08-26T01:47:27.000Z --- # Integration Guide ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/fD5I9jFrtOsYaEIRwMjVH_keywatcher-splash-card.png" size="60" width="780" height="310" position="flex-start" alt="Morse Watchmans" sha="4573be2aa30abab4eade9b132dca045801fc053a" initialPath="/assets/integration-guide/keywatcher/keywatcher-splash-card.png" githubPath="docs/assets/integration-guide/keywatcher/keywatcher-splash-card.png" showCaption="false"} :::hint{type="info"} This integration connects Sine with Morse Watchmans KeyWatcher key management systems, allowing key access to be coordinated with visitor management workflows. It enables system integrators and IT administrators to configure secure, streamlined key access for visitors and staff. This guide is intended for technical staff responsible for configuring and troubleshooting the integration. ::: # Overview Sine integrates with Morse Watchmans KeyWatcher via the KeyMaaS platform to automatically issue and track physical keys for visitors and contractors. When a visitor checks in, KeyWatcher is notified and prepares their assigned keys for retrieval, and on check-out, Sine prompts the visitor to return the keys and logs the transaction against their record. # How It Works Sine integrates with the Morse Watchmans KeyWatcher key cabinet system to link visitor check-in records with electronic key retrieval and return, allowing key access to be tracked automatically against each visitor's visit. ## Key Cabinet Check-in Visitors are issued a one-time credential to retrieve their assigned keys from an electronic key cabinet. **Check-in Flow:** - A visitor or contractor arrives on-site and checks in using either the SinePoint kiosk or the SinePro mobile app. - Sine sends the visitor's details and assigned key requirements to the KeyWatcher key cabinet system. - The key cabinet system generates a unique access credential, such as a one-time PIN, and delivers it to the visitor via SMS or email. - The visitor enters their credential at the key cabinet to unlock it and retrieve their assigned keys. - The key cabinet system logs the key transaction, and this record is associated with the visitor's Sine check-in. **Check-out Flow:** - The visitor initiates check-out through Sine. - Sine notifies the key cabinet system that the visitor is checking out. - The visitor is prompted to return their keys to the cabinet before the check-out process can be completed. - Once the key cabinet system confirms the keys have been returned, Sine finalizes the visitor's check-out. - If the keys are not returned, the key cabinet system triggers an overdue alert, which is sent to the configured contacts. # Requirements ## Sine Requirements - **Integration enablement**: A Sine subscription that supports the KeyWatcher integration, with the integration enabled on your account. Additional fees may apply. ## Morse Watchmans KeyWatcher Requirements - **KeyWatcher cabinet**: One or more KeyWatcher Touch or KeyWatcher Illuminated cabinets installed, powered, and connected to the network at the target site(s). - **KeyMaaS subscription**: An active KeyMaaS subscription, which provides the cloud integration layer connecting Sine to your KeyWatcher hardware. - **KeyMaaS API credentials**: API credentials from the KeyMaaS platform to authenticate the connection between Sine and your KeyWatcher account. - **Key slots configured**: Key slots pre-loaded with physical keys and configured in the key management platform, ready for assignment to visitor types. - **Testing environment**: A test cabinet or sandbox environment for validating the integration before deploying it to production. # Configuration ## Morse Watchmans KeyWatcher Configuration ### KeyWatcher Configuration ::::WorkflowBlock :::WorkflowBlockItem **KeyMaaS account setup** — Log in to your KeyMaaS portal and verify that your KeyWatcher cabinet(s) are registered and online. ::: :::WorkflowBlockItem **Key groups** — Create key groups in KeyMaaS to represent the sets of keys that should be assigned to different visitor types. Key groups are used to map Sine visitor types to specific keys. ::: :::WorkflowBlockItem **API credentials** — Generate API credentials in the KeyMaaS portal with permissions to create and manage user key assignments. Copy the API key, as you will need it when configuring the integration in Sine. ::: :::WorkflowBlockItem **Employee records** — Ensure that visitor records created by Sine via KeyMaaS are assigned to the correct site and division in your KeyWatcher system. ::: :::: ## Sine Configuration ### General Setup ::::WorkflowBlock :::WorkflowBlockItem **Admin permissions** — Ensure you have `Team` or `Site Admin` permissions. These are required to configure integrations. ::: :::WorkflowBlockItem **Log in** — Log in to the Sine admin dashboard at [https://dashboard.sine.co](https://dashboard.sine.co). ::: :::WorkflowBlockItem **Select site** — Navigate to the `Locations` tab and click on the site you want to configure the integration for. ::: :::WorkflowBlockItem **Add integration** — In the Site menu, click the `Integrations` menu item. Click the `Add integration` button and select `KeyWatcher` from the list of available integrations. If the integration does not appear in the list, contact support. ::: :::WorkflowBlockItem **Name integration** — Enter a name for the integration. This can be anything, but choose a name that helps you identify its purpose. ::: :::: ### Connection ### Connection Method - **Cloud to cloud**: Sine connects directly to the KeyMaaS platform via a cloud-to-cloud API connection, requiring no on-premise infrastructure. ### Authentication ::::WorkflowBlock :::WorkflowBlockItem **API Key** — Enter your KeyWatcher API Key to authenticate the connection between Sine and your key management platform. ::: :::WorkflowBlockItem **Test Connection** — Click the `Test connection` button to confirm that your configuration is correct. Once Sine successfully verifies the connection to your KeyWatcher account, the Integration Settings section becomes available. ::: :::: ### Integration Settings ### Key Assignment ::::WorkflowBlock :::WorkflowBlockItem **Visitor type mapping** — Map each Sine visitor type to a key set or key slot group in KeyWatcher. When a visitor of that type checks in, Sine automatically assigns them the corresponding keys. This setting controls which keys are assigned to visitors based on their visitor type in Sine. ::: :::WorkflowBlockItem **Key set selection** — Select the key sets or individual key slots in KeyWatcher that should be available for assignment to visitors. Only keys that are in their home slot and available will be assigned. ::: :::: ### Checkout Behaviour ::::WorkflowBlock :::WorkflowBlockItem **Block checkout until keys returned** — Toggle on to enforce key return before check-out can be completed. When enabled, visitors cannot complete their Sine check-out until the key cabinet confirms all assigned keys have been returned. When disabled, check-out proceeds immediately and an overdue alert is sent if the keys are not returned. ::: :::WorkflowBlockItem **Grace period** — Set the number of minutes to wait after check-out before an overdue key alert is sent. Leave this field blank to send alerts immediately. Use this setting to allow a short window after check-out is initiated before overdue alerts are triggered, giving visitors time to return keys without generating false alerts. ::: :::: ### Overdue Key Alerts ::::WorkflowBlock :::WorkflowBlockItem **Alert contacts** — Enter one or more email addresses or mobile numbers that should receive overdue key alerts. Alerts are sent when a visitor checks out or their pass expires without the keys being returned. ::: :::WorkflowBlockItem **Alert message** — Enter the message body for overdue key alert notifications. Customise the overdue alert message to include any site-specific instructions for recovering unreturned keys. ::: :::: ### Messages - **Visitor failure message** — Enter the message to display to the visitor at the kiosk if the key management integration fails for any reason. ### Notifications - **Send integration failure notifications** — Enter one or more email addresses to notify if the integration fails. Notified recipients receive the failure details. *** *Need help? Contact Sine Support at* **[support@sine.co](mailto\:support@sine.co)**