Address Book Permission Refinement
Currently, user / group permissions control access to the "Address Book" as a single entity. However, there are frequently cases where the permissions need to be more granular than this.
For example, a customer has no use for the concept of "Individuals" and they want to prevent users from inadvertently adding this kind of record into the database. Currently, the only front-end solution is to deploy a MenuBuilder customization which removes all references to "Individuals" from the various record creation menus.
Ideally, this should be handled by separating the user / group permissions into buckets for:
- Company
- Individual
- Contact
Business logic would be used to ensure at least Company OR Individual was selected - because a Contact must be attached to a parent-level record. Additional thought might be given to expanding this to include the old-style lead (starred) records as this was also a common request in the past.