Security
We have defined the entities, how they relate to each other, how they will be uniquely identified, and we have defined the fields for each entity and how they map between CRM and ERP fields, and the CRUD synchronization actions.
We now need to review the security rules for the contact integration. The integration will change the data that is available in the CRM application and will change the actions that users can do, including having the ability to indirectly change ERP data.
The flexibility that you will have in implementing security rules depends on your CRM application.
A good way to review the security is to look at each of the CRUD actions in turn (create, read, update and delete), starting with the read action.
Security for "read" information
The new information that can be read in CRM is all the ERP accounts receivable customers, including some ERP-specific information such as tax group, payment terms, and credit on hold status, their contacts, addresses, phone numbers, and...