You’re offline. This is a read only version of the page.
Hello, the app I'm working on has users and contacts. One or more users may belong to a team. Based on the nature of the particular business environment I work in, a contact may have the same logical role(s)/team(s) as a user in some scenarios. However, only users (not contacts) can be associated with teams and roles in CRM.
We have managed this scenario in the past by adding a "Contact Type" section to the Contact form. This section has a set of checkboxes for different roles like "Is [Role1]", "Is [Role2]", etc. Can you think of a more structured/native way to manage these associations in CRM?
*This post is locked for comments
I have the same question (0)
I decided to create a new "Contact Role" entity to store a list of the different potential roles for a Contact. I created a relationship between Contact and Contact Role to allow the selection of multiple Contact Roles for a Contact. This is a more structured approach than simply adding indicator checkboxes to the Contact form.
However, I'm wondering if "Role" is a good name for this? This association is really only used to classify a contact for different purposes. There's no related access control rules so I'm wondering if there's a better word than "Role "to describe this association? What are your thoughts?
Share
Report
All responses (
Answers (
4
