CCall Home Help
Homeowner decision guideU.S. national guidance

Homeowner decision guide

Reviewed and updated September 22, 2026

How should old smart-lock access codes and user accounts be audited?

Safety boundaryRemove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected device before concluding the work is complete. If physical keys were issued, account for them separately; do not assume an app change disables a mechanical key.
Help by phoneSpeak with a locksmith.

Checking the call option…

What you can discuss
  • Explain your problem or project in your own words.
  • Ask about service in your area and scheduling.
  • Discuss the next step and what the provider needs to know.

Calls connect to an independent provider; we may receive compensation. Service area, scheduling and job acceptance are confirmed on the call.

Prefer to read first? Explore the guide

Audit every route that can authorize entry: keypad codes, app users, administrator roles, connected platforms, and physical keys. Start with an inventory of doors and locks, then list the people who still need each form of access. Removing a person's name from your contacts is not the same task as removing their credential from the lock system.

Schlage's app guidance separates changing an access-code name from changing the code itself. Its role documentation also distinguishes administrator permissions from limited guest access. An audit should therefore check the actual credential and role, not merely tidy the display names. Activity history can be useful context, but a code event alone does not establish which person used a shared credential.

More context for this decision

Details that can change the next step

Use the sections that match what you can safely observe. They add context without diagnosing the property from a distance.

How should old smart-lock access codes and user accounts be audited?

Revoke carefully and verify delivery

Remove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected device before concluding the work is complete. If physical keys were issued, account for them separately; do not assume an app change disables a mechanical key.

How should old smart-lock access codes and user accounts be audited?

Create a repeatable closeout record

For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing credentials. Repeat the review after contractors, household changes, a lost device, or property turnover. Suspected unauthorized entry requires a security response, not just a routine cleanup of user names.

Separate safety, observed conditions and project scope

Which situation best matches the home?

01

Revoke carefully and verify delivery

Remove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected device before concluding the work is complete. If physical keys were issued, account for them separately; do not assume an app change disables a mechanical key.

Notice next: Remove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected.

02

Create a repeatable closeout record

For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing credentials. Repeat the review after contractors, household changes, a lost device, or property turnover. Suspected unauthorized entry requires a security response, not just a routine cleanup of user names.

Notice next: For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing.

03

Decision point 3

For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing credentials. Repeat the review after contractors, household changes, a lost device, or property turnover. Suspected unauthorized entry requires a security response, not just a routine cleanup of user names.

Notice next: Record the visible condition and timing without opening, dismantling or entering an unsafe area (3).

Safe observation

What to record before contacting a professional

Use safe, visible observations and existing records only.

These observations organize the next conversation; they do not diagnose the property or authorize work.

What to record
  1. Remove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected.
  2. For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing.
  3. Record the visible condition and timing without opening, dismantling or entering an unsafe area (3).
  4. Record the visible condition and timing without opening, dismantling or entering an unsafe area (4).
Stop and get appropriate help
  • Remove credentials that no longer have a legitimate purpose using the model's documented process.
  • Review integrations separately and preserve your own owner access and recovery information.
  • Check that changes have reached each affected device before concluding the work is complete.
  • If physical keys were issued, account for them separately; do not assume an app change disables a mechanical key.
Move from information to action

Who is the useful next contact?

Qualified locksmith

Use when the question requires inspection, testing, repair, installation or a property-specific scope.

  • Remove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected.
  • For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing.
  • Record the visible condition and timing without opening, dismantling or entering an unsafe area (3).
  • Record the visible condition and timing without opening, dismantling or entering an unsafe area (4).
Relevant manufacturer, utility, insurer or local authority

Use when product instructions, utility responsibility, coverage, permits or local rules change the decision.

Contact guidance explains who may help and what to prepare. It does not verify a provider, license, price, arrival time or acceptance of the request.

Checking whether the call request form is available

No request details are needed while this check is pending.

This status does not confirm provider availability, service area or job acceptance.

Short answers

Questions people ask before the call

How should old smart-lock access codes and user accounts be audited?

Audit every route that can authorize entry: keypad codes, app users, administrator roles, connected platforms, and physical keys. Start with an inventory of doors and locks, then list the people who still need each form of access. Removing a person's name from your contacts is not the same task as removing their credential from the lock system. Schlage's app guidance separates changing an access-code name from changing the code itself. Its role documentation also distinguishes administrator permissions from limited guest access. An audit should therefore check the actual credential and role, not merely tidy the display names. Activity history can be useful context, but a code event alone does not establish which person used a shared credential.

What should I document before the next step?

Remove credentials that no longer have a legitimate purpose using the model's documented process. Review integrations separately and preserve your own owner access and recovery information. Check that changes have reached each affected. For each lock, record the review date, remaining authorized roles, removed access, and any outstanding key-return or ownership-transfer question. Do not store working codes in a public spreadsheet or publish screenshots containing. Record the visible condition and timing without opening, dismantling or entering an unsafe area (3).

What still needs local or property-specific confirmation?

Finished text does not establish a remote diagnosis or a model-specific repair instruction. Current site ownership, canonical URL and internal-link placement require separate review.

Where this guidance applies

The explanation, safe observations and preparation questions apply as general U.S. homeowner guidance.

Confirm permits, adopted codes, licensing, property responsibility and service scope for the actual address.

A ZIP code may help screen service availability; it does not establish a local rule, price or provider commitment.

Sources and boundaries

What supports this guide?

Finished text does not establish a remote diagnosis or a model-specific repair instruction.

Current site ownership, canonical URL and internal-link placement require separate review.

Source candidates have not been independently approved or preserved as approved SourceVersions.

No price, service availability, license, warranty coverage, search volume or local legal applicability is inferred.

This national guide cannot diagnose the property, verify a provider, or confirm address-specific availability.

Permits, adopted codes, licenses, property responsibility and product instructions must be confirmed for the actual location and scope.