Difference between revisions of "Actions"

From Privacy-Now
Jump to: navigation, search
(Workflow)
(Workflow)
 
(3 intermediate revisions by the same user not shown)
Line 10: Line 10:
 
A workflow enables to move ''actions" in several statuses as shown in the following picture.
 
A workflow enables to move ''actions" in several statuses as shown in the following picture.
  
[[File:Actions_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Access Requests workflow and statuses.]]
+
[[File:Actions_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Actions workflow and statuses.]]
  
  
Line 33: Line 33:
  
 
== Information ==
 
== Information ==
''Access request'' records information are organized in four sections:
+
''Action'' records are organized in three sections:
  
* <u>''Identification''</u>, where identification data of the ''access request'' are recorded,
+
* <u>''Identification''</u>, where identification data of the ''action'' 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 ''action'';
* <u>''Access Request Details''</u>, with the details of the ''access request'';
+
* <u>''Action Details''</u>, with the details of the ''action''.
* <u>''Data Subject Details''</u>, with the details of the ''data subject'' issuing the ''access request'';
 
* <u>''Data Subject Representative''</u>, containing the details of the representative of the ''data subject'', if any.
 
  
 
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.  
 
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 46: Line 44:
  
 
== Privileges ==
 
== 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).
+
''Actions'' 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 ''action'' 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"
Line 68: Line 66:
 
|<u>Audit Team</u> || Members of the ''group'' assigned to this role have view (read) privileges.
 
|<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>Action 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,
 
* transition to any compatible status,
 
* update fields when possible.
 
* update fields when possible.
 
|}
 
|}
 
== Warning and alerts ==
 
TBC
 
  
 
== Reports ==
 
== Reports ==
The list of ''access requests'' can be filtered and exported to excel format from the ''view'' '''''Access Requests'''''.
+
The list of ''actions'' can be filtered and exported to excel format from the ''view'' '''''Actions'''''.
  
 
== Related processes ==
 
== Related processes ==
''Access Requests'' can be related to ''processing activities''.
+
''Actions'' can be related to ''data breaches'', ''issues / non conformities'', ''privacy impact assessments'', ''risks'' and ''processing activities''.

Latest revision as of 14:47, 12 September 2018

Introduction to Actions

Actions provide a way to support and oversee tasks and activities needed to manage the lifecycle of any other aspect of personal data compliance management (e.g. processing activities, access requests, etc.).

The process enables to record actions and to support their fulfilment.

Workflow

A new action can be created using the Add New functionality and choosing "New Action".

A workflow enables to move actions" in several statuses as shown in the following picture.

Actions workflow and statuses.


The following table explains the meaning of each status:

Status Description
Default A temporary status where the action is initially created before the first save
Draft An action in this status is being defined and not actioned.
Opened An action in this status is defined and in progress.
Cancelled Action cancelled. This is an end of life status.
Completed In this status, all activities related to the action were completed. This is an end of life status, meaning no further status transitions are allowed.
Closed In this status, all activities related to the action are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.

Information

Action records are organized in three sections:

  • Identification, where identification data of the action are recorded,
  • Ownership & Organization, containing the assignment of the key roles enabled to manage the action;
  • Action Details, with the details of the action.

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

Actions 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 action 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:
  • transition records to any compatible status,
  • update fields when possible,
  • update data sources directly in record management.
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:
  • transition records to any compatible status,
  • update fields when possible.
Audit Team Members of the group assigned to this role have view (read) privileges.
Action Owner This role can be assigned to a single user among members of the groups previously described. The Owner has several privileges:
  • transition to any compatible status,
  • update fields when possible.

Reports

The list of actions can be filtered and exported to excel format from the view Actions.

Related processes

Actions can be related to data breaches, issues / non conformities, privacy impact assessments, risks and processing activities.