Codelocks introduces ConnectShare smart locks for app, RFID and code access

A standalone-lock option with multiple credentials

Codelocks has introduced ConnectShare, a connected smart-lock range intended to bring mobile credential sharing to standalone keypad locks. The range supports access through a user code, an RFID card or a smartphone credential, with setup and administration handled in the Codelocks Connect App.

The announcement is relevant to projects that need more flexibility than a fixed keypad code but do not necessarily call for a conventional hardwired online-lock deployment. Candidate uses include shared work areas, staff-only rooms, rental or temporary-use spaces, and smaller retrofit projects where running power and data cabling to each opening would be disruptive.

What the app changes

The Codelocks Connect App is used to manage compatible locks and users. For ConnectShare, the company says administrators can invite smartphone users and issue time-sensitive NetCodes, which are codes configured with a defined start date, time and duration. This can reduce the need to distribute and recover physical keys for short-term access.

Codelocks also lists GuestCode, Code Free and Do Not Disturb functions. These features should be considered against the operating policy of the opening: unrestricted or guest-controlled modes may suit certain occupied spaces, but may be inappropriate for controlled storage, restricted technical rooms or other doors requiring a tightly defined access procedure.

Activity records and higher-control features

A notable addition is an activity log that records access events for the lock. Codelocks positions this as a first for its Connect by Codelocks range. For facilities that need event history, integrators should confirm how frequently the lock is synchronized, how records are exported and retained, and whether the available record detail meets the organization’s audit requirements.

The range also includes Multi-Admin, allowing responsibility for an individual lock to be shared, and Dual Authorization, which requires two valid credentials for an unlock. Dual Authorization may be useful where an organization has a two-person-entry procedure, but it should be tested with the selected credential types and written operating process before deployment.

Initial models and door considerations

ConnectShare is initially offered as the CL4500CC and CL5500CC. Codelocks describes the CL4500CC as a medium-duty model available in latch and mortice configurations. The CL5500CC is positioned as a heavy-duty model with latch, lock and panic-access options. Both are offered in brushed steel, while solid black is also available for the CL5500CC.

The manufacturer’s August product notice lists a radius mortice-latch option with 60 mm and 70 mm backsets and identifies 35–60 mm wooden doors as the intended door-thickness range. These details do not replace a door survey. Specifiers should verify handing, door preparation, latch or lockcase compatibility, egress hardware, fire-door assembly requirements and applicable local code before selecting a model.

Fire-test claims require assembly-level review

Codelocks states that ConnectShare has completed independent testing to BS EN 1634-1 for 30- and 60-minute timber door sets when installed with a Codelocks FireKit, along with performance testing to BS EN 12209. Those are specific test and installation conditions, not a blanket rating for every door or hardware combination.

For US projects, the authority having jurisdiction and the door manufacturer’s listing requirements remain decisive. Procurement teams should obtain the relevant product documentation and confirm the complete approved door, frame, latch or lock, closer and fire-hardware configuration rather than relying solely on a lock-family claim.

How ConnectShare fits in an access-control design

ConnectShare is best evaluated as a standalone, app-managed locking approach rather than assumed to be a substitute for every networked access-control system. Codelocks says the mobile credential-sharing process is device-to-device and does not require an internet connection at the lock. That can simplify retrofit work, but it also means project teams should understand how credentials, lock events and administrative updates are transferred in the intended operating workflow.

Before standardizing on the platform, installers and end users should validate credential enrollment, administrator handoff, lost-phone procedures, audit retrieval, battery maintenance, emergency access and support responsibilities. The combination of code, card and phone access gives operators choices, but the security outcome will depend on configuration and site procedures as much as on the lock itself.