FAQ: Dormakaba Locks – Lynx

FAQ: Dormakaba Locks

Introduction

Lynx integrates with multiple Dormakaba lock models, including Oracode locks, WiFi- and Bluetooth-enabled Saffire EVO locks, and Mortise (M) models that support auto-lock. Through this integration, you can generate and manage guest access codes, monitor lock status, and configure site settings directly from the Lynx portal — while certain hardware-level tasks, like permanent staff code creation and Bluetooth enablement, are handled directly through Dormakaba.

Frequently Asked Questions Table of Contents:

When to use this guide
Benefits of using this Guide
Frequently Asked Questions
Key Features

When to use this guide:

Use this guide when you need to:

Understand which Dormakaba lock models Lynx supports and how they differ.
Set up a new Dormakaba Saffire EVO WiFi integration.
Troubleshoot a guest code that isn't working on the lock.
Confirm whether an issue should be handled by Lynx Support or Dormakaba Support.
Learn how auto-lock works and which models support it.

Benefits of using this Guide

Enhanced security through auto-lock functionality on supported Mortise (M) models.
Operational efficiency through automated guest code generation.
Guest convenience with keyless access.
Scalable integration across multiple properties.
Reduced liability through consistent security protocols.

M-Unit changes: Any change made with the M-Unit must be applied to every lock on the property.

Code format: Lynx generates access codes using digits only — no spaces or special characters.

Multiple locks per reservation: A code should sync to each lock tied to a reservation. Contact Lynx Support if only one code appears.

Dormakaba support contacts: lodgingcustomerservice@dormakaba.com or oracode.customerservice@dormakaba.com.

Frequently Asked Questions

