...
Info |
---|
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
| 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.
| 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 |
|
Info |
---|
It is possible to add several purposes to the same processing operation, but it is also possible to add several processing operations to the same consent template. |
"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. |
Info |
---|
If the name / telephone number / email address / address are already entered in the organisation configuration, they are pre-filled with this value. |
"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
| .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
hide the action button on the receipt
change the colour of the "submit" button
...
Code Block |
---|
.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
Code Block |
---|
.fsc-receipt-actions { display: none } |
change the colour of the "submit" button
Code Block |
---|
.fsc-submit button {
background-color: rgb(6,219,171) !important;
border-color: #FFAA00 !important;
} |
...
change the order of the "data" and "purpose" fields
Code Block |
---|
.fsc-entry-data { order: 2; }
.fsc-entry-retention { order: 3; }
.fsc-entry-usage { order: 1; }
.fsc-entry-data-controller { order: 4; } |
Lifecycle of a consent 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"
Info |
---|
At this stage, the template is in draft form. |
Modifying an existing template
Note |
---|
Before modification, make sure that the template is in draft status: an active template can no longer be modified, in order to be able to guarantee the integrity and validity of the consents collected. The only modification allowed is the addition or removal of labels / aliases / email template / visibility. If the template needs to evolve, it will have to be duplicated to create a new 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";
Info |
---|
Editing a template is subject to authorisation; remember to check your authorisations with your administrator |
The role of labels
Labels are used to categorise consent templates in order to filter them and thus find a template more quickly.
Info |
---|
Labels are optional. |
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;
...
In the template Information section, click the cross to remove the label;
Note |
---|
Labels are defined for a template and not for the template language |
The role of aliases
The template alias is an optional name used when calling the Consent API.
...
Use case: management of the replacement of one template by another, without having to modify all the calls to the template.
Info |
---|
The alias can be changed even when the template is active. |
The visibility of a 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;
Info |
---|
Visibility can be changed even when the template is active. |
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;
...
Then select the desired display languages for editing the template.
Note |
---|
When several languages are chosen, filling in a field, even an optional field, makes it necessary to fill in all the languages. |
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;
Note |
---|
Once activated, a template can no longer be edited. |
Deleting a consent template
In the list of templates, click Edit or click on the template label;
Click Delete;
Note |
---|
Only a "Draft" model can be deleted. Once activated, all templates are kept for as proof of enforceability. |
Deactivating a consent template
...
See how to define a consent email template here.
Note |
---|
The creation, activation, deactivation, etc. functionalities are subject to authorisation; remember to check your authorisations with your administrator |
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;
Info |
---|
An email template can be associated with a form template even after the form has been activated. |
Note |
---|
Editing the template is subject to authorisation; remember to check your authorisations with your administrator. |
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;
...
For the "Information" section, the fields to be completed are as follows:
Template name: Marriage
Template language(s): French
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:
Main title: Fancy going out to eat?
Title for provisions: I'm hungry, aren't you?
Application provisions: I suggest that we go out for a nice meal, that's good, I know a 🇮🇹 place that's not very far away, plus today they've got arancini on the menu.
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:
Data related to the processing operation / Subtitle "Data related to the processing operation": However, I need your 📱
Data related to the processing operation / Description of the data related to the processing operation: Unless I'm wrong, you never gave it to me.
Purpose(s) / Subtitle "Purpose": I can use it in the following cases:
Purpose(s) / Subtitle "Third party data sharing": I will send it to:
Purpose(s) / Purpose No. 1: to call you
Purpose(s) / Basis of consent of purpose No. 1: Main service
Purpose(s) / Purpose No. 2: to give it to a friend
Purpose(s) / Basis of consent of purpose No. 2: Third party sharing
Purpose(s) / Purpose No. 2 / Third party No. 1 / Name of the company: Jules-de-chez-Smith-en-face
Purpose(s) / Purpose No. 2 / Third party No. 1 / Description: The guy who lives across the street
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:
Surname: Guy Michu
Telephone number: 0123456789
Email address: guy.michu@exemple.com
Address: 11 rempart saint Thiebault 57000 METZ
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:
Validation button label: Let's go for that
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:
Page title: fancy going out to eat?
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:
.fsc-global-title {
border-bottom: 10px solid #2E64FE;
margin-bottom: 40px;
text-shadow: 4px 4px 30px;
font-size: 36px;
font-variant: small-caps
}
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.
Info |
---|
Once activated, a template can no longer be edited. |
After activation, you can generate a consent collection link (enter any identifier):
...