Many companies are, understandably, extremely concerned about employees stealing their sales database when they leave the company. Finding the right balance between giving employees access to the data so they can do their job, and securing the data so they can't steal it is always going to be challenge, but I think more could be done to control data security in ACT!

 

For example, even if you set a users security role and permissions so that they can't access the export to Excel functions, they can still print off a report containing all the data, so a "Disable Reports" option would be a help. Even if you did that, the technically savvy could ODBC into the SQL database and access the data that way; (Can't think of a way to prevent that one - can it be restricted to Administrators?).

 

Beyond that, it would be useful if there was at least an audit trail; a log somewhere that recorded the fact that a user had run an export of data.

 

With synchronized, remote databases, would it not be sensible that they became disabled and unusable if they have not been synchronized in a period of time?

 

Data security can never be perfect, but the more layers of defense we build in the better it will be.

 

Jeff