...
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
...
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.
...
After activation, you can generate a consent collection link (enter any identifier):
and post submission:
To find out more
...
...
...
...
...