Audits - Revision history

Cbisso: /* Privileges */

2018-09-28T15:24:31Z

‎Privileges

Sottini at 19:59, 12 September 2018

2018-09-12T19:59:42Z

Sottini: /* Privileges */

2018-09-12T19:57:00Z

‎Privileges

Sottini: /* Information */

2018-09-12T19:55:26Z

‎Information

Sottini: /* Workflow */

2018-09-12T14:53:13Z

‎Workflow

Sottini: /* Workflow */

2018-09-12T14:52:22Z

‎Workflow

Sottini: /* Workflow */

2018-09-12T14:51:03Z

‎Workflow

Sottini: /* Workflow */

2018-09-12T14:49:24Z

‎Workflow

Sottini: /* Workflow */

2018-09-12T14:47:23Z

‎Workflow

Sottini: /* Workflow */

2018-09-12T14:46:56Z

‎Workflow

@@ Line 67: / Line 67: @@
 * update fields when possible.
 |-
-|<u>Supervisory Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
+|<u>Auditors Supervisory Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 |-
 |}

@@ Line 70: / Line 70: @@
 |-
 |}
 == Reports ==
-The list of ''access requests'' can be filtered and exported to excel format from the ''view'' '''''Access Requests'''''.
+The list of ''audits'' can be filtered and exported to excel format from the ''view'' '''''audits'''''.
 == Related processes ==
-''Access Requests'' can be related to ''processing activities''.
+''Audits'' can be related to ''risks'' and ''issues / non conformities''.

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

@@ Line 35: / Line 35: @@
 == Information ==
-''Access request'' records are organized in five sections:
+''Audit'' records 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 ''audit'' 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 ''audit'';
-* <u>''Access Request Details''</u>, with the details of the ''access request'';
+* <u>''Details''</u>, with the details of the ''audit'' to accomplish;
-* <u>''Data Subject Details''</u>, with the details of the ''data subject'' issuing the ''access request'';
+* <u>''Results''</u>, with the conclusions of the ''audit''.
 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 29: / Line 29: @@
 |-
 |Closed || In this status, all activities related to the ''audit'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
 |-
 |}

@@ Line 22: / Line 22: @@
 |Opened || An ''audit'' in this status is draft and it is not actioned yet.
 |-
-|Planned || An ''audit'' in this status is ready for execution.
+|Planned || An ''audit'' in this status is planned for execution.
 |-
-|In progress || In this status, the ''access request'' has been taken in charge and it is being actioned.
+|In progress || In this status, the ''audit'' is in progress.
 |-
-|Cancelled || ''Access request'' cancelled. This is an end of life status.
+|Completed || In this status, all activities related to the ''audit'' were completed and closure is expected after confirmation.
 |-
-|Completed || In this status, all activities related to the ''access request'' were completed and closure is expected after confirmation.
+|Closed || In this status, all activities related to the ''audit'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.
 |-
 |}

@@ Line 20: / Line 20: @@
 |Default || A temporary status when the ''audit'' is initially created before the first save.
 |-
-|Opened || An ''access request'' in this status is draft and it is not actioned.
+|Opened || An ''audit'' in this status is draft and it is not actioned yet.
 |-
-|Requested || An ''access request'' in this status is confirmed and it is waiting to be actioned.
+|Planned || An ''audit'' in this status is ready for execution.
 |-
-|In charge || In this status, the ''access request'' has been taken in charge and it is being actioned.
+|In progress || In this status, the ''access request'' has been taken in charge and it is being actioned.
 |-
 |Cancelled || ''Access request'' cancelled. This is an end of life status.
 |-
 |Completed || In this status, all activities related to the ''access request'' were completed and closure is expected after confirmation.
 |-
 |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.

@@ 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 ''audit'' is initially created before the first save.
 |-
 |Opened || An ''access request'' in this status is draft and it is not actioned.

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

−	[[File:~~Audits_Workflow_ENG v1~~.0.JPG\|centre\|thumb\|800x800px\|Audits workflow and statuses.]]	+	[[File:Audits_Workflow_ENG_v1.0.JPG\|centre\|thumb\|800x800px\|Audits workflow and statuses.]]

@@ Line 6: / Line 6: @@
 == Workflow ==
-A new ''access request'' can be created using the '''Add New''' functionality and choosing "New Access Request".
+A new ''audit'' can be created using the '''Add New''' functionality and choosing "New Audit".
-A workflow enables to move ''access requests" in several statuses as shown in the following picture.
+A workflow enables to move ''audits" in several statuses as shown in the following picture.
-[[File:Access_Requests_Workflow_ENG v1.0.JPG|centre|thumb|800x800px|Access Requests workflow and statuses.]]
+[[File:Audits_Workflow_ENG v1.0.JPG|centre|thumb|800x800px|Audits workflow and statuses.]]