--- title: uberGARD iKLAS slug: km-iklas createdAt: 2026-10-27T05:49:23.000Z --- # Integration Guide ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/wcLG8qpYnJ7JtMy8chtg8_iklas-splash-card.png" size="60" width="780" height="310" position="flex-start" alt="uberGARD" sha="98b21b4dc60f9c55bcf9308187a0751d651b0a02" initialPath="/assets/integration-guide/iklas/iklas-splash-card.png" githubPath="docs/assets/integration-guide/iklas/iklas-splash-card.png" showCaption="false"} :::hint{type="info"} This integration connects Sine with uberGARD's iKLAS access control system, allowing visitor and access data to flow between the two platforms. Configuring this integration enables system integrators to streamline access management for visitors and staff while maintaining accurate records across both systems. This guide is intended for system integrators and IT administrators responsible for configuring and maintaining the connection between Sine and iKLAS. ::: # Overview This integration connects Sine with uberGARD iKLAS, allowing visitors and contractors to select the keys they need during check-in and collect them themselves from the key cabinet. Keys sync from iKLAS into Sine daily, and once a host approves a visit, Sine creates a cabinet user, activates their key access, and sends the visitor a user ID and PIN. On check-out, Sine reminds the visitor to return their keys, verifies the return against the cabinet, and removes their access, and key cabinet problems never block a check-in. # How It Works Sine integrates with the uberGARD iKLAS key management system to synchronize key availability and manage key cabinet access as part of the visitor check-in and check-out process. ## Key Cabinet Check-in Visitors select the keys they need as part of check-in and are issued a user ID and PIN to release those keys from the iKLAS cabinet once their pass is approved. **Check-in Flow:** ::::WorkflowBlock :::WorkflowBlockItem Ahead of any visit, Sine syncs the keys from the configured iKLAS key groups into a read-only asset type, ensuring the check-in form reflects the keys currently available for visitors to select. ::: :::WorkflowBlockItem A visitor or contractor arrives and checks in via SinePoint kiosk, the SinePro mobile app, or an invitation link. ::: :::WorkflowBlockItem The check-in form presents the synced keys, and the visitor selects the keys they need for their visit. ::: :::WorkflowBlockItem When the pass is created, Sine creates a user for the visitor in iKLAS and generates a unique PIN for them. The keys are reserved against the visitor, but access is not yet open. ::: :::WorkflowBlockItem The visitor's host approves the pass. ::: :::WorkflowBlockItem On approval, Sine enables the visitor's key access in iKLAS and emails them their user ID and PIN. ::: :::WorkflowBlockItem The visitor enters their user ID and PIN at the cabinet, and iKLAS releases the keys they selected. ::: :::WorkflowBlockItem If the cabinet is unreachable at any point, the visitor still checks in. The failure is recorded against their pass and sent to the integration's notification contacts. ::: :::: **Check-out Flow:** ::::WorkflowBlock :::WorkflowBlockItem The visitor checks out via Sine and is reminded to return their keys to the cabinet. ::: :::WorkflowBlockItem The visitor keeps their cabinet access for a short grace period so they can return the keys. ::: :::WorkflowBlockItem The visitor returns the keys to the iKLAS cabinet, which records the return against their user. ::: :::WorkflowBlockItem After the grace period, Sine reads the cabinet's transaction history to confirm which keys came back, and reports any that did not. ::: :::WorkflowBlockItem Sine then revokes the visitor's key access and removes their user record from iKLAS. ::: :::: # Requirements ## Sine Requirements - **Integration enablement**: A Sine subscription that supports the iKLAS integration, with the integration enabled on your account. Additional fees may apply. - **Dynamic asset type**: A dynamic asset type created on the Asset types page to hold the synced keys. This asset type must not already be linked to another integration. Its assets are managed entirely by the integration and are read-only in Sine. - **Key selection question**: A key selection question added to the visitor type form of every visitor type that should offer keys, bound to the dynamic asset type created above. A visitor only triggers the integration if they select keys on this question. - **Host approval**: Host approval enabled on those visitor types. Key access activates only when the pass is approved. Without host approval enabled, keys release as soon as the visitor checks in. - **Visitor contact details**: An email address captured at check-in so the visitor can receive their user ID and PIN. ## uberGARD iKLAS Requirements - **iKLAS cabinet**: One or more iKLAS key cabinets installed, powered, and connected to the network at the target site, with keys loaded into their positions. - **API user account**: An iKLAS user account for Sine to authenticate with. This account must be permitted to create and delete users, assign and revoke key access profiles, and read key groups, keys, and transactions. - **Key groups**: The keys that should be available to visitors grouped into one or more iKLAS key groups. Sine syncs keys by key group, so a key that does not belong to a selected group is never offered at check-in. - **Audit user**: An iKLAS user to which key access changes made by Sine will be attributed in the cabinet's audit records. - **Testing environment**: A test cabinet or sandbox environment available for validating the integration before going live. - **Network connectivity**: Determine your method for connecting Sine with your on-premise iKLAS system. - **Direct API access**: Requires network firewall access to the iKLAS API from outside your network. - **Sine Secure Bridge**: Requires installation of the Sine Secure Bridge agent to establish a secure, managed tunnel between your on-premise iKLAS system and Sine. # Configuration ## uberGARD iKLAS Configuration ### iKLAS Configuration Complete these steps in iKLAS before configuring the integration in Sine. The Sine configuration requires values that you create during this setup. ::::WorkflowBlock :::WorkflowBlockItem **Create the API user** — Create a dedicated iKLAS user for Sine and grant it permission to manage users and key access profiles and to read key groups, keys, and transactions. Record its username and password for use in the Sine configuration. ::: :::WorkflowBlockItem **Name the keys** — Confirm that every key you intend to offer is installed in a cabinet position and clearly named in iKLAS. Key names are what visitors see when selecting keys at check-in, so name each key in terms a visitor would recognize, such as the door, room, or vehicle it corresponds to. ::: :::WorkflowBlockItem **Create key groups** — Group the keys that should be available to visitors into one or more key groups. Only keys belonging to the key groups selected in Sine are synced and offered at check-in, so key groups determine which keys visitors can request. ::: :::WorkflowBlockItem **Identify the audit user** — Identify the iKLAS user to which key access changes made by Sine should be attributed, and record its user ID for use in the Sine configuration. ::: :::WorkflowBlockItem **Confirm network access** — Confirm that the cabinet's API is reachable from Sine, either by allowing inbound access through your firewall or by preparing a Sine Secure Bridge tunnel that reaches it. ::: :::: ## Sine Configuration ### General Setup ::::WorkflowBlock :::WorkflowBlockItem **Admin permissions** — Ensure you have `Team` or `Site Admin` permissions. These permissions are required to configure integrations. ::: :::WorkflowBlockItem **Log in** — Log on to the [Sine admin dashboard](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 `Integrations`. Click `Add integration` and select `iKLAS` 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. You can use any name, but choose one that helps you identify its purpose. ::: :::: ### Connection ### Connection Method There are two ways to establish network connectivity to your on-premise iKLAS system. Select your preferred method below. ::::::Tabs :::::Tab{title="Sine Secure Bridge"} Sine Secure Bridge enables a secure, managed tunnel between Sine Cloud and your on-premise system's API. ::::WorkflowBlock :::WorkflowBlockItem **Enable Secure Bridge** — Switch `Use Sine Secure Bridge` on to display a dropdown list of your Secure Bridge tunnels, then select the tunnel that reaches your iKLAS server. Sine takes the server address from the tunnel, so the `Base URL` field is hidden while the toggle is on. If the Sine Secure Bridge toggle is not visible, contact your Sine representative. ::: :::WorkflowBlockItem **Documentation** — For more information on installing and configuring a Sine Secure Bridge tunnel, visit the Secure Bridge Documentation. ::: :::: ::::: :::Tab{title="Direct network connection"} Direct connection from Sine Cloud to your on-premise system's API. - **Base URL** — Enter the URL and port of your iKLAS server, for example `https://your-iklas-server.com:443`. ::: :::::: ### Authentication ::::WorkflowBlock :::WorkflowBlockItem **Credentials** — Enter the iKLAS username and password that Sine should authenticate with. These credentials belong to the API user created in iKLAS, not an administrator's personal login. ::: :::WorkflowBlockItem **Test Connection** — Click `Test connection` to confirm that your configuration is correct. Once Sine successfully verifies the connection to your iKLAS account, the Integration Settings section becomes available. ::: :::: ### Integration Settings These settings become available once the connection has been tested successfully. ### Settings ::::WorkflowBlock :::WorkflowBlockItem **Key groups** — Select the iKLAS key access groups that should be available to visitors when this integration activates access. Keys that do not belong to any of the selected groups are never synced into Sine. Controls which keys are synced from the cabinet and offered to visitors at check-in. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/Q5s1NN78Ee84caQB2xs7e_key-groups.png" size="75" position="flex-start" alt="key-groups" sha="d83b210aa194b9314f7710dc0559039911069ecd" initialPath="/assets/integration-guide/iklas/key-groups.png" githubPath="docs/assets/integration-guide/iklas/key-groups.png" showCaption="false"} ::: :::WorkflowBlockItem **Asset type** — Select the dynamic asset type that the synced keys should be written to. This must be the same asset type that the key selection question on your visitor type form is bound to. The dynamic asset type the integration manages and syncs keys into. Only dynamic asset types that are not already linked to another integration can be selected. You can manage asset types from the Asset types page. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/s28PRPeaeGWGsyr_vG82J_asset-type.png" size="75" position="flex-start" alt="asset-type" sha="ccc87744bcb055f3e4ae9a03d3173b083d84765d" initialPath="/assets/integration-guide/iklas/asset-type.png" githubPath="docs/assets/integration-guide/iklas/asset-type.png" showCaption="false"} ::: :::WorkflowBlockItem **Audit user ID** — Enter the ID of the iKLAS user that key access changes made by Sine will be attributed to. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/aBxnXwNSO0U04Yha3HhsO_audit-user-id.png" size="75" position="flex-start" alt="audit-user-id" sha="da134e20b3e75ac13f52daaff311a82ced8c98cd" initialPath="/assets/integration-guide/iklas/audit-user-id.png" githubPath="docs/assets/integration-guide/iklas/audit-user-id.png" showCaption="false"} ::: :::WorkflowBlockItem **Max keys per user** — Set a limit between `1` and `12` for how many keys can be assigned to each visitor. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/7gzq7bhQEuDGGJKpUQwBw_max-key-per-user.png" size="75" position="flex-start" alt="max-key-per-user" sha="7e96d4173c81eda21c2baf5956c0f5dffb14e82e" initialPath="/assets/integration-guide/iklas/max-key-per-user.png" githubPath="docs/assets/integration-guide/iklas/max-key-per-user.png" showCaption="false"} ::: :::: ### Visitor Requirements :::hint{type="warning"} **Visitors may not receive key credentials** — Key credentials are sent to the email address captured on the visitor's pass, so a pass created without an email address will never receive them. This panel appears when a visitor type at the site can check in without an email address, and it names the affected visitor types. Use `Review settings` to make email a required field for those visitor types, or leave the panel as-is if those visitor types are not meant to be offered keys. ::: ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/I7Hd3jgam5ZW34utJ1Ws3_visitor-requirements.png" size="75" position="flex-start" alt="visitor-requirements" sha="7a76ac947b3c301069f8109d6cb3ded2663d20ec" initialPath="/assets/integration-guide/iklas/visitor-requirements.png" githubPath="docs/assets/integration-guide/iklas/visitor-requirements.png" showCaption="false"} ### Manual Update - **Sync key data** — Click `Run sync` to reconcile the linked asset type against iKLAS immediately, rather than waiting for the next scheduled sync. New, removed, and updated keys are all reflected in the asset type. Run this after adding or renaming keys in the cabinet so they become selectable at check-in right away. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/VVmz3Afm0EK0KFhl2RXOC_manual-update.png" size="75" position="flex-start" alt="manual-update" sha="376fd77db92af58af89cad0eebdb3d020bca0b6f" initialPath="/assets/integration-guide/iklas/manual-update.png" githubPath="docs/assets/integration-guide/iklas/manual-update.png" showCaption="false"} ### Notifications - **Send integration failure notifications** — If the integration fails, enter one or more email addresses to be notified of the failure and its corresponding details. ### Save - **Save the integration** — Click `Save`. Sine verifies the connection, links the selected asset type to this integration, and runs a first sync of the keys in the selected key groups. Keys are then re-synced once a day for as long as the integration stays active. ### Key Selection at Check-in The integration only runs for a visitor when they select keys on their check-in form, so the final step is to put the key selection question in front of the right visitors. Complete this section after saving the integration, so the synced keys are available to confirm. ::::WorkflowBlock :::WorkflowBlockItem **Confirm the synced keys** — Open the Asset types page and confirm that the keys from your selected key groups now appear under the linked asset type. These assets are read-only, as they are maintained by the integration, and keys that leave your selected key groups are dropped from the list on the next sync. ::: :::WorkflowBlockItem **Add the key selection question** — On each visitor type that should be offered keys, add the key selection question to the form and bind it to the asset type linked above. The question's options are loaded from the asset type each time the form is opened, so the key list is always current. ::: :::WorkflowBlockItem **Confirm host approval** — Confirm that `Host Selection Required` is ticked for those visitor types. Key access is activated when a pass is approved, so without host approval a visitor's keys are released as soon as they check in. ::: :::: # Testing ::::WorkflowBlock :::WorkflowBlockItem **Create a test check-in** — Check in a test visitor using a visitor type whose form includes the key selection question, and select one or more keys. ::: :::WorkflowBlockItem **Verify the visitor record** — Confirm that a user record for the test visitor is created in iKLAS with the selected keys assigned to them. ::: :::WorkflowBlockItem **Verify credential delivery** — Approve the test visitor's pass and confirm that they receive their cabinet access credentials. ::: :::WorkflowBlockItem **Retrieve a key** — Use the delivered credentials at the iKLAS cabinet and confirm the selected keys are released. ::: :::WorkflowBlockItem **Verify key return and revocation** — Check the test visitor out, return the keys to the cabinet, and confirm that their access is revoked and their iKLAS user record is removed. ::: :::WorkflowBlockItem **Check failure notifications** — Monitor the integration failure notifications to ensure they are working correctly. ::: :::: *** *Need help? Contact Sine Support at* **[support@sine.co](mailto\:support@sine.co)**