ContactManager Data Protection Officer
A Data Protection Officer is expected to be available to handle problems with data destruction.
Therefore, in the base configuration, there is a Data Protection Officer role to which
users can be assigned. The code name for this role is data_protection_officer.
Data Protection Officer permissions
In the base configuration of ContactManager, the Data Protection Officer role has the following permissions relating to personal data destruction:
requestcontactdestructioneditobfuscatedusercontact
This role also has additional permissions to enable the user
to work with users and groups. These permissions
include groupcreate,
groupdelete,
groupedit,
usereditattrs,
usereditlang,
useredit,
usergrantroles,
userviewall,
grouptreereview,
groupreview, and
userview.
A user named DataProtection Officer with login
dpofficer, which has the Data
Protection Officer role, is available in the sample
data.
In the base configuration, ContactManager screens prevent a user from editing obfuscated user contacts if the user does not have permissions to do so. In addition, ContactManager prevents a user without the correct permissions from adding obfuscated user contacts to or removing them from groups and roles. You can create additional permissions and configure ContactManager to further limit editing of obfuscated objects.
Notifying the Data Protection Officer
The PersonalDataDestruction plugin interface provides a method that enables notification of the Data Protection Officer, notifyDataProtectionOfficer.
For example, in the base configuration, the class that implements the PersonalDataDestruction plugin interface, ABPersonalDataDestructionSafePlugin, overrides the notifyDataProtectionOfficer method. In this class, the notifyDataProtectionOfficer method logs messages to the system console if a destruction request fails.