Door & Zone Inventory
List entrances, shared areas, private suites and reservable rooms by operating purpose.
Define door groups, member permissions, visitor handling and booking windows before choosing hardware. The project brief gives operations, IT and procurement one basis for technical and commercial review.
Entry point, visitor calling and the handover between public access and reception.
Shared desks, private suites and staff routes tied to defined access groups.
Meeting spaces that require scheduled permissions and event records.
List entrances, shared areas, private suites and reservable rooms by operating purpose.
Define who admits visitors, administers permissions and reviews exceptions.
Identify drawings, opening conditions, interfaces and approval material required for review.
Map membership events to door groups so approved users receive the right credential without routine desk-side setup. Roles, active periods and access groups are defined during implementation.
Apply an end date or status change to the relevant credential set when membership changes. This reduces stale permissions and avoids manual card-recovery workflows.
Support authorised entry outside reception hours with the configured mobile, card or PIN method. Select fallback procedures by site, user group and door type.
Use booking events to apply access windows to selected rooms. Confirm early-entry, cancellation and audit rules before the connection is released.
Review events by door, time and user group to support capacity, service and exception management. Confirm available report fields during project scoping.
Issue time- and door-limited QR codes or PINs for day passes and events. Configure validity, permitted zones and record-retention requirements for each use case.
The membership platform sends an approved event to the access layer. The connection maps membership status, role, site and active period to the appropriate door groups, then issues the selected credential. The exact workflow depends on the source platform API, access policy and operating rules agreed during project scoping.
The access plan can include RFID cards, PIN codes or a reception-managed fallback, subject to the selected hardware and operating policy. Confirm credential fallback, offline behaviour and exception handling for each door type before installation.
Connection is assessed against the source platform's API, webhook events and data model. The project scope defines the required member, booking and status mappings. Documented external-interface work should be confirmed against the specific deployment requirements before commercial approval.
Temporary QR codes or PINs can be configured by validity period, permitted doors and user type. The project rules should cover issue authority, event capacity, credential expiry and the retention of access records.
Door events can support review by time, door and user group, subject to the selected platform and data policy. Define reporting fields, retention periods and any building-system interface during the technical review.
White-label app branding is assessed separately from the standard access deployment. It covers brand replacement for the app rather than bespoke app development, and the current program minimum order quantity is 1,000 units. Confirm eligibility, product scope and commercial terms with the project team.
The current co-working deployment MOQ is 200 locks. Pricing depends on door count, sites, credential policy, platform interface and the level of project support required. Submit the operating map and platform details for a project-specific quotation.