| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1138 |
| Technical Name |
de_dsfdpiworkflow |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
| Versions | 18.0 19.0 |
DE DSFA / DPIA Workflow
Guided Datenschutz-Folgenabschätzung (DPIA, Art. 35 DSGVO) with threshold check, risk scoring and sign-off
DE DSFA / DPIA Workflow (DSGVO Art. 35)
Key Features
Data-Protection Impact Assessment (DSFA)
Data-Protection Impact Assessment (DSFA). Tracks Reference, Processing Activity, Description of Processing, Purpose, Legal Basis (Art. 6 / 9). One-click start threshold, apply threshold, submit dpo, dpo close, mark consulted.
DPIA Threshold Criterion
DPIA Threshold Criterion. Tracks Criterion, Code, Guidance, Reference.
Technical / Organisational Measure (TOM)
Technical / Organisational Measure (TOM). Tracks Measure, Code, Description, Default Measure.
DPIA Risk
DPIA Risk. Tracks Risk, Assessment, Rights / freedoms affected, Inherent Score, Mitigation Measures.
DPIA Threshold Check
DPIA Threshold Check. Tracks Processing Activity, WP248 Criteria, Muss-Liste, Result, DSFA Required. One-click create assessment.
Where a type of processing
Where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons, Art.
35 DSGVO requires the controller
35 DSGVO requires the controller to carry out a Datenschutz-Folgenabschätzung (data-protection impact assessment, DPIA) *before* the processing starts.
The German supervisory authorities publish
The German supervisory authorities publish a "Muss-Liste" of processing operations that always require a DPIA, and the WP248 nine criteria are used to decide borderline cases (two or more criteria → DPIA needed).
Use Cases
Screenshots
Assessments
Criteria
Measures Toms
Risks
Threshold Check
Why Choose This Module
a threshold check (Schwellwertanalyse) over the WP248 nine criteria plus the national Muss-Liste that tells you whether a DSFA is required at all; a structured description of the processing and its necessity/proportionality; a risk register where each risk is scored by likelihood x severity, given a mitigation, and re-scored to a residual risk; the Art. 35 Abs. 2 consultation of the data-protection officer and the Art. 36 prior-consultation flag when high residual risk remains; a formal sign-off with a locked, versionable record.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: German, English
- Author: Pokutsoft
- Dependencies: base, mail
- Support: support@pokutsoft.com
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1138 |
| Technical Name |
de_dsfdpiworkflow |
| License | OPL-1 |
| Website | https://pokutsoft.com/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module