ACT! offers a splendid array of individual preference controls from adjusting list and calendar filters, customizable menus to program default preferences for everything from font sizes, colors to scheduling rules.
What ACT! does NOT do is maintain all these preferences in a user-based component of the database. No, the preferences are configured in the machine-specific Windows user profile. This is just "how it's worked for years" but it's nuts and seems a relatively easy feature request to accomodate.
If ACT! user preferences WERE stored in the database instead:
- users could work from different workstations with their same preferences active upon log in.
- database owners could protect their database by eliminating menu options that might damage data or compromise security, based on who is logged in
- consultants and administrators would spend less time installing and configuring ACT! on each user's computer as the preferences could all be set in the master database
- support analysts would receive fewer calls from users who have lost their preferences due to a new Windows profile or simply logging in as a different user
Like all feature suggestions, this one will only be considered if enough of you provide your support/kudos. Additional benefits or suggestions are appreciated too!