If you are taking possession of a Generic account (also called a Nonhuman account) you will need to change its password.

Unsure what accounts your area has?

You can browse the OrgChart to see what nonhuman accounts are associated to whom. A nonhuman account's owner is treated like a team supervisor.

If you haven't already requested ownership of a new or existing generic account, submit a Google Assistance Request in Jira.

Once the Help Desk has notified you the ownership process is complete, you will need to sign in to iam.appstate.edu.

Since you are the owner, sign in using your personal, App State username and password - do not use the generic account username.

If this is your first time signing in to iam.appstate.edu, you must update your user account password as well. Once you do, you won't need to do so again for 365 days.

Once inside the IAM site, look for the Help users link on your dashboard and click it.

Help Users link.


The next screen will show you a listing of all the generic accounts you currently own. Click on any part of the bar except the User name link to get to the password change form.

Listing of generic accounts.

The form will look much like your own password change page. Double check the username at the top of page so you don't change your own password, then scroll to the bottom.

Check the username.

Enter the new password for the account conforming to format requirements. Click the Change passwords button to finish.

Security Question warning

You may see the error below when arriving on the Passwords page. You can ignore it as Security Questions are not used with Generic accounts.

Error message.

You should now be able to sign in to Google using your generic account username and password. Remember, use the full email address at the Google prompt and just the username at App State sign in.

Consider making your first action setting the forward address for the account to your own email address.

If you encounter any problems, please contact the Help Desk at 828-262-6266 or report back to the original Jira request ticket.