Questions	Answers
What types of Dormakaba locks does Lynx support?	Lynx supports multiple Dormakaba lock models, including Oracode locks (traditional models), Saffire EVO (WiFi and Bluetooth-enabled models), and Mortise (M) models for auto-lock capability.
What are the main benefits of using Dormakaba locks with Lynx?	Enhanced security with auto-lock functionality (with the mortise lock model only), operational efficiency through automated code generation, guest convenience with keyless access, scalable integration across multiple properties, and reduced liability with consistent security protocols.
What's the difference between Oracode and Saffire EVO locks?	Oracode locks are traditional Dormakaba models that require M-Unit management. Saffire EVO locks are newer WiFi and Bluetooth-enabled models that integrate more directly with Lynx and support auto-lock on Mortise (M) models.
How long can access codes be?	Access codes can range from 6 to 12 digits.
How do codes sync between Lynx and the lock?	Dormakaba locks use an algorithm to sync codes. As long as the lock has been added to Lynx, the codes you see in Lynx will match the codes that work on the lock.
How do I create permanent staff codes?	Permanent codes must be created directly with Dormakaba. Contact their customer service and provide your M-Unit. You cannot create permanent user codes through Lynx.
A user's code shows as active in Lynx but doesn't work on the lock. What's wrong?	The most common cause is that the user hasn't been added to the access group associated with that lock. To resolve: (1) verify the exact lock name in your system, (2) confirm the user has been added to the group linked to that specific lock, (3) check that the user appears under Permanent Users once added, (4) the code should start working after these changes. If you need further assistance, contact Lynx support with the lock name and user details.
How can I verify my Dormakaba lock is online?	Check your Lynx dashboard to see the device status. If the lock shows offline, this is a Dormakaba hardware connectivity issue and should be escalated to Dormakaba support.
Codes aren't syncing to the lock. What should I do?	First verify the lock is online. If it's online but codes aren't syncing, this is a Lynx support issue. If the lock is offline, contact Dormakaba support to get the lock back online before further troubleshooting.
Do Dormakaba locks require special maintenance?	No. Once the lock is connected to Lynx, it doesn't need to be reconnected or require ongoing maintenance.
Are there activity logs for Dormakaba locks?	No, there are no activity logs or access notifications available for Dormakaba locks.
How do I set up access for a common door (like a front entrance)?	First, ensure the common door has been set up with Dormakaba. Lynx won't display common doors in the system, but guest codes will still work. The code must be modified when entered on the lock — for example, if the guest code is "123456", the code to enter on a common door lock is "#1#123456".
What is auto-lock and which Dormakaba models support it?	Auto-lock automatically locks the door the moment it closes. This feature is only supported on Dormakaba Mortise (M) models with motorized deadbolts — standard cylindrical or deadbolt models cannot use it. Auto-lock requires activation during initial installation and may require a technician.
What are the benefits of auto-lock?	Maximum security (the door is never accidentally left unlocked), a stress-free experience for guests (no need to remember to lock up), a stronger lock with a motorized deadbolt, and operational savings since staff don't need to check or manually lock doors.
Does auto-lock use more battery?	Yes. The motorized component uses more battery power, so consistent battery monitoring is essential.
Can I disable auto-lock temporarily?	No, auto-lock generally cannot be turned off on demand by the user once it's configured.
How do I enable Bluetooth on Dormakaba locks?	To enable BLE (Bluetooth Low Energy): (1) contact Dormakaba customer service directly, (2) sign the cloud agreement and complete payment, (3) Dormakaba's customer service will redirect your request to their Project Coordinator team, (4) the Bluetooth team will then configure your site with the generated credentials.
What information do I need to set up a Dormakaba Saffire EVO WiFi integration?	When adding a Dormakaba integration to Lynx, you'll need to provide the Site Name, Country, State, and Zip Code. Once complete, Lynx will submit your information to Dormakaba for the next steps.
What user levels do I need to configure for Dormakaba integration?	You must select four different user levels during integration setup. If you don't select all four user levels, codes on the locks will not be created properly.
Can I set up multiple properties with Dormakaba locks?	Yes. Dormakaba locks support multiple properties and lock types through Lynx's centralized platform. Ensure each property is properly configured with the required site information.
What happens if I change or remove staff codes?	Any changes to staff codes (creation, removal, or editing) must be done through Dormakaba's system, not Lynx. Contact your Dormakaba representative and provide them with the updated user list and M-Unit information.
Can I create shared keys on Dormakaba locks?	Yes, you can create a shared key on Dormakaba locks through Lynx.
What time zone settings apply to Dormakaba Saffire EVO locks?	Time zone configuration is important for proper lock functionality. Refer to the time zone configuration documentation specific to your Dormakaba Saffire EVO model setup.
What's the difference between guest codes and staff codes?	Guest codes are temporary access codes generated for reservations and managed through Lynx. Staff codes are permanent codes for employees and must be created through Dormakaba. Guest codes work on all locks (including common doors with modification), while staff codes are configured per lock.
When should I contact Lynx Support vs. Dormakaba Support?	Contact Lynx Support for lock onboarding to Lynx, adding a Dormakaba integration, code syncing issues, troubleshooting codes that aren't working on online locks, lock configuration questions, and guest code generation/management. Contact Dormakaba Support for physical lock installation, lock offline troubleshooting, hardware connectivity issues, permanent staff code creation, device warranty claims, BLE (Bluetooth) enablement, cloud agreement setup, and lock specifications.
Can external systems wipe the API connection to Kaba?	No. Lynx uses an API integration with Kaba to create codes. No one can wipe the Lynx connection with any of the locks on Kaba.
Can Lynx delete old or revoked codes from the Kaba portal?	No. No one can delete a code from the Kaba portal. It is not possible at all. Triggering a force sync on Lynx will not remove codes from the Kaba portal.

Key Features

Support for multiple Dormakaba lock families — Oracode, Saffire EVO, and Mortise (M) models — through one centralized platform.
Auto-lock capability on supported Mortise (M) models for added security and guest convenience.
Centralized guest code generation and syncing across multiple properties.
Shared key creation directly through Lynx.
Four required user levels during integration setup to ensure codes generate correctly on the lock.

Learn more about Overview: Dormakaba Locks here.