Author: |
Tecnativa, initOS GmbH, Odoo Community Association (OCA) |
License: |
AGPL-3 |
Branch: |
16.0 |
Repository: |
Change2improve/data-protection |
Dependencies: |
base,
privacy,
and
web |
Languages: |
HTML (435, 12.4%),
PO File (1708, 48.6%),
Python (727, 20.7%),
Sass (5, 0.1%),
XML (473, 13.5%),
and
reStructuredText (164, 4.7%) |
Other branches: |
11.0,
12.0,
13.0,
14.0,
and
15.0 |
Other repositories: |
AwesomeFoodCoops/odoo-production,
DITIntl/odoo-production,
ERPLibre/data-protection,
Gabinete-Digital/data-protection,
Groupe-Informatique-LaCoopSurMer/odoo-production,
Guobower/data-protection,
ITISAG-OCA/data-protection,
ITISAG/data-protection,
MathBenTech/data-protection,
NeatNerdPrime/data-protection,
OCA-MUK/data-protection,
OCA/data-protection,
OdooBulgaria/data-protection,
Otsokop/odoo-production,
SanteLibre/data-protection,
SeuMarco/data-protection,
Tecnativa/data-protection,
VisiionSolucionesTecnologicas/data-protection,
acsone/data-protection,
akretion/data-protection,
anhvu-sg/data-protection,
azmeuk/odoo-production,
cedvict/data-protection,
chetanrdhaduk/odoo-production,
daramousk/data-protection,
druidoo/FoodCoops,
dzungtran89/odoo-production,
estevebadia/odoo-production,
exosoftware/oca-data-protection,
initOS/data-protection,
isoscl/data-protection,
krunal267/odoo-production,
lachouettecoop/odoo-production,
lideritjnma/data-protection,
mszinte/odoo-production,
njeudy/data-protection,
noorealam96/data-protection,
nthnnl/odoo-production,
odoo-modules/odoo-production,
pscloud/data-protection,
sanube/data-protection,
siddharth7815/odoo-production,
suningwz/odoo-production,
supercoopbdx/odoo-production,
techultrasolutions/data-protection,
trobz/odoo-production,
and
vidtsin/odoo-production |
<h1 class="title">Privacy - Consent</h1>
<p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Production/Stable" src="https://img.shields.io/badge/maturity-Production%2FStable-green.png" /></a> <a class="reference external" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external" href="https://github.com/OCA/data-protection/tree/16.0/privacy_consent"><img alt="OCA/data-protection" src="https://img.shields.io/badge/github-OCA%2Fdata--protection-lightgray.png?logo=github" /></a> <a class="reference external" href="https://translation.odoo-community.org/projects/data-protection-16-0/data-protection-16-0-privacy_consent"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external" href="https://runbot.odoo-community.org/runbot/263/16.0"><img alt="Try me on Runbot" src="https://img.shields.io/badge/runbot-Try%20me-875A7B.png" /></a></p>
<p>This module allows the user to define a set of subjects (partners)
affected by any data processing activity, and establish
a process to ask them for consent to include them in that activity.</p>
<p>For those that need explicit consent as a lawfulness base for personal data
processing, as required by GDPR (article 6.1.a), this module provides the
needed tools to automate it.</p>
<p><strong>Table of contents</strong></p>
<div class="contents local topic" id="contents">
<ul class="simple">
<li><a class="reference internal" href="#installation" id="id1">Installation</a><ul>
<li><a class="reference internal" href="#multi-database-instances" id="id2">Multi-database instances</a></li>
</ul>
</li>
<li><a class="reference internal" href="#usage" id="id3">Usage</a></li>
<li><a class="reference internal" href="#bug-tracker" id="id4">Bug Tracker</a></li>
<li><a class="reference internal" href="#credits" id="id5">Credits</a><ul>
<li><a class="reference internal" href="#authors" id="id6">Authors</a></li>
<li><a class="reference internal" href="#contributors" id="id7">Contributors</a></li>
<li><a class="reference internal" href="#maintainers" id="id8">Maintainers</a></li>
</ul>
</li>
</ul>
</div>
<a name="installation"></a>
<h2><a class="toc-backref" href="#id1">Installation</a></h2>
<p>You may want to install, along with this module, one of OCA's
<code>mail_tracking</code> module collection, such as <code>mail_tracking_mailgun</code>, so
you can provide more undeniable proof that some consent request was sent, and
to whom.</p>
<p>However, the most important proof to provide is the answer itself (more than
the question), and this addon provides enough tooling for that.</p>
<a name="multi-database-instances"></a>
<h3><a class="toc-backref" href="#id2">Multi-database instances</a></h3>
<p>To enable multi-database support, you must load this addon as a server-wide
addon. Example command to boot Odoo:</p>
<pre>
<code>odoo-bin --load=web,privacy_consent</code>
</pre>
<a name="usage"></a>
<h2><a class="toc-backref" href="#id3">Usage</a></h2>
<p>New options for data processing activities:</p>
<ol class="arabic">
<li><p class="first">Go to <em>Privacy > Master Data > Activities</em> and create one.</p>
</li>
<li><p class="first">Give it a name, such as <em>Sending mass mailings to customers</em>.</p>
</li>
<li><p class="first">Go to tab <em>Consent</em> and choose one option in <em>Ask subjects for consent</em>:</p>
<ul class="simple">
<li><em>Manual</em> tells the activity that you will want to create and send the
consent requests manually, and only provides some helpers for you to
be able to batch-generate them.</li>
<li><em>Automatic</em> enables this module's full power: send all consent requests
to selected partners automatically, every day and under your demand.</li>
</ul>
</li>
<li><p class="first">When you do this, all the consent-related options appear. Configure them:</p>
<ul>
<li><p class="first">A smart button tells you how many consents have been generated, and lets you
access them.</p>
</li>
<li><p class="first">Choose one <em>Email template</em> to send to subjects. This email itself is what
asks for consent, and it gets recorded, to serve as a proof that it was sent.
The module provides a default template that should be good for most usage
cases; and if you create one directly from that field, some good defaults
are provided for your comfortability.</p>
</li>
<li><p class="first"><em>Subjects filter</em> defines what partners will be elegible for inclusion in
this data processing activity.</p>
</li>
<li><p class="first">You can enable <em>Accepted by default</em> if you want to assume subjects
accepted their data processing. You should possibly consult your
lawyer to use this.</p>
</li>
<li><p class="first">You can choose a <em>Server action</em> (developer mode only) that will
be executed whenever a new non-draft consent request is created,
or when its acceptance status changes.</p>
<p>This module supplies a server action by default, called
<em>Update partner's opt out</em>, that syncs the acceptance status with the
partner's <em>Elegible for mass mailings</em> option.</p>
</li>
</ul>
</li>
<li><p class="first">Click on <em>Generate consent requests</em> link to create new consent requests.</p>
<ul class="simple">
<li>If you chose <em>Manual</em> mode, all missing consent request are created as
drafts, and nothing else is done now.</li>
<li>If you chose <em>Automatic</em> mode, also those request e-mails are enqueued
and, when the mail queue is cleared, they will be set as <em>Sent</em>.</li>
</ul>
</li>
<li><p class="first">You will be presented with the list of just-created consent requests.
See below.</p>
</li>
</ol>
<p>New options for consent requests:</p>
<ol class="arabic simple">
<li>Access the consent requests by either:<ul>
<li>Generating new consent requests from a data processing activity.</li>
<li>Pressing the <em>Consents</em> smart button in a data processing activity.</li>
<li>Going to <em>Privacy > Privacy > Consents</em>.</li>
</ul>
</li>
<li>A consent will include the partner, the activity, the acceptance status,
and the request state.</li>
<li>You can manually ask for consent by pressing the button labeled as
<em>Ask for consent</em>.</li>
<li>All consent requests and responses are recorded in the mail thread below.</li>
</ol>
<a name="bug-tracker"></a>
<h2><a class="toc-backref" href="#id4">Bug Tracker</a></h2>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/data-protection/issues">GitHub Issues</a>.
In case of trouble, please check there if your issue has already been reported.
If you spotted it first, help us smashing it by providing a detailed and welcomed
<a class="reference external" href="https://github.com/OCA/data-protection/issues/new?body=module:%20privacy_consent%0Aversion:%2016.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p>
<p>Do not contact contributors directly about support or help with technical issues.</p>
<a name="credits"></a>
<h2><a class="toc-backref" href="#id5">Credits</a></h2>
<a name="authors"></a>
<h3><a class="toc-backref" href="#id6">Authors</a></h3>
<ul class="simple">
<li>Tecnativa</li>
<li>initOS GmbH</li>
</ul>
<a name="contributors"></a>
<h3><a class="toc-backref" href="#id7">Contributors</a></h3>
<ul class="simple">
<li><a class="reference external" href="https://www.tecnativa.com">Tecnativa</a>:<ul>
<li>Jairo Llopis</li>
</ul>
</li>
<li><a class="reference external" href="https://www.initos.com">initOS GmbH</a>:<ul>
<li>Florian Kantelberg</li>
</ul>
</li>
</ul>
<a name="maintainers"></a>
<h3><a class="toc-backref" href="#id8">Maintainers</a></h3>
<p>This module is maintained by the OCA.</p>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.</p>
<p>This module is part of the <a class="reference external" href="https://github.com/OCA/data-protection/tree/16.0/privacy_consent">OCA/data-protection</a> project on GitHub.</p>
<p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>