Software Extensions
Targeted extensions to CAW Enterprise.
CAW expansions
How modules work
Modules are extensions that you activate within CAW. Therefore, you do not receive an extra platform, extra management, or a migration project.
What you can expect
- One management environment and user management
- The same authorization and tag structure (modules add capabilities within the same model)
- The same audit trail and reporting chain
- Expand by capability (only activate what you use)
- Add modules later without restructuring the core
When do you choose a module?
(CAW-M02, CAW-M06)
(CAW-M09, CAW-M12)
CAW Modules
Maps and Location Graphics
For organizations with many locations and assets, “knowing what is where” is operationally important, and this module adds map and floor plan views. Locks and communicators can be positioned on maps and on custom visuals (floor plans and photos) so that management and tracking do not depend on local knowledge or separate documentation.
The module supports working with geographic coordinates. This enables export to GIS environments, allowing CyberLock layers to connect to existing geographic information systems.
Typical of: campuses, municipalities, public transport, water boards, industrial estates, utility companies
By Support
Brings door functionality under the same management regime as your other access components. You manage rights per door, record events (such as Request-to-Exit), and monitor door status via sensors. You can also have doors automatically unlock and lock at scheduled times and trigger alarms for forced doors or doors that remain open for too long.
Relevant as soon as doors become part of your security and compliance approach and you do not want to manage this as a separate subsystem.
Typical of: sensor doors, controlled passages, perimeter, logistics
Advanced Security Features (legacy, version-dependent)
Bundles security features such as stricter multi-key timing, temporary activation of an expired key, and support for TOTP two-factor authentication for administrator accounts. In current CAW versions, parts of this are standard. Therefore, position this as version- and use-case-dependent.
Relevant in environments where risks related to key sharing, time windows, and administrative login must be explicitly mitigated.
Typical of: stricter admin login security, high-security zones, exception procedures
Lock List Expansion
Designed for scale when the number of locks and authorizations exceeds what practically fits on a single key by default. The module supports the expansion of lock lists and filtering by communicator. As a result, you can manage many rights in practice without keys or synchronization running into capacity bottlenecks.
Ideal for large environments with a lot of variation in roles and changing teams, where “effective access” is greater than what you want to fit into a single static load.
Typical of: large environments with many doors (and therefore cylinders), many roller variants, many changing teams
Active Directory / Azure AD
Connects CAW to your identity source. Security groups and users can be synchronized and linked to individuals and tags in CAW. The result is less duplicate management and a better joiner-mover-leaver process. Leaving the company means losing access. Role changes in AD can propagate to CAW structures depending on the configuration.
Strong for organizations where identity governance is leading and audit pressure is high.
Typical of: SSO, IAM processes, service desk workflows, audit pressure
Advanced Door Features
Expands door management with operational features:
-
No PIN required schedule: no PIN is required within a time window (friction down during office hours and check up outside hours)
-
Keep unlocked calendar entries: schedule future time slots during which a door remains unlocked based on calendar items
-
Door monitor window: live view of door activity in a scrolling window
Relevant whenever doors are part of facility processes and management needs to be predictable and plannable.
Typical of: high-security passages, office hours vs. off-peak hours, event locations
Rolling Access Codes
Automates periodic code rotation. You configure when codes roll and can work with a grace period so that the transition remains manageable. This is interesting if code rotation is an explicit part of your security baseline without it becoming a manual project.
Reduces manual work and increases consistency of execution.
Typical of: higher baseline requirements, periodic security rotation, less static access
FlashLock Compatibility
Adds support for FlashLocks and associated credentials such as fobs. Flash access can be issued via email or SMS, enabling temporary or distributed access without physical transfer. FlashLock grants access via a unique light flicker generated by the phone.
Relevant for contractors, visitors, and situations where ease and speed of dispensing are important.
Typical of: temporary access, contractors, external teams, fast issuance
Dynamic Tags
From static to rule-based or conditional access. Dynamic Tags link access to requirements in self-defined fields in persons, locks, and tags. As a result, access can be automatically granted or revoked upon changes to attributes (e.g., certificate expired, contract status changed).
This makes management scalable and reduces errors because access follows the policy and not the manual work.
Typical of: safety gating, certificate-based access, contractors, role changes
Fobs
Can be used for cylinders with NFC/Bluetooth support. Additionally, supports IR fobs as an extra credential type.
Fobs can also be linked to individuals with expiration rules and deployed for access to CyberLock Blue/NFC and doors via a FlashReader, depending on the configuration.
Handy if you want to use easier-to-issue carriers in addition to keys within a single policy.
Typical of: keyless entry, visitors, flex workers, alternative credentials besides keys
Camera and NVR Integration
Linkes camera footage to audit trail events. With Frigate NVR and compatible cameras, you can capture video clips and link them to specific events, including notifications with a link to the clip. This is particularly valuable for retrospective verification, incident analysis, and internal controls.
You get context for events: what happened around the moment of entry, forced door, or anomaly.
With AI support on the server, the images can be analyzed directly using machine learning.
Typical of: critical rooms, asset rooms, higher resistance class
OSDP Support
Enables integration with third-party RFID card readers via OSDP for Flex II/FlexEdge/ValidiKey. Relevant if you want to reuse or standardize existing card readers while CAW retains control and logging. Fits well in hybrid environments where card and key coexist.
Typical of: hybrid environments, reuse of existing readers, standardization