When a resident says they cannot sign in, it usually comes down to the wrong email, an unfinished invitation, or a password issue. This checklist is for property managers and staff working in the web admin. Start by asking the resident to read you the exact error: “wrong password” and “account not found” point to very different fixes.
1. Confirm the email on file
Look the resident up under Residents and check the email in the Contact column matches exactly what they are typing. A typo or an old email is the single most common cause. Residents sign in with their email (guards can also use a username), so even a small mismatch fails.
2. Check their account status
The Residents list shows only Active or Inactive, and it shows Active residents by default. Change the filter to see Inactive ones.
- Inactive: the resident was deactivated, so sign-in is blocked until the account is reactivated.
- Active: the account is fine, so it is most likely a password issue or an unfinished setup (next).
To find people who never finished setup, open Residents > Sign-ups. A home where nobody has signed in shows there, and a person who signed in with the temporary password but never chose their own shows Didn’t finish setup. From there you can remind them, or open the resident and use Resend invitation.
3. Reset the password
Have the resident tap Forgot Password? on the sign-in screen. The reset link is good for one hour. If that does not work for them, open Edit Resident, press Resend invitation (top right) and confirm with Send sign-in details. A resident gets a new temporary password, their current password stops working, and they are signed out on every device. Their phone stops getting alerts and gate calls until they sign in again with the new details. Any Google or Apple sign-in they had linked is removed. Anyone who is not only a resident of this community (for example staff, a board member, a guard, or someone with a home in another community) instead gets an emailed link to set their own password, and nothing else on their account changes. Either way, new and reset accounts choose a new password on first sign-in, so make sure they finish that step rather than reusing the temporary one.
4. Make sure they are in the right place
Confirm they are using the resident app or the resident website (not a staff address), signing in with the email on file, and running the latest app version. If they are opening a bookmarked page, have them use the current address.
5. Rule out a lockout or blocked email
- Too many attempts blocks sign-in from that internet connection for about 30 minutes (after 5 failed attempts in 15 minutes). It covers everyone on the same network, and it clears on its own.
- Invite or reset email never arrives: ask them to check spam, and confirm their email provider is not blocking messages from the community. Resend after correcting the address. When you resend to a resident, the Invitation credentials window shows the temporary password, so you can read it out or press Print.
6. Check whether the community itself is paused
If no one in the community can sign in, the account may not be the problem. The whole community could be suspended. Confirm the community’s status before troubleshooting individual logins.
An invited adult cannot get in
If the person was invited to a home rather than added by you, check People who can sign in on the Households page. A Pending invitation means they have not accepted yet: use Resend (allowed 10 minutes after the last send) or Cancel and invite again. The link works for 7 days. A person who already has a home in this community cannot accept a second one; add it to their account yourself. See Household logins (office): who can sign in for each home.
Still locked out?
If the email is correct, the account is active, and a fresh invitation still fails, escalate to your Maximum.Community administrator with the resident’s email, their account status, and the exact error message they see.