Difference between revisions of "Processing Activities"
(→Privileges) |
(→Privileges) |
||
Line 45: | Line 45: | ||
''Processing activities'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users & Groups]] for more information on how to set this privilege). | ''Processing activities'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users & Groups]] for more information on how to set this privilege). | ||
− | The lifecycle of the '' | + | The lifecycle of the ''processing activity'' is managed by the roles described in the table below. ''Groups'' are pre assigned to the roles according to the ''settings'' (see [[Settings]] for more information on how to set these defaults). Initial assignments can be modified according to privileges choosing among the enabled ''groups'' (see once again [[Settings]] for more information on how to enable ''groups''). |
{| class="wikitable" | {| class="wikitable" | ||
! Role !! Description | ! Role !! Description | ||
|- | |- | ||
− | |<u>DPO Group</u> || Members of the ''group'' assigned to this role | + | |<u>DPO Group</u> || Members of the ''group'' assigned to this role have full privileges. They can: |
− | * transition | + | * transition records to any compatible status, |
− | * update | + | * update fields when possible, |
− | * update | + | * update ''data sources'' directly in record management. |
|- | |- | ||
− | |<u>Data Controller Group</u> || Members of the ''group'' assigned to this role have | + | |<u>Data Controller Group</u> || Members of the ''group'' assigned to this role have view (read) privileges. |
|- | |- | ||
− | |<u>Data Processor Group</u> || Members of the ''group'' assigned to this role have | + | |<u>Data Processor Group</u> || Members of the ''group'' assigned to this role have view (read) privileges. |
|- | |- | ||
− | |<u>Working Team</u> || Members of this ''group'' have | + | |<u>Working Team</u> || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to: |
− | * transition | + | * transition records to any compatible status, |
− | * update | + | * update fields when possible. |
|- | |- | ||
− | |<u>Audit Team</u> || Members of the ''group'' assigned to this role have | + | |<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges. |
|- | |- | ||
− | |<u>Owner</u> || This role can be assigned to a single user among members of the ''groups'' previously | + | |<u>Owner</u> || This role can be assigned to a single user among members of the ''groups'' previously described. The <u>Owner</u> has several privileges: |
− | * transition | + | * transition to any compatible status, |
− | * update | + | * update fields when possible. |
|} | |} | ||
Revision as of 13:40, 11 September 2018
Contents
Introduction to Processing Activities
Processing activities are the core of element of personal data. Many regulations require to document and assess them.
The process enables to record processing activities, to maintain them and use them for assessment or other tasks related to personal data management.
Workflow
A new processing activity can be created using the Add New functionality and choosing "New Processing Activity".
A workflow enables to move the processing activities in several statuses as shown in the following picture.
The following table explains the meaning of each status:
Status | Description |
---|---|
Default | A temporary status when the processing activity is initially created before the first save. |
Draft | A processing activity in this status is draft. |
Active | A processing activity in this status is actually executed by the organization. |
Inactive | A processing activity in this status is not executed by the organization. Either it was in the past or it will in the future. |
Cancelled | Processing activity cancelled. It is still possible to recover a processing activity from this status by enabled users. |
Information
Processing activities records information are organized in four sections:
- Identification, where identification data of the processing activity are recorded,
- Ownership & Organization, containing the assignment of the key roles enabled to manage the processing activity;
- Characteristics, with the key attributes of the processing activity;
- Information Technology, with information about the technologies used to process personal data by the processing activivty.
Detailed information on the meaning and use of every field can be found by pointing the mouse on the (i) next to each field. This will activate a tooltip with a brief description of the field.
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See How To for more information.
Privileges
Processing activities can be created by the users to whom the corresponding privilege is granted (see Users & Groups for more information on how to set this privilege).
The lifecycle of the processing activity is managed by the roles described in the table below. Groups are pre assigned to the roles according to the settings (see Settings for more information on how to set these defaults). Initial assignments can be modified according to privileges choosing among the enabled groups (see once again Settings for more information on how to enable groups).
Role | Description |
---|---|
DPO Group | Members of the group assigned to this role have full privileges. They can:
|
Data Controller Group | Members of the group assigned to this role have view (read) privileges. |
Data Processor Group | Members of the group assigned to this role have view (read) privileges. |
Working Team | Members of this group have several privileges. They can manage the entire lifecycle, being enabled to:
|
Audit Team | Members of the group assigned to this role have view (read) privileges. |
Owner | This role can be assigned to a single user among members of the groups previously described. The Owner has several privileges:
|
Warning and alerts
TBC
Reports
The list of access requests can be filtered and exported to excel format from the view Access Requests.
Related processes
Access Requests can be related to processing activities