ID The "ID" column displays numbers that are automatically created by WBPS and used to identify user records. Each user that you create will have an ID number. If you have several password sets and applications, each user in each application and password set will have an ID number that is unique across the entire database used by the program. When data on this form is arranged alphabetically by Username, the ID numbers will appear scattered and somewhat random, as above. When data is sorted by order entered, however, they will appear in increasing order: Note that in this case the ID numbers may not be consecutive. Users number 53, 69, and 70 in the above example may have been deleted or may have been created in different password sets or applications. Why is ID important? You don't need to know the ID number for any user in order to use WBPS, and for most purposes you can ignore the ID column on this screen. When you have fully implemented WBPS on a site, however, the User ID is passed as a parameter when each user logis in and accesses the first secure page, and this can be used for usage tracking and analysis. Below is a browser window showing a user (betsy) who has just successfully logged into the Employees password set secure page on a site:    The parameter passed in the page address (in this case, m=4) contains the user ID of the person accessing the page. (The parameter name, "m" in this case, is assigned randomly by the program). The number "4" indicates the user ID, in this case, betsy: An administrator can collect statistical information from the server logs for this Web site, and can obtain a frequency count of the number of times each user has accessed each "First Secure Page" in a given period. Note: unusually high frequency counts for a single user may indicate that user's login name and password may be compromised and is being used by unauthorized users. If, for example, analysis reveals that most users access the Employees' area an average of once a week, but one user accesses it 50 times a day, it is possible that this user's login credentials have become known by unauthorized persons. The administrator can take immediate action by deleting the WBPS records for such users (and then republishing the WBPS files for the site) pending investigation of the possible security breach.