Q:

Should I, for any reason, allow a Super Admin to see the users' password through the UI? 

Currently I am developing an application with 3 roles: 1 for customers, 1 for the company employees and another one for a Super Admin. 
Is it a good practice to allow Super Admin users to see/edit the users' passwords through the UI?  Or should it only be modified directly through the DB? 
UPDATE: I am using asp.net membership provider and MySQL.  Therefore, there is a table in the DB called my_aspnet_membership which stores two fields: Password and PasswordKey.  The field PasswordKey seems to be the encrypted password.  However, the Password field is stored in plain text.  So, can anyone tell me why this is designed in this way if it is not a good practice?  Thank you all for your responses! 
UPDATE: For those who asked if it really stores the password in two different fields:

A:

Your password should not be stored un encrypted inside your database and as such, shouldn't be visible to users of the UI nor the database. 
As for whether it should be modifyable, sure. 
In this case the password should be re-generated through user or administrator request.  Again, this should be encrypted in the database.  My preference would be to auto generate the new password for the user rather than have an administrator type it themselves. 
Given this, the only way to change the password directly in the database would be to encrypt it first before insertion.  It's quicker to do this through an UI that deals with the encrypting. 
UPDATE
In answer to your update, you should specify in your web.config that the password format be hashed:
<providers>
<add [...]
    passwordFormat="Hashed"
/>
</providers>

as outlined here:
http://msdn.microsoft.com/en-us/library/ff648345.aspx

A:

No user should be allowed to see the Plaintext password of any other user whatsoever.  The password must be encrypted atleast if not hashed even in the database.  
You MAY allow the super admin to change any user's password, but allowing him to see it in plaintext is taboo. 
EDIT: Are you absolutely certain the password field stores the password in plaintext, while there exists another passwordkey field?  Because, it sounds similar to a 'salt' mechanism to me.  Where, the password is first encrypted with one key, and then re-encrypted with the passwordkey field.  
EDIT 2: I am now almost absolutely certain that your database is using a salted password.  Salted passwords are often used to increase the security level of the database.  For more information on salt, check this.