Management of consent templates
Management of consent templates
“Consent of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her."
(European Data Protection Regulation Article 4, 11)
The consent template configuration module offers your organisation the possibility of customising as much as possible the consent collection forms displayed in the user journeys, so that they fit into your environment, while respecting the recommendations of the French Data Protection Agency (CNIL) (Integration of the name of the data controller, the processing purposes, the retention period, the name of the recipient of the data, and the contact details of the service to contact to assert rights).
This customisation includes: content, titles, graphic charter and multilingualism.
The organisation can create as many consent collection form templates as needed, depending on the customer journey.
Contents of this documentation:
- 1 The consent template creation wizard
- 2 Lifecycle of a consent template
- 2.1 Viewing existing consent templates
- 2.2 Creating a template
- 2.3 Modifying an existing template
- 2.4 The role of labels
- 2.5 The role of aliases
- 2.6 The visibility of a template
- 2.7 Customising the style
- 2.8 Customising the titles of sections
- 2.9 Translation management
- 2.10 Activating a consent template
- 2.11 Deleting a consent template
- 2.12 Deactivating a consent template
- 3 Consent form and emails
- 4 Example - Tutorial (Step 1)
- 5 To find out more
The consent template creation wizard
The different fields are distributed in several sections.
Only the Footer, Other parameters, Label edition and CSS Styles sections are optional.
The other sections are necessary to comply with legal requirements and are therefore mandatory:
"Application provision";
"rocessing operations";
"Data controller";
mandatory fields are shown in bold, fields available in multilingual format are shown in italics.
"Information" section
Field name | Description | Example |
Template name | Corresponds to the name of the form template internal to your organisation. This name will not be displayed to the end user. | Marketing (test) |
Template language(s) | Corresponds to the different languages of the form (possibility to make a multilingual form). | French, English, Chinese, etc. |
Alias | Optional name for calling the consent API. It allows you to manage the replacement of one template by another, without having to modify all the calls to the template. Find out more. |
|
Labels | Used to categorise consent templates in order to filter them and therefore find a template more quickly. |
|
Visibility | Used to define the scope of access to the template. Find out more. | Private |
Consent email template to use | For using the "Send consent email" feature. Allows you to link a consent email template to a consent template. Find out more. (see step 2 of the tutorial by here) |
|
"Titles and application provisions" section
Field name | Description | Example |
Main title (Language) | Corresponds to the title of the form that will be displayed to the end user. | Collection of consent |
Title for provisions | Corresponds to the title of the insert dedicated to the application provisions. | Application provisions |
Application provisions | Corresponds to the content of the insert dedicated to the application provisions. |
|
"Processing operations" section
Insert name | Field name | Description | Example |
Data related to processing operations | Subtitle "Data related to processing operations" | Corresponds to the title of the section that must explain to the end user which of their data will be used for this processing. | What data do we use? |
| Description of Data related to processing operations | Corresponds to the description (in accordance with the principles of the GDPR) of the data used in the context of the processing. | free text |
Retention period The insert will appear in the form if and only if both fields of the insert are completed | Subtitle "Retention period" | Corresponds to the title of the section that must explain to the end user how long their data will be kept after processing. | For how long do we keep data? |
Description of the retention period | Corresponds to the description (in accordance with the principles of the GDPR) of the data retention period in relation to this processing. |
| |
Purpose(s) | Subtitle "Purpose" | Corresponds to the title of the section that must explain to the end user the purpose(s) for which their data will be used in the context of this processing. | What do we do with it? |
Subtitle "Sharing data with a third party" | Corresponds to the title of the corresponding section. Only displayed if data is shared with a third party (see Basis of consent), mandatory in this case.§ | For this purpose, this data will be transmitted to: | |
Description of purpose No. 1 | Corresponds to the description (in accordance with the principles of the GDPR) of the purpose of the use of data in relation to this processing. |
| |
Basis of consent for purpose No. 1 |
| Marketing, Main Service, Enhanced Service, Research and Third party sharing | |
References of associated processing operations |
|
"Data controller" section
Field name | Description | Example |
Name | Name of the data controller. |
|
Telephone number | Telephone number of the data controller. |
|
Email address | Email address of the data controller. |
|
Address | Postal address of the data controller. |
|
"Data controller" letterhead | Corresponds to an introductory section placed at the beginning of the paragraph devoted to the data controller. |
|
"Data controller" footer | Corresponds to a concluding section on the data controller placed at the end of the paragraph devoted to the data controller. |
|
"Validation button and footer" section
Field name | Description | Example |
Validation button label | Corresponds to the text that will be entered on the validation button in the consent form. | Submit |
Footer title | Corresponds to the footer title. |
|
Footer description | Corresponds to the content of the footer. |
|
"Other parameters" section
Field name | Description | Example |
Page title | Corresponds to the title of the tab displayed in the browser on opening the consent form. | free text (by default, the field will be pre-filled: Collection of consent) |
Display an "Accept all" box | Checkbox to display an "Accept All" box on the form. |
|
Text for the "Accept All" box | Corresponds to the wording of the box allowing to accept all processing operations of a form (whether one or more). | Accept all |
"CSS style" section
Template elements that can be customised
Section/ Element | Name of the CSS class | Position modifiable? |
Title | .fsc-global-title |
|
Provisions | .fsc-dispositions.fsc-wrapper |
|
Data controller | .fsc-data-controller.fsc-wrapper |
|
Accept all | .fsc-accept-all.fsc-wrapper |
|
Processing operations
| .fsc-entries.fsc-wrapper
| |
Validate | .fsc-submit | |
Footer | .fsc-footer.fsc-wrapper |
|
A few examples
application of a style to the main title of the form
.fsc-global-title {
border-bottom: 10px solid #2E64FE;
margin-bottom: 40px;
text-shadow: 4px 4px 30px;
font-size: 36px;
font-variant: small-caps
}
hide the action button on the receipt
.fsc-receipt-actions { display: none }
change the colour of the "submit" button
.fsc-submit button {
background-color: rgb(6,219,171) !important;
border-color: #FFAA00 !important;
}
change the order of the "data" and "purpose" fields
Lifecycle of a consent template
Viewing existing consent templates
Click Right Consents> Configuration > Consent forms;
If necessary, use the filters to refine your search;
Creating a template
Click Right Consents> Configuration > Consent forms;
Click New template;
Customise the template;
Once the name of the template has been entered, you can save it at any time by clicking "Save"
Modifying an existing template
Access the templates by clicking Right Consents> Configuration > Consent Forms;
On the line of the template to be modified, click , then Edit;
Customise the template;
To save the changes, click "Save";
The role of labels
Labels are used to categorise consent templates in order to filter them and thus find a template more quickly.
In the template Information section, go to the Labels field;
A list with the labels already saved is proposed. Enter characters to filter the list, and then select the label;
Or enter a new label and validate the entry using the Enter key;
To delete labels from a template:
In the template Information section, click the cross to remove the label;
The role of aliases
The template alias is an optional name used when calling the Consent API.
Each alias can point to several templates, but only one of these templates can be active.
Use case: management of the replacement of one template by another, without having to modify all the calls to the template.
The visibility of a template
The visibility of the template is used to define the scope of access to the template:
Public: the template can be called by any organisation;
Private: access to the template is only authorised for the organisation;
Restricted: Access is restricted to a defined list of profiles;
Customising the style
Your consent form can be given a style in line with your organisation's graphic charter.
In the CSS Style section, define the style of the style of the different tags, insert icons, etc.;
Click to preview the resulting form;
Save;
Customising the titles of sections
Each title of the form can be customised. Go to the Label edition section
Translation management
In the template Information section, select the desired languages. For each of the languages chosen, complete the text in the language indicated.
To hide/display only certain languages, click Form editing options.
Then select the desired display languages for editing the template.
Activating a consent template
In the list of templates, click Edit or click on the template label;
If necessary, complete at least the required elements marked with a red icon;
Click Activate;
Deleting a consent template
In the list of templates, click Edit or click on the template label;
Click Delete;
Deactivating a consent template
In the list of templates, click Edit or click on the template label;
If necessary, complete at least the required elements marked with a red icon;
Click Activate;
Consent form and emails
Once consent has been obtained, an email summarising the consent given can be sent to the data subject so that they can consult and possibly modify it.
See how to define a consent email template here.
Linking an email template to a consent form
Click on form templates;
Select the template to associate with the consent email template, click Action>Edit;
In the Consent email template choice list, select the email template to be used;
Click Save;
How to send an email after collecting consent
Generate the collection Link from a template;
Fill in the collection parameters:
the identifier of the user concerned by the consent;
the consent email: the address to which the email confirming the collection will be sent;
Validate to display the consent collection form;
Validate the form;
Example - Tutorial (Step 1)
Let's create a consent template called "Marketing (example)", which will serve as the first step in our tutorial on the Right Consents product.
To do this, go to the "Configuration" part of the menu on the left, and click on "Consent form". From there, click on "New templates" at the top left of the screen.
This takes you to the page for creating a new consent template. It is materialised as follows:
Once the name of the template has been entered, you can save it at any time by clicking "Save". At this stage, the template is in draft form.
As you can see, a consent template consists of the following sections: Information, Titles and application provisions, Processing operations - there is a basic one to be completed but you can add others - , Data controller, Validation button and footer, Other parameters, CSS style.
Let's start filling in the template fields. At any time, in the lower right part of your screen, you can have a preview of the consent template.
For the "Information" section, the fields to be completed are as follows:
Once this section has been completed with the necessary information, click "Next".
For the "Titles and application provisions" section, there is a block of fields to be completed per language defined in the previous section. The fields to be completed per block are as follows:
Once this section has been completed with the necessary information, click "Next".
For the "Processing operations" section, and in particular at the beginning "Processing operation No. 1", the fields to be completed are the following:
Once this section has been completed with the necessary information, click "Next".
For the "Data controller" section, the fields to be completed are as follows:
Once this section has been completed with the necessary information, click "Next".
For the "Validation button and footer" section, the fields to be completed are as follows:
Once this section has been completed with the necessary information, click "Next".
For the "Other parameters" section, which is entirely optional, the fields to be completed are as follows:
Once this section has been completed with the necessary information, click "Next".
For the "CSS Style" section, which is entirely optional, simply insert a CSS style sheet to match your graphic charter. For example:
There we have it, together we have created a consent template!
Once you have entered all the information, you can save the template and then activate it. To be able to activate a template, you must make sure that all the mandatory information on the form has been completed (the icons to the right of each section title must be grey). If this is not the case (one or more icons to the right of the section titles is/are red), you must return to the section to modify or complete the information provided.
After activation, you can generate a consent collection link (enter any identifier):
and post submission: