> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/reservations-and-operations/smart-locks.md). # Smart locks Smart locks lists your connected smart locks with their status, settings, activity and access codes. {% hint style="info" %} **Requirements** * A connected smart lock integration. {% endhint %} ## Smart locks list | Column | What it shows | | ----------------- | ----------------------------------------------------- | | Identity code | The unique identity code of the lock. | | Listing | The listing the lock is installed in. | | Location | Where the lock is in the property. | | Connection status | Online or offline. | | Battery | The charge level, and whether the device is charging. | **Refresh** updates the list. The **Grid** / **Table** toggle switches the layout. Search finds locks by name. ## Lock details | Field | What it does | Limits | | ----------------- | ---------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Name and brand | The name of the lock, its brand, and whether it is online. | The name and description can be edited. | | Door name | The user-facing name of the location or function of the lock, for example *Front Door*. | None | | Device components | Whether the **Keypad** and the **Door sensor** are connected. | A lock without keypad shows *There is no keypad on this lock.* | | **Open Door** | Unlocks the door remotely from Guestway. | You confirm *Are you sure you want to open this door?*. | | Location | The entry point the lock controls, for example *Apartment door* or *Building entrance*. | None | | Room door | Whether the lock is on a room door. Guestway detects it from the integration data. | Edit sets a manual override. | | PIN code suffix | The key guests press after the code: **Auto-detect**, **Hash (#)** or **Enter key (↵)**. | None | | Device health | The uptime as a percentage and a 30-day timeline, and the battery level over time. | The battery chart shows **Last 24h**, **Last 7 days**, **Last 30 days**, **Last 3 months**, **Last year** or **This year**. | | Linkage | The listings and complex the lock is linked to. | None | | Subscription | An unsubscribed lock pauses the sync of Guestway without being deleted. | None | ## Guest access settings | Setting | What it does | Limits | | ----------------------------------- | ------------------------------------------------------------------------------------------------- | --------------------------------------- | | **Guest Can Open Remotely** | Guests unlock the door from their phone in the [guest portal](/guest-experience/guest-portal.md). | Only within 100 meters of the property. | | **Prevent Access Until Checked-in** | Guests cannot use their code until they are checked in. | None | | **Revoke Access on Check-out** | The guest's access ends when the stay ends. | None | | Check-in offset | How long before check-in the guest code works. | Up to 24 hours. | | Check-out offset | How long after check-out the guest code still works. | Up to 24 hours. | The offsets work together with **Prevent Access Until Checked-in** and **Revoke Access on Check-out**. ## Activity logs **Activity Logs** is a timeline of every interaction with the lock, each with a timestamp. | Entry | Meaning | | -------------------- | ----------------------------------------------------------------------------------------------------- | | **Manually** | A physical action, such as locking or unlocking by hand, or the door opened or closed without a code. | | **Keypad** | A lock or unlock on the keypad with a code. | | **Access with Code** | Which code was used: a manual code or a fallback code. | | **Motor Blocked** | The lock mechanism met physical resistance. A hardware issue. | ## Access codes | Code type | What it is | | ------------- | ----------------------------------------------------------------------------------------- | | **Automatic** | Made by Guestway for a reservation, when the stay is confirmed, and removed when it ends. | | **Manual** | Made by a user on the lock, for cleaners, maintenance or long-term access. | | **Fallback** | A backup code for when automatic codes fail or are not available. | | Validity | Meaning | | ------------ | ---------------------------------- | | **Active** | The code works now. | | **Upcoming** | The code works in a future window. | | **Expired** | The window has ended. | The duration of a code is **Always**, or a window from **Valid From** to **Valid To**. For each code, the eye icon shows the PIN, the menu disables, enables, edits or deletes it, and the last-used time shows when it last opened the door. A used code can show *Code has been used & will be revoked soon.* **Schedule Overview** shows the scheduled access per user or guest. | Field of a new code | What it does | Limits | | ---------------------------- | --------------------------------------------------- | --------------------------------------------------------- | | **Name** | The label of the code, for example *Cleaning Code*. | Required. | | **Pin Code** | The numbers to type on the lock. | It cannot contain the number 0, and cannot start with 12. | | **Valid From**, **Valid To** | The window in which the code works. | None | ## Related * [How to create an access code](/reservations-and-operations/smart-locks/how-to-create-an-access-code.md) * [Static locks](/reservations-and-operations/static-locks.md) * [Guest journey](/guest-experience/guest-journey.md): self check-out and access. * [Service templates](/guest-experience/service-templates.md): services linked to locks. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.guestway.io/reservations-and-operations/smart-locks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.