Implementing General Data Protection Regulations in your Dynamics 365 for Customer Engagement portals
The General Data Protection Regulation (GDPR) is a legal act of the European Union (EU), which protects data for all individuals within the EU. With GDPR, people can control the use of their personal data in Dynamics 365 for Customer Engagement.
As an administrator, you can configure your portal to meet GDPR standards. For example, minors must have parental consent to use the portal. You can also establish terms and conditions for people who use your portal. Users must agree to the terms and conditions to use the portal.
GDPR allows you to obtain consent from portal users about the use of their personal data, identify minor users, and get parental consent for minors.
The Last Successful Sign-in field in the portal contact record shows when a portal user has last logged in. This date is picked up by a Dynamics 365 for Customer Engagement audit of the contact record and makes that information available in the standard audit stream. This allows the administrator to see inactive community members and delete their records.
The login tracking feature has been deprecated. It is recommended to use an analytics technology like Azure Application Insights to capture this kind of information. To see the list of deprecated features, click here.
Identifying minor portal users and obtaining parental consent
Regulations for identifying minors vary by country/region. Because a minor can only access the portal with parental consent, you can configure the portal to identify minors using these fields in the portal contact record:
Is Minor: Indicates that the contact is considered a minor in their jurisdiction. By default, No is selected.
Is Minor with Parental Consent: Indicates that the contact is considered a minor in their jurisdiction and has parental consent. By default, No is selected.
The following site settings control the use of portals by minors and minors without parental consent:
|Authentication/Registration/DenyMinors||Denies use of the portal by minors. By default, it is set to false.|
|Authentication/Registration/DenyMinorsWithoutParentalConsent||Denies use of the portal by minors without parental consent. By default, it is set to false.|
If a portal user is determined to be a minor and the portal is configured to block minors, an appropriate message appears and content is not shown.
If a portal user is determined to be a minor without parental consent, and the portal is configured to block minors without parental consent, an appropriate message appears and content is not shown.
The following content snippets control messages that appear when the portal is used by minors and minors without parental consent. You can change the message according to your requirements.
|Account/Signin/MinorNotAllowedCopy||HTML||The use of this portal is not suitable for use by minors and is not allowed.|
|Account/Signin/MinorWithoutParentalConsentNotAllowedCopy||HTML||The use of this portal by minors requires parental consent.|
When someone registers using an external provider and the portal is configured to block minors or minors without parental consent, the contact record is not created and the user is not authenticated.
Agreeing to terms and conditions
According to the GDPR, portal users must agree to the terms and conditions to allow marketing, profiling, or access to private information. As an administrator, you can publish your own terms and conditions to get consent of the portal user before they are authenticated to the site.
The following content snippets control the display of terms and conditions on the screen. You can change the text according to your requirements.
|Account/Signin/TermsAndConditionsHeading||Text||Terms and Conditions|
|Account/Signin/TermsAndConditionsAgreementText||Text||I agree to these terms and conditions|
Account/Signin/TermsAndConditionsCopy content snippet is empty by default. A portal administrator must enter the terms and conditions in this content snippet.
The following site settings control the terms publication date and whether the terms should be displayed on the portal:
|Authentication/Registration/TermsPublicationDate||A date/time value in GMT format to represent the effective date of the current published terms and conditions. If the terms agreement is enabled, portal users that have not accepted the terms after this date will be asked to accept them the next time they sign in. If the date is not provided, and the terms agreement is enabled, the terms will be presented every time portal users sign in.
Note: If you want a portal user to agree to the terms and conditions every time they sign in, do not provide a value for this site setting.
|Authentication/Registration/TermsAgreementEnabled||A true or false value. If set to true, the portal will display the terms and conditions of the site. Users must agree to the terms and conditions before they are considered authenticated and can use the site. By default, it is set to false.|
The following field is added in the portal contact record to store the date and time a portal user agreed to the terms and conditions:
Portal Terms Agreement Date: Indicates the date and time that the person agreed to the portal terms and conditions.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.