Guest access should be temporary, individual, and easy to revoke. Do not share the household’s master password, administrator account, alarm PIN, or permanent lock code with a cleaner, contractor, pet sitter, visitor, or short-term house sitter. Give each person the smallest access needed for a defined time, then test removal when the job ends.
Guest access plan at a glance
| Guest | Typical access | Time limit | Remove after |
|---|---|---|---|
| Cleaner | Unique door code; alarm code only if the home will be armed | Scheduled service window | Contract ends or staff changes |
| Pet sitter | Entry code, pet-area instructions, limited camera information | Trip dates plus a short buffer | Final visit is confirmed |
| Contractor | One entrance, temporary code, no camera or admin access | Appointment window | Work and tool collection finish |
| House sitter | Entry, alarm use, emergency contacts, selected device control | Travel dates | Keys and responsibility return |
| Overnight visitor | Door access and simple arming instructions | Visit dates | Departure |
1. Inventory every way someone can enter or control the home
List physical keys, keypad codes, smart-lock codes, alarm PINs, app invitations, camera shares, garage remotes, gate fobs, voice assistants, Wi-Fi credentials, and emergency lockboxes. Add the account owner, each administrator, and every person who can invite another user.
Access often survives in more than one place. Deleting a lock code does not remove an app invitation. Removing someone from the alarm app does not recover a copied key or garage remote. The inventory is the revocation checklist.
2. Use one identity per person
Create a named code or account for each guest. Shared “cleaner” or “family” codes make it hard to identify use, stop one person without affecting others, or investigate an unexpected entry. Never reuse the owner’s master code.
- Use a unique door code and alarm code where the system supports both.
- Set start and end times instead of relying on memory.
- Give app access only when a code cannot do the job.
- Reserve administrator rights for the smallest possible group.
- Keep a physical backup entry method for lock, hub, internet, or battery failure.
3. Match access to the job
A contractor who needs the side door does not need camera history, alarm settings, household routines, or a front-door code. A pet sitter may need an alarm PIN and the ability to enter twice a day, but not access to bedrooms or indoor cameras. A house sitter may need wider control, but only for the travel window.
Write down the exact door, days, hours, alarm mode, camera expectations, and emergency contact. If the platform cannot enforce the boundary, decide whether a supervised visit or physical key is safer.
4. Configure smart-lock codes safely
Check the door fit, deadbolt alignment, auto-lock timing, code schedule, battery level, failed-attempt alerts, and manual-key fallback before the guest arrives. Test the code with the door open and closed, then lock out and unlock from the guest’s expected path.
The smart-lock battery and outage checklist covers battery warnings, direct versus platform control, and backup entry. If the home has several residents, also review the shared-house smart-lock guide.
5. Give alarm access without giving away control
Explain how to disarm on entry, arm on exit, respond to a countdown, silence a false alarm, and call the right monitoring or household contact. Use the provider’s test mode for practice. Do not ask a guest to learn the system during a live alarm.
Record which sensors protect the guest’s route and whether a pet, cleaner, or contractor could trigger a motion sensor. Use the false-alarm reduction checklist to tune delays, codes, pet rules, and response steps.
6. Set camera boundaries before sharing access
Tell guests where exterior and common-area cameras are used. Do not place cameras in private spaces. Limit live view, history, export, audio, deletion, and settings access separately where the platform allows it. A person who only needs door access usually does not need a camera account.
Review camera privacy zones, microphones, notifications, shared users, and linked smart-home accounts. The HomeKit security privacy guide provides an Apple Home and vendor-app audit that also applies to many mixed-platform households.
7. Build a simple arrival and departure routine
| Moment | Safe action | Avoid |
|---|---|---|
| Before arrival | Confirm the named code, schedule, route, alarm state, and contact | Sending a master code in a group chat |
| At entry | Disarm using the guest’s own code and confirm the door relocks | Disabling sensors for the whole visit |
| During visit | Use only approved rooms and controls | Sharing camera or admin credentials |
| At exit | Close windows, lock doors, arm the agreed mode, report problems | Assuming auto-lock or auto-arm succeeded |
| After service | Expire access and review the event log | Leaving “temporary” access active |
8. Test failures before relying on guest access
- Turn off internet access and test the door code, lock, alarm, and local siren.
- Simulate a low lock battery and confirm who receives the warning.
- Test a phone with no data connection and identify the keypad or physical fallback.
- Confirm what happens if the guest mistypes the code several times.
- Cut power and time the hub, router, lock, camera, and keypad backups.
- Practice a false alarm through the provider’s approved test process.
9. Revoke access completely
Expire the lock code and alarm PIN, remove app invitations, sign out shared sessions where available, recover physical keys and remotes, rotate a lockbox code, and remove the person from automations and household groups. Review the event log for use after the agreed end time.
If you are moving systems, the security migration guide shows how to remove old users, integrations, devices, and billing paths without leaving an orphaned account.
10. Run a quarterly access audit
List every active person, code, key, app invitation, camera share, voice assistant, integration, and administrator. Remove access that no longer has an owner or a current reason. Test one temporary-code expiry and one emergency entry path each quarter.
Preserve only records you are allowed and need to keep. The evidence preservation guide covers original clips, event timelines, incident notes, and working copies.
Where Abode fits
A sensor-led system can keep entry detection separate from camera noise. Compare the Abode Smart Security Kit, Abode Lock, Mini Door/Window Sensor, and current Abode plans. Verify current guest-code, user, automation, and monitoring features for the exact setup before ordering.
Frequently asked questions
Should I give a cleaner my alarm master code?
No. Create a named user code with the smallest access and shortest schedule that works. Keep the master code private.
Is a smart-lock code safer than a physical key?
A scheduled code is easier to expire and audit, but it depends on correct door fit, batteries, platform behavior, and a working backup entry method.
Should a pet sitter have camera access?
Usually only if live view or event history is needed for the job. Explain camera locations and limit access to the minimum views and time window.
What should I remove when a guest leaves?
Remove codes, app invitations, camera shares, household groups, automations, physical keys, remotes, and lockbox access. Check the event log after revocation.
August 2026 update: manage guest access as a timed lifecycle
Guest access should have a named owner, a defined purpose, a start time, an end time, and proof that every permission was removed. A lock code alone is not the full access path. The guest may also receive an alarm code, app invitation, camera view, garage or gate access, monitoring instructions, a mechanical key, or a shared password. Put every route on one access record before the visit begins.
Create one guest-access record
Record the guest’s name, access purpose, approved doors and areas, arrival and departure window, owner, backup contact, codes or app roles issued, camera access, monitoring instructions, physical keys, parking or gate credentials, and the date each item must be revoked. Use the smart-lock access-code audit to identify stale or duplicated codes before adding another one.
Do not put a PIN in the calendar title, group chat, door label, or general house note. Send the minimum information through an agreed private channel, then delete or archive it according to the household policy after the visit.
Match access to the job
- House sitter: may need the main entry, alarm arm and disarm, pet or plant areas, emergency contacts, and a clear camera-privacy boundary. The HomeKit house-sitter checklist provides a useful model even when the home uses another platform.
- Cleaner: usually needs a narrow time window, one door, the minimum alarm procedure, and no camera exports, billing, device administration, or account recovery.
- Contractor: should receive access only for the approved work area and appointment. Use the repair or installer handoff process when a technician needs panel, network, or device access.
- Family or friend: may need recurring entry, but recurring does not mean permanent administrator access. Review the permission on a schedule and after any move, phone loss, relationship change, or shared-house change.
- Emergency backup: should be able to act when the primary owner is unavailable without sharing the owner’s credentials. Rehearse this with the backup administrator drill.
Separate entry, alarm, camera, and account permissions
A person who can unlock a door does not automatically need to change alarm users, view indoor cameras, export clips, edit automations, see billing, or recover the owner account. Assign each permission separately where the platform allows it. Run the security app permission audit on the guest’s phone and the household administrator’s phone so notifications, location access, camera access, and background operation match the job.
For cameras, follow the shared-user access audit. Decide whether the guest can view live video, receive alerts, review history, download clips, speak through a camera, change detection zones, or delete events. Indoor-camera access deserves a separate decision from entry access.
Test arrival before the owner leaves
- Create the guest identity, code, or invitation with the intended start and expiry.
- Test the approved door from outside. Confirm the door is physically latched before and after the test.
- Arm and disarm using the exact guest procedure under provider-approved test mode where needed.
- Confirm the guest receives only the intended alerts and cannot reach owner-only settings.
- Test what happens if the internet is down, the guest’s phone is unavailable, or the smart lock battery is low.
- Confirm the backup contact can help without sending the owner’s password or recovery code.
Keep a physical fallback under control
If the guest receives a mechanical key, record the key identifier, handoff time, return deadline, and who verified the return. Use the mechanical-key backup checklist to test the cylinder and keep the fallback usable without leaving an untracked copy. A hidden key is not a reliable revocation method.
Revoke access in a fixed order
- Disable the temporary lock and alarm codes.
- Remove the guest from alarm, lock, camera, garage, gate, voice-assistant, and smart-home apps.
- End temporary schedules, geofences, scenes, and automations created for the visit.
- Collect mechanical keys, remotes, fobs, and printed emergency information.
- Remove the guest from monitoring contacts and household communication groups.
- Review account activity and camera exports during the access period.
- Test the old credential and confirm it fails without exposing the new credential.
- Close the access record with the revocation time, verifier, exceptions, and follow-up owner.
Forty-five-minute guest-access handoff test
- Minutes 0–5: review the guest’s approved areas, times, emergency duties, privacy limits, and owner.
- Minutes 5–10: issue the minimum lock, alarm, app, camera, and physical credentials. Record each one without exposing the secret in the shared checklist.
- Minutes 10–15: test entry, latch state, arm, disarm, and the intended alert from the guest’s actual phone or code.
- Minutes 15–20: test that owner-only settings, billing, account recovery, camera exports, and unrelated doors are unavailable.
- Minutes 20–25: rehearse internet loss, phone loss, low lock battery, a false alarm, and an unanswered owner call as tabletop cases.
- Minutes 25–30: verify the backup contact, monitoring instructions, emergency services guidance, and the mechanical fallback.
- Minutes 30–35: simulate departure by disabling every issued digital permission and collecting every physical item.
- Minutes 35–40: try the expired code and removed account. Confirm failure, then verify the owner’s access and normal alarm state still work.
- Minutes 40–45: restore the intended future schedule if this was a rehearsal, record the evidence, and assign any failed control.
Pass only when the guest can complete the approved job, cannot reach owner-only controls, has a safe fallback, and can be removed without changing every household credential. Do not leave access active because revocation was inconvenient or untested.