Privacy Impact Assessments - Revision history

Cbisso: /* Privileges */

2018-10-10T10:44:40Z

‎Privileges

Sottini: /* Workflow */

2018-09-12T14:48:13Z

‎Workflow

Sottini: /* Information */

2018-09-12T06:49:35Z

‎Information

Sottini at 21:32, 11 September 2018

2018-09-11T21:32:33Z

Sottini: /* Privileges */

2018-09-11T21:07:42Z

‎Privileges

Sottini: /* Information */

2018-09-11T20:35:01Z

‎Information

Sottini: /* Workflow */

2018-09-11T20:30:48Z

‎Workflow

Sottini: /* Workflow */

2018-09-11T20:25:52Z

‎Workflow

Sottini: /* Workflow */

2018-09-11T20:23:24Z

‎Workflow

Sottini: /* Workflow */

2018-09-11T20:23:09Z

‎Workflow

@@ Line 65: / Line 65: @@
 * update fields when possible.
 |-
-|<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
+|<u>Auditors Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 |-
 |<u>PIA 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:

← Older revision		Revision as of 14:48, 12 September 2018
Line 10:		Line 10:
	A workflow enables to move the ''Privacy Impact Assessment" in several statuses as shown in the following picture.		A workflow enables to move the ''Privacy Impact Assessment" in several statuses as shown in the following picture.

−	[[File: Privacy_Impact_Assessment_workflow_ENG_v1.0.JPG\|centre\|thumb\|800x800px\|~~Access Requests~~ workflow and statuses.]]	+	[[File: Privacy_Impact_Assessment_workflow_ENG_v1.0.JPG\|centre\|thumb\|800x800px\|Privacy Impact Assessments workflow and statuses.]]

@@ Line 33: / Line 33: @@
 == Information ==
-''Privacy Impact Assessment'' records information are organized in four sections:
+''Privacy Impact Assessment'' records are organized in four sections:
 * <u>''Identification''</u>, where identification data of the ''Privacy Impact Assessment'' are recorded,

@@ Line 71: / Line 71: @@
 * update fields when possible.
 |}
 == Reports ==
-The list of ''access requests'' can be filtered and exported to excel format from the ''view'' '''''Access Requests'''''.
+The list of ''Privacy Impact Assessments'' can be filtered and exported to excel format from the ''view'' '''''Privacy Impact Assessments'''''.
 == Related processes ==
-''Access Requests'' can be related to ''processing activities''.
+''Privacy Impact Assessments'' can be related to ''processing activities'', ''risks'' and ''issues / non conformities''.

@@ Line 45: / Line 45: @@
 == Privileges ==
-''Access request'' 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).
+''Privacy Impact Assessments'' 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 ''access request'' 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'').
+The lifecycle of the ''Privacy Impact Assessment'' 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"
@@ Line 61: / Line 61: @@
 |<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 several privileges. They can manage the entire lifecycle, being enabled to:
+|<u>Assessment Team</u> || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:
 * transition records to any compatible status,
 * update fields when possible.
@@ Line 67: / Line 67: @@
 |<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 described. The <u>Owner</u> has several privileges:
+|<u>PIA 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 to any compatible status,
 * update fields when possible.

@@ Line 33: / Line 33: @@
 == Information ==
-''Access request'' records information are organized in four sections:
+''Privacy Impact Assessment'' records information are organized in four sections:
-* <u>''Identification''</u>, where identification data of the ''access request'' are recorded,
+* <u>''Identification''</u>, where identification data of the ''Privacy Impact Assessment'' are recorded,
-* <u>''Ownership & Organization''</u>, containing the assignment of the key roles enabled to manage the ''access request'';
+* <u>''Ownership & Organization''</u>, containing the assignment of the key roles enabled to manage the ''Privacy Impact Assessment'';
-* <u>''Access Request Details''</u>, with the details of the ''access request'';
+* <u>''Risk Assessment Questions''</u>, containing the preliminary assessment questions;
-* <u>''Data Subject Details''</u>, with the details of the ''data subject'' issuing the ''access request'';
+* <u>''Impact Assessment Questions''</u>, if any significant risk is found in the <u>''Risk Assessment Questions''</u> section, it contains detailed impact assessment questions (''DPIA'');
 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.

@@ Line 22: / Line 22: @@
 |Opened || A ''Privacy Impact Assessment'' in this status is draft.
 |-
-|Detailed Assessment || An ''access request'' in this status is confirmed and it is waiting to be actioned.
+|Detailed Assessment || This status means that a detailed assessment needs to be executed. If a significant risk is found during the preliminary assessment, the transition through this status is required before closing the ''Privacy Impact Assessment''.
 |-
-|Suspended || Activities concerning the ''access request'' are temporarily suspended, meaning no further status transitions are allowed.
+|Suspended || Activities concerning the ''Privacy Impact Assessment'' are temporarily suspended.
 |-
-|Closed || In this status, all activities related to the ''access request'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
+|Closed || In this status, the assessment is completed.
 |-
-|Cancelled || ''Access request'' cancelled. This is an end of life status.
+|Cancelled || ''Privacy Impact Assessment'' cancelled. This is an end of life status.
 |-
 |}

@@ Line 8: / Line 8: @@
 A new ''Privacy Impact Assessment'' can be created using the '''Add New''' functionality and choosing "New Privacy Impact Assessment".
-A workflow enables to move the ''access request" in several statuses as shown in the following picture.
+A workflow enables to move the ''Privacy Impact Assessment" in several statuses as shown in the following picture.
 [[File: Privacy_Impact_Assessment_workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Access Requests workflow and statuses.]]
@@ Line 18: / Line 18: @@
 ! Status !! Description
 |-
-|Default || A temporary status when the ''access request'' is initially created before the first save
+|Default || A temporary status when the ''Privacy Impact Assessment'' is initially created before the first save.
 |-
-|Opened || An ''access request'' in this status is draft and it is not actioned.
+|Opened || A ''Privacy Impact Assessment'' in this status is draft.
 |-
-|Requested || An ''access request'' in this status is confirmed and it is waiting to be actioned.
+|Detailed Assessment || An ''access request'' in this status is confirmed and it is waiting to be actioned.
 |-
 |Suspended || Activities concerning the ''access request'' are temporarily suspended, meaning no further status transitions are allowed.
 |-
 |Closed || In this status, all activities related to the ''access request'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
 |-
 |}

← Older revision		Revision as of 20:23, 11 September 2018
Line 10:		Line 10:
	A workflow enables to move the ''access request" in several statuses as shown in the following picture.		A workflow enables to move the ''access request" in several statuses as shown in the following picture.

−	[[File: ~~Privacy_ImpactAssessment_workflow_ENG_v1~~.0.JPG\|centre\|thumb\|800x800px\|Access Requests workflow and statuses.]]	+	[[File: Privacy_Impact_Assessment_workflow_ENG_v1.0.JPG\|centre\|thumb\|800x800px\|Access Requests workflow and statuses.]]