|
|||
|
|||
Brian - maybe the better idea would be to store the passwords using the customizable Asset Configuration Note. You will get to store the passwords under each Asset in a structured way, unlike with History Notes.
Thanks. |
|
|||
|
|||
We used two of the user defined fields named password and password(copy)
Enter the information (and other notes) into the password field, and copy it to the password(copy). We do this in case someone accidently deletes something in the password field trying to copy, using Ctrl-C (or Ctrl-X). You can display the password field right next to the asset description in the tabs so its quick to find. Also the asset list can be exported to Excel and with some editing, gives you a quick list to give to the client. There is a way to display the fields in the Web interface by editing some template files (although not fully supported) Another option would be to sign up for LastPass.Com Enterprise (~$15 / month) and your team can be given selective access, which is something you CANNOT do currently in CommitCRM. |