Web User Requests Form

To look up a web user, go to the Requests tab, or the Requests icon on the menu ribbon.

Above the Requests grid, you can use Search like most other modules. (If you have the email address associated with the account, use the Keyword text box.)

You can open the Web User's form from any of their web requests, not just New User. To open the form, click on the 4-character reference code in the Number column.

That will open a Request form. To edit a web user (if you have the right permissions), you can open that form by clicking on the icon immediately to the left of the name in the Public User Account box at the top of the form.

This will open the Web User Details form.  (Ignore the tabs at the bottom of the form.)

Things you can do in the Web User Details form:

1. Send the user a password reset (randomly generated). The passwords that are generated via LAMA versus the passwords generated when users click the "Forgot password" link online tend to have fewer non-alphanumeric characters, so they are easier for some users to enter.
2. Set Secret QA doesn't mean anything now, since we no longer require Secret QAs.
3. Some users have difficulties with finding their Verification Email when they first enroll. You can resend one to them here -- it seems that it might be slightly more likely to escape SPAM filters.
4. Users cannot change their emails themselves. When you use the Change Email button, you will be prompted to enter the new email twice (for spelling verification). LAMA will check whether a web account exists that's already using that email. If so, you can't use that email, because two accounts with the same email will render both accounts inoperable.
5. Users also cannot change their usernames themselves. You can do that with Change Username.
6. While you can't view users' passwords, you can remind them of their usernames -- all of the text before the original email address (in parentheses) is the username.
7. Lastly, you can render a web account active or inactive (all accounts are active on creation by default).