> 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/how-to-create-a-static-lock.md).

# How to create a static lock

This guide shows you how to add a static lock with its code and link it to listings, so that guests get the right code.

{% hint style="info" %}
**Before you start**

* The code of the lock.
  {% endhint %}

## Create the lock

{% stepper %}
{% step %}

### Add the lock

Go to **Static Locks**, and click **+**.
{% endstep %}

{% step %}

### Fill in the lock

Fill in the **Name** for your team, the **Door Name** for guests, the **Pin Code** and the **Type**.

If automated messages must share the code, turn on **Visible to guest**.
{% endstep %}
{% endstepper %}

## Link it to listings

{% stepper %}
{% step %}

### Link the listings

Link the listing the lock opens. For a shared door, such as a building entrance, link the complex instead of each listing.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
When you replace a device, edit the lock instead of deleting and recreating it. Deleting removes its access references everywhere.
{% endhint %}

## Related

* [Static locks](https://docs.guestway.io/reservations-and-operations/static-locks.md): all fields.


---

# 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/how-to-create-a-static-lock.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.
