Adjusting User Permissions

Every user in LDMS is assigned privileges. When you create a new user, you should review the default privileges that are assigned to all new users and adjust them accordingly.

Every privilege corresponds to a menu item in LDMS. For example, the Kit Entry permission controls access to QA/QC > Kit Entry. If you want to know what a particular permission does, find the LDMS menu item of the same name.

Modifying a user's permissions

  1. Click Administration > User Configuration from the LDMS menu bar.

  2. Select the user that you want to modify from the User ID drop-down list.

  3. Select the permissions desired.

    • The View permission allows a user to see the records (e.g. viewing aliquots in Specimen Management ).

    • The delete permission allows a user to remove records (e.g. deleting an aliquot).

    • The modify permission allows a user to change records (e.g. changing an aliquot's volume); the view permission would also be required separately.

    • The add permission allows a user to create new records (e.g. adding new specimens); this can be independent of the ability to view records, so a person could enter data without being able to see existing data.

    • The full permission is the same as giving a user access to view, add, modify, and delete.

  4. To make a user a system administrator, select the System Administrator Capabilities option.

  5. Click the button from the LDMS toolbar.

Tip:

Click on a column header to select or unselect all of the permissions in that column. This is useful if you want to quickly give someone full permission to everything in LDMS.

System Administrator Capabilities

At least one user at your laboratory must have System Administrator Capabilities. This gives the user access the certain features:

  • Reset and change passwords for other users

  • Lock out and unlock user accounts

  • Delete users

  • Designate other system administrators

By default, the original ADMIN account has system administrator privileges. Before deleting the ADMIN account, make certain that at least one user has system administrator capabilities.