The user manager displays a list of active and (if present) a list of deleted users. Users are presented in a tabular format showing userid, name, a reset password icon (), trusted status and default permission. The effective permission for the user (if different than the default permission because of per-calendar or per-user-group permissions) may also appear.

Click on a user's userid to login as that user. If the user data contains an email address the mail icon () appears next to the user's name. Click on this icon to send that user an email. Trusted admin and super users may download an excel spreadsheet containing all user data (excluding passwords) by click in the user download icon ()

Using users

One reason to create users is to track who has added an event to the database or who has last modified an event. Each time an event is added the currently logged in user is recorded as the owner of the event. Also, whenever an event is modified the currently logged in userid is recorded as last editor.

Another important use for users is to assign permission levels. By using different permission levels one may control who may add or edit events, who may manage calendars, who may add other users, etc.

Finally, without users it would be impossible to insure against one user from changing another user's events. If two users have the same permission level (for example edit) they may not edit each other's events.

Creating users

Prior to setting up users it is helpful to ask yourself a few questions. Your answers to the questions will help you setup an effective user system. Each question is presented below followed by upshot based on your answer to the question (read the entire list before proceeding). The super user is created the first time the software runs. The super user must always exist.

Will more than one user be adding or managing events?

Will more than one user be managing calendars?

Will more than one user be managing users and other system-wide settings?

Should two users be able to change each other's events?

Are there certain users who should be able to change every event?

Are there users who should be able to add events but not delete or modify them?

Should users be able to add or edit themselves or change their own passwords?

Should events be reviewed prior to appearing on the calendar?

Do you wish to have visitors login simply to see the calendar?

Have your visitors previously logged in to the website? Do you wish to avoid having them login again?

Forgotten passwords

There are a number of ways for an administrator to handle lost or forgotten passwords:

Data managers