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

# Static Locks

Static Locks are the manual locks at your properties — padlocks, lock boxes, and numpads — that don't connect to the internet. The **Static Locks** page tracks each one with its name, location, lock type, and PIN code so your team and guests always have the right access information at hand.

***

### The Static Locks list

The page shows every static lock connected to your account in a single, organised view. Each row carries:

* **Name** — the lock's custom label.
* **Door Name** — the physical entry point (e.g. *Apartment Door*, *Main Gate*).
* **Linked Complex** — the building or compound the lock belongs to.
* **Linked Listing** — the rental unit the lock is attached to.
* **PIN code** — the access code (hidden by default; click the eye icon to reveal).

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/yr4635malk>" %}

Click any row to open the lock's detail panel for editing.

***

### Lock detail view

The detail panel breaks the lock into three cards: **Information**, the linkage cards (**Linked Complexes** and **Linked Listings**), and **Manage**.

#### Information

Click the **edit** icon at the top of the **Information** card to flip the fields into editable inputs. Click the green checkmark to save or the red close icon to discard.

* **Name** — the lock's custom label, used in lists and reports.
* **Description** — optional extra context (e.g. *Lock for the storage room shared with neighbours*).
* **Type** — the kind of static lock. Pick from:
  * **Padlock**
  * **Lock Box**
  * **Numpad**
* **Door Name** — the public-facing label guests see when the code is shared with them in the [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox).
* **Pin Code** — the access code; hidden by default and revealed via the eye icon.
* **Visible** — when enabled, the code is synchronised with a custom field named `gw_codes` in your PMS (if your PMS supports it). Once synced, you can automate messages that share the code with guests. When disabled, the code stays internal.

#### Linked Complexes

The **Linked Complexes** card shows every building or compound the lock is associated with. Click the **+** icon to link an additional complex; complexes already linked can be detached from here too.

Use this for shared infrastructure — building entrances, gates, shared storage rooms — that applies across an entire complex rather than a single listing.

#### Linked Listings

The **Linked Listings** card lists every individual property listing the lock is connected to. Use the **+** icon to add more listings, or the unlink icon next to a listing to detach it.

#### Manage

The **Manage** card carries a **Delete Lock** option that permanently removes the lock from your account. Use it when a device is no longer in service or has been replaced.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/dr9o0x6cor>" %}

***

### How to create a new static lock

To create a new static lock, click the **+** button. You'll be prompted to fill out a few essential fields:

1. **Name** — a clear label that's easy to recognise later, especially when managing many locks.
2. **Door Name** — the physical location of the lock (*Apartment Door*, *Main Gate*, *Side Entrance*). This is what guests see when the code is shared with them.
3. **PIN code** — the numeric sequence users will input to open the lock.
4. **Visible** — enable this to sync the code with the `gw_codes` PMS custom field for automation; leave it off to keep the code internal.
5. **Lock type** — pick *Padlock*, *Lock Box*, or *Numpad* so the system can recognise and represent the device correctly.
6. **Linked listing** — connect the lock to a specific listing from your portfolio so the right guests get the right code.

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/vkmg385i3k>" %}

***

### Tips

* **Use Door Name for the guest, Name for your team.** Name is internal; Door Name is what guests see — keep both clear and short.
* **Pick the right lock type.** Type drives the icon and how the lock appears across Guestway, so don't default everything to *Padlock* if it's actually a Numpad.
* **Enable Visible to automate code sharing.** When your PMS supports `gw_codes`, this saves your team from manually copying lock codes into every message.
* **Link at the complex level for shared doors.** Building entrances and shared gates belong on the complex, not duplicated across every listing inside it.
* **Use the Description for the staff context.** Anything that helps the next person understand the lock's quirks (rotation schedule, who has the override key) goes here.
* **Delete carefully.** Deleting a lock removes its access references everywhere — if you're swapping the device, edit it instead of recreating it.

***

### Related pages

* [Smart Locks](https://docs.guestway.io/guestway-platform/smart-locks) — manage connected, internet-enabled smart locks with rotating per-reservation codes.
* [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox) — share static lock codes with guests directly from the **Access** tab during a conversation.
* [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal) — where guests see door codes during their stay.
* [General (Listings Details)](https://docs.guestway.io/guestway-platform/properties/general-listings-details) — link static locks to listings from the property's settings.
* [Service Templates](https://docs.guestway.io/guestway-platform/service-templates) — services that link to static locks (e.g. storage rooms, parking gates).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.guestway.io/guestway-platform/static-locks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.