> 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/static-locks.md).

# Static locks

Static locks are the locks without internet, such as padlocks, lock boxes and numpads, with their codes and the listings they open.

## Static locks list

| Column         | What it shows                                                 |
| -------------- | ------------------------------------------------------------- |
| **Name**       | The internal name of the lock.                                |
| **Door Name**  | The entry point, for example *Apartment Door* or *Main Gate*. |
| Linked complex | The building the lock belongs to.                             |
| Linked listing | The rental unit the lock is attached to.                      |
| **Pin Code**   | The code, hidden until you click the eye icon.                |

A click on a row opens the lock.

## Information

| Field                | What it does                                                                                                                             | Limits                                        |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| **Name**             | The internal name, visible only within Guestway, for example *Garage Lock*.                                                              | Required.                                     |
| **Description**      | Extra context for your team.                                                                                                             | Optional.                                     |
| **Type**             | **Padlock**, **Lock Box** or **Numpad**.                                                                                                 | Required.                                     |
| **Door Name**        | The name guests see, for example when the code is shared in the inbox.                                                                   | None                                          |
| **Pin Code**         | The access code.                                                                                                                         | None                                          |
| **Visible to guest** | Syncs the code with the custom field `gw_codes` in your PMS, so that automated messages can share it. When off, the code stays internal. | Only when your PMS supports the custom field. |

## Linked complexes

The complexes of the lock, for shared doors such as building entrances, gates and shared storage rooms. **+** links a complex.

## Linked listings

The listings of the lock. **+** links a listing, and the unlink icon detaches one.

## Manage

**Delete** removes the linked listings and deletes the lock completely.

## Related

* [How to create a static lock](https://docs.guestway.io/reservations-and-operations/static-locks/how-to-create-a-static-lock.md)
* [Smart locks](https://docs.guestway.io/reservations-and-operations/smart-locks.md)
* [Guest portal](https://docs.guestway.io/guest-experience/guest-portal.md): where guests see their codes.
* [Service templates](https://docs.guestway.io/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/static-locks.md?ask=<question>&goal=<user_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.
