Create reusable key access points

An access point stores a reusable location, its guest instructions and, when relevant, a default code. Staff can then select it as the pickup or drop-off exception for an individual reservation.

It does not replace the operation default. Set that starting point in Set default key pickup and drop-off.

Before creating one#

• The account needs the Agency plan and the Key access points feature.
• You need permission to create and read access points.
• You must be assigned responsibility for reusable locations, instructions, and codes; a visible menu is not that designation.
• For the Office type, create the correct office first and verify its address.
• Decide who may see codes. A default code can be included in guest communication and is also visible to authorized staff in Holidario.

Create a lockbox#

1. Open PMS > Key access points and select Create.
2. Choose Lockbox.
3. Enter an unambiguous internal name, such as the rental and physical location.
4. Keep Active enabled if it should appear in reservation selectors.
5. Enter the address and select the correct search result.
6. Add a default code only when it is stable and authorized for every guest who will use that point.
7. Enter instructions for every language you use. Each text allows up to 256 characters.
8. Save, then open the record to verify its location, status, code and languages.

The address, code and instructions are technically optional. Treat them as a required operational check before using the point for a reservation.

Create an office point#

1. Choose Office and select an office in the team.
2. Add an internal name and activate the point.
3. Enter reception or collection instructions in the required languages.
4. Save and verify that the record shows the expected office and address.

The address comes from the selected office. An office point does not allow a reservation-specific code or instruction override; correct the office or the access point instructions when its general information is wrong.

Check it before use#

• open the record and confirm its location does not say Not configured;
• review every language and exclude internal notes, other guests' data and ambiguous directions;
• physically verify the lockbox, address and code;
• use a short, unambiguous name that remains distinguishable in a compact list;
• deactivate the point when it is no longer operational.

An inactive point is excluded from new reservation exceptions. Before deactivating one or changing a code, review upcoming arrivals that already depend on it.

If it is missing or will not save#

• The menu is missing: check the plan, feature and read-key-access-point.
• You cannot create or edit: an administrator must check create-key-access-point or update-key-access-point.
• The office is missing: verify the active team and that the office belongs to that team.
• The address is wrong: edit it and select a valid search result; do not rely on incomplete free text.
• It is absent from a reservation: confirm the point is active and belongs to the same team.

Device acceptance for this create-and-edit flow has not yet been verified. Complete the initial configuration and final language-and-code review on a wider screen. If you open the form on a smaller screen and cannot see every field, control, and saved summary, do not save; repeat the review on a wider screen. Never include the code in screenshots sent to support.

Next step#

Apply the point only to the stay that needs it with Override key handover for a reservation. If access remains denied or the point belongs to another team, do not recreate it as a duplicate: send support the point ID, active team and screen, with the code hidden.