Community Websites - Modifying Resident Credentials

Navigation: Community Website > Administration > Unit Administration
Purpose: Resetting an Resident's username or password

---

A Resident's credentials consist of a username and password. 

If the Resident has an email address on file with Management, the username will by default be the Resident's email address. If there is no email address on file, a username will auto-populate with the following convention:
Unit No., and status of the resident. Example: 101.owner, or 101.tenant. 

If the Resident's email address changes, they may need the username updated in order to log in with a valid username. 

Having a valid email address also ensures that the user can initiate a Forgot Password action, should they need to recover their account. 

The password, created for the first time or reset, must be 8 characters long. While special characters may be included in the password, take care not to insert any spaces.  Accidental spaces are one of the main reasons why owners are unable to log in.

---

To change a Resident's Username or Password

• Go to the Community Website and click on Administration, then click on the Unit Administration menu link.
• From the Unit Administration's User Profiles, find the user whose credentials need to be reset, and click on the Edit button, which is indicated by the pencil icon. 

• Once in the User Profile, click on the Reset Username or the Reset Password link, located next to the resident's name and role.

• For the Username Reset, you will see your current Username, which you need to modify, followed by a blank form field to input a new Username.  Both fields must match. Click Save to save the new Username.

• For the Password Reset, you will see the current Username, followed by a blank form field to input a new Password, and another to confirm the new Password. Both Password fields must match. Click Save to save the new Password.

When these steps are completed, the new credentials are saved and in use for both the current session, and any future login sessions.

NOTE: Be sure to test the Credentials before providing them to the User.