Affiliation conflicts in data processing agreements (DPA)
Affiliation conflicts in DPAs arise when a contract applies to different organizations (controller and processor) at the same time, because a DPA always relates to one contracting organization. To avoid conflicts, the contract should be created separately for both organizations. The "All my organizations" button allows you to bypass the conflict temporarily.
When recording data processing agreements (DPA), affiliation conflicts can occur if a contract is assigned both to one organization as the controller and to another company as the processor. For legal reasons, data processing agreements always relate to one specific contracting organization (contractual partner 1).
The system reports a conflict when an attempt is made to edit a DPA that was created for an organization other than the selected one. To avoid this conflict, the DPA must be created separately for both organizations (controller and processor).
Alternatively, you can use the All my organizations button at the top right to switch to the respective matching organization in order to bypass the conflict. However, this is only a temporary solution, since access is then not exclusively limited to one organization.
To permanently restrict access to the DPA, the permission should only exist for one organization, while the DPA is created separately for both organizations.
Changes and errors may occur. The information in this article has been carefully compiled, but does not claim to be complete or correct.