SAP Customer Consent provides robust version control to manage consent statements, ensuring users always have valid consent based on the current terms and conditions. This is crucial for maintaining compliance with data privacy regulations.
SAP Customer Consent allows you to version your consent statements either by Number or Date and input the appropriate dates or version for the consent.
Once you save the new statement, you cannot change this definition.
A re-consent cut-off should be added with any significant consent change that requires existing users to re-consent.
Validating the User's Consent Status
Consent management includes a built-in mechanism for ensuring that users who log in to your site have a valid consent in place for the relevant mandatory statements:
New User Registration: A new user registers on your site but does not agree to the terms of service. The user will not be able to submit the registration screen.
Existing Users Without Consent: A user registered on your site before the consent module was implemented and has no valid consent statements associated with their account. The next time they log in, the Registration Completion screen will be displayed, requesting the relevant agreements.
Consent Statement Updates: A user has agreed to your site consent statements and is still logged in, but the site admins have changed the version of one of the consent statements. The Registration Completion screen will be displayed during their logged-in session, requesting their re-consent.
To ensure these scenarios function correctly, you must include the relevant consent statements on all registration and registration completion screens and set a value to the verifyLoginInterval parameter in the WebSDK Configuration. This parameter dictates how often the system checks for updated consent requirements.
Updating Consent Statement Versions
The consent management tool gives you the option to update the version of the consent statement that is currently in effect and set a required date for consent renewal.
Minor Changes: For minor changes that don't require existing users to re-consent, create a new version by increasing ONLY the Version field value in the consent management dashboard.
Significant Changes: For significant changes that require existing users to re-consent, increase both the Version field and the Re-consent cut-off field values. This means that users who consent to a version earlier than the number or date specified under the Re-consent cut-off are presented with a Registration Completion screen and will be required to re-consent. Users who choose not to consent will not be able to access the areas or features of your site that are available only to fully registered users.
For more information, refer to the Version Control documentation in the SAP Help Portal.
Managing Consent Versions
The user interface provides clear visual cues for managing consent versions:
Editing: To edit a consent version for a locale, choose the Edit icon or choose the link in the locale name. A new page opens where you can see all consent versions for this locale and their information.
Status Indicators: A green icon in the Status column indicates the currently published version.
Version Types: You can have draft versions that you can further edit or delete but are inaccessible for end users and archived versions, which are previously published versions that were overwritten by other published versions.
Actions: The Actions column allows you to edit, publish, or delete a specific draft version or duplicate any of the versions in the table to create a new version based on this version.
Note
Once a locale version has been published, it cannot be deleted. The only action available for a published or previously published version is Duplicate.
For more information, refer to the Creating and Managing Consent Statements documentation in the SAP Help Portal.