Issues & Non Conformities - Revision history

Cbisso: /* Privileges */

2018-10-10T09:54:56Z

‎Privileges

Cbisso: /* Privileges */

2018-10-10T09:54:25Z

‎Privileges

Cbisso: /* Privileges */

2018-10-10T09:54:16Z

‎Privileges

Cbisso: /* Privileges */

2018-10-10T09:51:03Z

‎Privileges

Fbertuletti: /* Related processes */

2018-09-21T08:10:16Z

‎Related processes

Fbertuletti: /* Related processes */

2018-09-21T07:53:59Z

‎Related processes

Sottini at 21:02, 14 September 2018

2018-09-14T21:02:33Z

Sottini: /* Workflow */

2018-09-14T20:41:08Z

‎Workflow

Sottini at 20:40, 14 September 2018

2018-09-14T20:40:37Z

Sottini: /* Privileges */

2018-09-14T20:38:38Z

‎Privileges

@@ Line 62: / Line 62: @@
 * update fields when possible.
 |-
-|<u>Auditor 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>Issue / NC 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:

@@ Line 49: / Line 49: @@
 ! Role !! Description
 |-
-|<u>Data Protection Officer Group (DPO) Group</u> || Members of the ''group'' assigned to this role have full privileges. They can:
+|<u>Data Protection Officer (DPO) Group</u> || Members of the ''group'' assigned to this role have full privileges. They can:
 * transition records to any compatible status,
 * update fields when possible,

@@ Line 49: / Line 49: @@
 ! Role !! Description
 |-
-|<u>DPO Group</u> || Members of the ''group'' assigned to this role have full privileges. They can:
+|<u>Data Protection Officer Group (DPO) Group</u> || Members of the ''group'' assigned to this role have full privileges. They can:
 * transition records to any compatible status,
 * update fields when possible,
@@ Line 62: / Line 62: @@
 * update fields when possible.
 |-
-|<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
+|<u>Auditor Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 |-
 |<u>Issue / NC 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:

@@ Line 64: / Line 64: @@
 |<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 |-
-|<u>Issue / NCOwner</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>Issue / NC 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.

← Older revision		Revision as of 08:10, 21 September 2018
Line 73:		Line 73:

	== Related processes ==		== Related processes ==
−	''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'' ~~and~~ ''Privacy Impact Assessment''.	+	''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'', ''Privacy Impact Assessment'' and ''Risks''.

← Older revision		Revision as of 07:53, 21 September 2018
Line 73:		Line 73:

	== Related processes ==		== Related processes ==
−	''Issues / non conformities'' can be related to ''actions'', ''audits'' ~~and~~ ''data breaches''.	+	''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'' and ''Privacy Impact Assessment''.

@@ Line 1: / Line 1: @@
 == Introduction to Issues / Non Conformities ==
-This workflow provides the mean to manage the lifecycle of ''Issues / non conformities''. An ''issue'' or a ''non conformity'' are different categorization of records but are managed in the same way by the same workflow.
+This workflow provides the mean to manage the lifecycle of ''issues / non conformities''. An ''issue'' or a ''non conformity'' are different categorization of records but are managed in the same way by the same workflow.
 == Workflow ==

← Older revision		Revision as of 20:41, 14 September 2018
Line 8:		Line 8:
	The workflow enables to move ''issues / non conformities'' in several statuses as shown in the following picture.		The workflow enables to move ''issues / non conformities'' in several statuses as shown in the following picture.

−	[[File:Issues_non_Conformities_Workflow_ENG_v1.0.JPG\|centre\|thumb\|800x800px\|~~Access Requests~~ workflow and statuses.]]	+	[[File:Issues_non_Conformities_Workflow_ENG_v1.0.JPG\|centre\|thumb\|800x800px\|Issues / non conformities workflow and statuses.]]

@@ Line 68: / Line 68: @@
 * 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 ''issues / non conformities'' can be filtered and exported to excel format from the ''view'' '''''Issues / Non Conformities'''''.
 == Related processes ==
-''Access Requests'' can be related to ''processing activities''.
+''Issues / non conformities'' can be related to ''actions'', ''audits'' and ''data breaches''.

@@ Line 42: / Line 42: @@
 == 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).
+''Issue / non conformity'' 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 ''issue / non conformity'' 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 64: / Line 64: @@
 |<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>Issue / NCOwner</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.