I found this interesting article written by powerobjects, i thought it would worth of sharing with my readers.
It may not be suggested to keep employees as contacts in a customer-focused implementation of Microsoft Dynamics CRM because of the perceived problem of email tracing from Outlook. When you track an email from Outlook, it will track the email against the CRM record of everybody on the email (either sender or recipients). When you have an employee as a contact in CRM, that contact record will show all the email the employee ever sent or received under Closed Activities.
Database administrators might be looking at this kind of email tracking with concern about how often the same email is being duplicated. When an email is tracked in CRM, it is NOT duplicated for each contact it is tracked against. A single email is merely ‘related’ to each contact. However, there is increased potential for duplicate records when you have employees in CRM. That is because when an employee sends and email to another employee and tracks the email, it may be tracked again when the 2nd employee receives the email.
If You MUST Track Employees in CRM
If you must track employees, there are some options for you to avoid the email tracking conflicts described above.
Option 1 – Use Contacts but Create Email Aliases
Use the contact record for employees, but create an email alias for each employee that is used only for CRM. Since CRM uses an exact match on email address in order to identify which contact to track email against, an alias will fool it. The email will not be tracked against the employee UNLESS it is Set Regarding the employee contact directly.
Option 2 – Use Users
Some organizations are uncomfortable with a single person having two records (Contact and User). To resolve this, they enter all employees (even non-Users) into CRM as users and then deactivate the users who do not need licenses. If choosing this route, employee lookups would need to be modified in order to include inactive records. This may make some tasks difficult, such as updating the employee records, either with workflow or manually. Since they are inactive, then they would be read-only.
Option 3 – Creating a Custom Entity
By creating a custom entity for employees, it gives you the flexibility to edit the records easily, but also to NOT have to create an email alias. Custom entities can be email-enabled so that email notifications can be sent manually or via workflow.
In considering how best to store employees in Microsoft Dynamics CRM, don’t forget to consider security. Determine who needs to access (view, edit, and delete) employee records, and who does not need to access. If you repurpose contacts or users for employees, you will have less control over security because your security model must support multiple uses of the same entity. By creating a custom entity for employees, you can control the rights separately.
If you like this post please click LIKE and visit my sponsors thanks !!!