ADT Keypad, Keychain Remote and Yale Assure Lock 2 shared users: sharing on these devices uses codes. ADT's user roles article explains each user has a four-digit security code: a Basic user, such as a dog walker or guest, gets a code that works only at the ADT Base, Keypad or touchscreen and has no app login; Standard and Admin users have their own codes and logins; the Duress user has a code that works only from the touchpad and needs professional monitoring.
The checks in more detail
Only the Primary and Admin roles can invite and remove users. The Yale Assure Lock 2 has its own Entry Codes that you can share with family, friends and others for trackable access through the app, and a programming code for adding and removing codes at the lock. To remove a user code at the lock, follow the Passage button steps and enter the code, or enter 00 to remove all user codes, which leaves the programming code.
Give guests temporary codes and delete them afterwards. Review who has codes when household members change. The Keychain Remote arms and disarms without a code, so give one only to trusted people and remove lost ones from Devices. Never share the programming code. Keep a private list of who holds which lock code and revisit it whenever a household member changes.
A guest who cannot get in may be entering the wrong number of digits or pressing the check mark too early. Clear any code a departed resident used the day they leave. A Basic user's code works at the Base, Keypad or touchscreen only, which suits a cleaner who should not have the app. ADT lists the Duress code as something to share with the household, so everyone knows it exists and knows to use it only in a genuine emergency.
Differential
Likely causes of “ADT Keypad, Keychain Remote and Yale Assure Lock 2 shared users”, and how to tell them apart
- 1
A shared code
What separates it It is unclear who unlocked the door or disarmed the system because several people share one code
How to confirm Give each person their own code so that every unlock and disarm is recorded against a name
- 2
A departed resident
What separates it A former resident's old code still works and can open the lock and disarm the system
How to confirm Delete that person's code the same day they leave so it no longer works on any device
- 3
A lost fob
What separates it The system can be armed or disarmed by someone who found a lost fob and pressed its buttons
How to confirm Remove the lost fob in the app so that it can no longer arm or disarm the system
- 4
A Basic user needs the app
What separates it A Basic user cannot log in to the app because a Basic code has no app access
How to confirm Make the person a Standard user if they need the ADT+ app on their phone
- 5
An unknown programming code
What separates it The lock's codes cannot be changed because nobody knows the programming code any more
How to confirm Recreate the codes by following ADT's steps for resetting and setting up the lock again
Before you touch a setting
Record this first — changing settings destroys the evidence
- The user role of the person who is affected
- The code that was used and by whom
- Whether a fob has been lost
- Whether the programming code is known
Try in this order
0 of 7 completedAssign separate codes
ReversibleAssign a separate four-digit code to each person, so that the history shows who armed the system or unlocked the door.
Use Basic codes for guests
ReversibleUse Basic codes for guests, which work at the Keypad and Base only and need no app login.
Share entry codes for the lock
ReversibleShare entry codes for the lock through the app, so that each visitor has a trackable code and you can remove it later.
Delete codes when done
ReversibleDelete codes when someone no longer needs access, on the same day, so an old code cannot be used again.
Remove lost fobs
ReversibleRemove a lost fob in the app as soon as you notice it is gone, so nobody can arm or disarm with it.
Keep the programming code private
ReversibleKeep the programming code private and never share it, since it is the code used to add and remove all the other codes.
Contact ADT
ReversibleContact ADT if access still fails after these steps, and have your roles and lock model ready.
Model-specific
What is true of this model and not of its siblings
- Codes
- Four digits for users, four to eight for the lock.
- Fob
- Needs no code.
- Other models this page answers
- These steps also fit the Yale Assure Lock 2 / Lock 2 Touch.
Stop boundary
When this stops being a self-service repair
- !If access to the home fails, contact ADT through chat and use your key for the door
- !If a fob is lost, remove it from the system at once so it cannot be used
- !If a code may have been compromised, change it straight away
Evidence ledger
Sources behind this answer
Primary, Admin, Standard, Basic and Duress users.
Yale lock setup, use and battery.
Keychain remote.
Keypad setup and use.
The company and its products.
Exact questions
Common questions
Can guests use the app?+
Guests cannot use the app if they have a Basic user code, since Basic users have no app login, only a keypad code.
Are lock entry codes trackable?+
Yes, lock entry codes are trackable, so you can see who unlocked the door and when, as long as each person has their own.
How do I clear all lock codes?+
To clear all lock codes enter 00 in programming mode, which removes every user code stored on the lock.
What does the fob do?+
The fob arms and disarms the system, so it is a convenient way to control the system without entering a code at the keypad.
Should I remove a lost fob?+
Yes, remove a lost fob straight away in the app, so that nobody who finds it can arm or disarm your system.
Is the Duress code shared?+
A Duress code is shared only with the people in the household who need it, and it should be a code that is kept private.
What is the programming code?+
The programming code is a code used to add and remove user codes on the lock, and it is separate from the user codes.
How do I remove all user codes?+
To remove all user codes, enter 00 in programming mode, which clears the codes stored on the lock.