Greeting's Dynamics Community,
My organization is new to the Dynamic 365 CRM Platform. We are currently migrating from CiviCRM over to Dynamics 365 Customer Engagement. We currently use the system to manage students that participate in our program to donors and parents. In our current system, we can grant permission to parents to update their student's contact information and view other details via the portal. This permission is assigned based on the relationship to the student. I've attached a screenshot of the current system. My question is, how can we achieve the same thing in dynamics 365? I know that we can assign each contact record to each other using the connections feature, but does this allow us to assign permission in the 365 portal for them to update and submit certain information. I read through some blogs and saw that households could be a possibility at achieving this but not sure if we want to go down the household route. Our current system had the household feature, but we elected to go the relationship/connection route. Any advice that can be given will to truly appreciated.
President and Chair of the Board of Trustees
Hello Christian C,
Achieving his through connections wont be such a good idea as it will not apply desired secuity you are looking for. CRM Portal honors Dynamics CRM security model by default and hence I would suggest you search bit more on Manager Hierarchy or Position Hierarchy which are extensions of security models that use business units, security roles, sharing, and teams.
Please go through this link for better understand the concept. More details here:
Hope this helps,
The short answer is yes, Dynamics Portals has entity permission system, which allow you to grant edit/view/create permission to the contact based on existing relationship/connections to target entities. You can start Here and read especially carefully about Parent Permissions model.There can be some complexities, let's imagine you are using one "connection" entity to connect all entities with others, and you can identify the nature of the connection only by attribute like "Connection Role". This is not possible to implement permission system based on the attribute value with OOB functionality.But you can overcome this by using liquid templates to check security at the portal (and as part of liquid you can verify if current contact has access to the record with FETCHXML).
If you have ability to build relationship model like student-parent, student-donor as different relationships, it will help a lot to quickly build permission system at the Portals with out of the box functionality. But once again - even if you cannot change the relationship system - it is always possible to build proper security model at the Dynamics Portals.
Will be glad to help with more specific questions.Thanks, Dmytro.
Business Applications communities