Re: Web interface "face lifting"
Hello All,
I too initially thought document access via the web interface was necessary. But having used CommitCRM for over a year now, we've adapted to make the web interface work for us.
One major concern with the web interface, is the inability for dual authentication. We can't have technicians logging into the web interface on rogue PC's where key loggers could be installed.
So we store ZERO passwords/usernames in Commit! Instead for any confidential data; one, the CommitCRM document folders are located on Windows Server 2003 with access granted only to specific users, two, we use Adobe Professional for our forms design so any firewall forms, backup forms and any other form containing potentially confidential data we use Adobe's password security.
How did we adapt: our client assets i.e. servers and PC's we used the notes section for the specific asset to record key features i.e. O/S, Office version, CD drive type, video card, wireless card model, sound card, raid or no raid, raid card. For for firewall assets we record the IP, subnet, gateway, DNS1, DNS2 in the notes section. We use a standard protocol for username/passwords to the firewalls on client sites, so we don't need to record that in the notes section. We create assets for the ISP under each client, we create assets for the mobile phones (Microsoft mobile), we create assets for the GoDaddy certs, assets for domain names, the list goes on and on.
With all that said I still would like a more modern, non-popup, clean web interface. Knowing the CommitCRM team, they've heard us and probably quietly working on this already. CommitCRM is great, they listen to us.
Brian Williams
Advantech NW
Hello All,
I too initially thought document access via the web interface was necessary. But having used CommitCRM for over a year now, we've adapted to make the web interface work for us.
One major concern with the web interface, is the inability for dual authentication. We can't have technicians logging into the web interface on rogue PC's where key loggers could be installed.
So we store ZERO passwords/usernames in Commit! Instead for any confidential data; one, the CommitCRM document folders are located on Windows Server 2003 with access granted only to specific users, two, we use Adobe Professional for our forms design so any firewall forms, backup forms and any other form containing potentially confidential data we use Adobe's password security.
How did we adapt: our client assets i.e. servers and PC's we used the notes section for the specific asset to record key features i.e. O/S, Office version, CD drive type, video card, wireless card model, sound card, raid or no raid, raid card. For for firewall assets we record the IP, subnet, gateway, DNS1, DNS2 in the notes section. We use a standard protocol for username/passwords to the firewalls on client sites, so we don't need to record that in the notes section. We create assets for the ISP under each client, we create assets for the mobile phones (Microsoft mobile), we create assets for the GoDaddy certs, assets for domain names, the list goes on and on.
With all that said I still would like a more modern, non-popup, clean web interface. Knowing the CommitCRM team, they've heard us and probably quietly working on this already. CommitCRM is great, they listen to us.
Brian Williams
Advantech NW
Comment