Short answers about Lockbox setup, roles, sessions, power, features, and emergency access.
For procedures, use the Quick Start or Support Center.
Setup and pairing
Use automatic Bluetooth pairing in Chrome or Edge. It pairs the Lockbox and provisions 2.4 GHz Wi-Fi in one flow. Manual Wi-Fi setup is the fallback.
The previous owner should unpair it first. If that is impossible, contact support@researchanddesire.com with proof of purchase and the identifier shown under Settings → Pairing. Do not publish the pairing code.
The code can change after a restart. Use the code currently shown on the device. Once paired, normal account ownership does not depend on retaining that code.
Roles and sessions
The Lockee is subject to the lock. A Keyholder is another account the Lockee authorizes to manage agreed session controls. Review consent, permissions, release, offline behavior, and revocation in the Keyholder Guide.
A self-lock is started without a Keyholder. Active self-lock controls can be more limited than a Keyholder-managed or test session, so complete a short test and verify Emergency Unlock before relying on it.
Do not change the partnership while a session is active. End the session safely, confirm the physical Lockbox is unlocked, then change the relationship under Settings → Partners. If account access or ownership is disputed, contact support.
A test lock is a practice session intended to verify setup and release behavior before a real lock. Use Start Your First Lock.
Power and connectivity
The existing product notes estimate about 24 hours unplugged under normal use, but actual runtime depends on screen, radio, motor, battery condition, and firmware behavior. Keep long sessions on stable power and verify the battery state before locking.
Use stable USB power for longer sessions when practical. The current documentation says a plugged-in Lockbox does not enter deep sleep, which helps preserve remote connectivity.
The physical indicator is live; the dashboard can take up to 60 seconds to update. Compare them with Check Online Status.
Local timers, menus, and physical controls continue according to the state stored on the device. Remote Keyholder commands, dashboard changes, and public votes require connectivity. See the Offline Capability Matrix.
Features
The session must enable breaks. The Lockee starts a break from the device, retrieves the key, and returns it before ending the break. Health and emergency access always take priority over an overdue record. See Take a Break.
It hides countdown information from the Lockee-facing device and dashboard views described in the feature guide. It must not hide safety or emergency instructions. See Hide Remaining Time.
It creates a shareable page where visitors can add or remove configured time. Agree on the audience and duration boundaries before sharing, and test how to disable it. See Public Voting.
Permalock removes the preset end time and uses Keyholder-controlled release. It is an advanced online mode that requires completed test locks and reviewed emergency access. See Permalock.
Emergency access
Use local Software Emergency Unlock when available. If it is disabled or the device cannot unlock, use Hardware Backplate Emergency Access. Do not wait for support when access is urgent.
The current design uses a replaceable backplate as a destructive physical fallback. Software cannot disable that physical path. Review it before every long or remotely managed session.
The active session ends, the event may be shared with connected partners, and the current documentation describes a 24-hour cooldown before another lock. See E-Lock 20. Safety comes before the cooldown or notification.