<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.privacy-now.eu/en/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cbisso</id>
		<title>Privacy-Now - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.privacy-now.eu/en/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Cbisso"/>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php/Special:Contributions/Cbisso"/>
		<updated>2026-05-14T13:44:37Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.30.0</generator>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=712</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=712"/>
				<updated>2018-10-19T10:28:00Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Bulk operations on consent records */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the current ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is selected.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=709</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=709"/>
				<updated>2018-10-19T09:51:28Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Bulk operations on consent records */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the current ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is selected.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=708</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=708"/>
				<updated>2018-10-19T09:51:17Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Bulk operations on consent records */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the current ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is selected.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=707</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=707"/>
				<updated>2018-10-19T09:23:39Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Consent Mail Structure and Procedure */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the current ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is selected.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newsletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''conset type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=706</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=706"/>
				<updated>2018-10-19T08:14:44Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Warning and alerts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the current ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is selected.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''conset type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=705</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=705"/>
				<updated>2018-10-19T07:43:52Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Warning and alerts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the current ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is set to &amp;quot;true&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''conset type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=704</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=704"/>
				<updated>2018-10-18T15:17:32Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Settings#Consents Source Details|Consents Source Details]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set manually or automatically. It can be set automatically by bulk import from xlsx.&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
Is possible to select only one ''consent type'' and one ''consent subject'' for each ''consent'' record.&lt;br /&gt;
When the ''consent type'' is selected/updated the following fields could be automatically updated too (check details in table below).&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt;||At record insert/update: the value of this field will be set to &amp;quot;Yes&amp;quot; if selected ''consent type'' &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; is &amp;gt; 0, otherwise &amp;quot;No&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Last Update&amp;lt;/u&amp;gt;||At record insert/update: The value of this field will be set to current date and time.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Final Consent Warning&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Deadline&amp;lt;/u&amp;gt;||This field is updated only if &amp;lt;u&amp;gt;Consent Expires&amp;lt;/u&amp;gt; is set to &amp;quot;yes&amp;quot;, otherwise not. At record insert/update: The value of this field will be set to current date + days specified in &amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
A ''consent'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Each ''consent'' will be set as an expiring consent or not depending from the property &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; of selected ''consent type'':&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; = 0: in this case the current ''consent'' will never expire and &amp;lt;u&amp;gt;'''no warning will be raised'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
* &amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt; &amp;gt; 0: in this case the consent ''consent'' will expire and will be possible to configure four levels of warning.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt;||The value of this field shall be an integer and shall be univocal. It is the matching code used by Privacy Now® to automatically acquire ''consent'' from external system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;||The value of this field shall be univocal. It is the name of ''consent type'' (i.e.: &amp;quot;Newsletter&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||Description of ''consent type''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Duration (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It is used by Privacy Now® mainly to set current ''consent'' record as expiring ''consent'' or not.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;First Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the first warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Second Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the second warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Third Warning (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the third warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Retention Period (days)&amp;lt;/u&amp;gt;||The value of this field shall be an integer &amp;gt;= 0. It will be used to evaluate the last warning threshold in case current ''consent'' is an expiring one.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Web Site URL&amp;lt;/u&amp;gt;||The value of this field will be the URL of front-end web site area to allow the ''data subject'' management of their ''consent'' (renew or revoke). It will be used in warning email sent by Privacy Now® to ''data subject'' in case the below option &amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt; is set to &amp;quot;true&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Send Warning to Data Subject&amp;lt;/u&amp;gt;||This field shall be set to &amp;quot;true&amp;quot; if consent record for selected ''consent type'' shall cause warning sending to ''data subject'' too, otherwise the warning will be sent only to receivers set into &amp;lt;b&amp;gt;''Settings\Application Settings''&amp;lt;/b&amp;gt; (see the paragraph dedicated to [[Settings#Notification Settings|Consents Warnings Recipients ]]).&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Consents Import ==&lt;br /&gt;
Privacy-Now® allows to acquire ''consents'' from external source (using structured email or xlsx file).&lt;br /&gt;
&lt;br /&gt;
=== Consent Mail Structure and Procedure ===&lt;br /&gt;
Privacy-Now® can be connected to a mailbox to acquire ''consents'' (see the paragraph dedicated to [[Settings#Consents Source Details|Consents Source Details]]).&lt;br /&gt;
&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example of a well structured email:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
== Bulk operations on consent records ==&lt;br /&gt;
Privacy Now® allows the bulk management of ''consent'' from &amp;lt;b&amp;gt;''Consents\Manage Consents from xlsx''&amp;lt;/b&amp;gt;.&lt;br /&gt;
[[File:Consent bulk import - xlsx example.jpg|centre|thumb|800x800px|Consents bulk management.]]&lt;br /&gt;
&lt;br /&gt;
Use below template to perform following bulk operations:&lt;br /&gt;
&lt;br /&gt;
 [[File:Consent Import Template.xlsx|centre|thumb|800x71px|Consents management template.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The operations allowed are:&lt;br /&gt;
* &amp;quot;insert&amp;quot;: Insert/Update of ''consents''&lt;br /&gt;
The data in current xlsx row will be updated on an existing ''consent'' if system match it univocally by ''conset type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'', otherwise a new ''consent'' will be created.&lt;br /&gt;
If ''data subject'' is not found: it will be created.&lt;br /&gt;
 &lt;br /&gt;
* &amp;quot;remove&amp;quot;: Removal of ''consents''&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be removed.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;wrongemail&amp;quot;: Move ''consents'' in status &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
The ''consent'' matched by ''consent type'' code, ''data subject'' &amp;lt;u&amp;gt;email&amp;lt;/u&amp;gt; and ''source'' will be moved in &amp;quot;Wrong Email&amp;quot; status. Only consent in &amp;quot;Valid&amp;quot; status can be moved in &amp;quot;Wrong Email&amp;quot; status.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The details of expected xlsx structure is explained in following table: for each operations is detailed which are the mandatory data. &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description!!Insert/Update!!Remove!!Move to &amp;quot;Wrong Email&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Id&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in Privacy Now®.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;||Name of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;||Surname of ''Data Subject'' in acquiring system.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;||Email of ''Data Subject'' in acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;||Phone of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;||City of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province/State&amp;lt;/u&amp;gt;||Province/State of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;||Country of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;||Login of ''Data Subject'' in acquiring system.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent&amp;lt;/u&amp;gt;||&amp;lt;u&amp;gt;Consent Type Code&amp;lt;/u&amp;gt; to be granted to imported ''Data Subject'' (defined in Privacy Now®).||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Consent Value&amp;lt;/u&amp;gt; given by ''Data Subject'' for the imported &amp;lt;u&amp;gt;Consent Type&amp;lt;/u&amp;gt;. The value could be &amp;quot;1&amp;quot; (''consent'' granted) or &amp;quot;0&amp;quot; (''consent'' not granted).||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data&amp;lt;/u&amp;gt;||''consent'' date.||Mandatory||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt;||record description.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Service&amp;lt;/u&amp;gt;||Privacy Now® ''service'' used as import target.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;||''Data Subject'' selected language.||Optional||Optional||Optional&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;uid&amp;lt;/u&amp;gt;||Univocal Id of ''Data Subject'' in acquiring system.||Optional||Optional||Optional &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;||A key word defining univocally the acquiring system.||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Operation&amp;lt;/u&amp;gt;||This field specify which is the operation expected for current xlsx record: &amp;quot;insert&amp;quot;, &amp;quot;remove&amp;quot; or &amp;quot;wrongemail&amp;quot;||Mandatory||Mandatory||Mandatory&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
A ''consent'' can be removed individually from Application Settings (see the paragraph dedicated to [[Settings#Utility|Appication Settings - Utility]]).&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=638</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=638"/>
				<updated>2018-10-15T08:19:04Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Application settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Types'''''|| The type of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source of ''consent''. Could be a website name or the name of the company.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Notification Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Utility''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identify the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the current status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mail &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Consents Source Details ====&lt;br /&gt;
This section allows to configure the mailbox to import ''consents'' in current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
The front-end web site shall be able to gather ''consents'' and send them to this mailbox as a structured email (described in next chapter).&lt;br /&gt;
&lt;br /&gt;
Each correctly parsed email will generate one or more ''consents'' in current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IS STRONGLY RECOMMENDED TO CREATE A BACKUP MAILBOX TO STORE ALL THE EMAIL (TO BE FORWARDED FROM MAIN MAILBOX) BECAUSE PRIVACY-NOW® WILL DELETE THEM DURING PARSING PROCESS.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Host&amp;lt;/u&amp;gt;|| This field shall be filled with the mailbox server address.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Port&amp;lt;/u&amp;gt;|| This field shall be filled with the mailbox server port.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| This field shall be filled with the mailbox login.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Password&amp;lt;/u&amp;gt;|| This field shall be filled with the mailbox password.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| This field shall be filled with the email.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Protocol&amp;lt;/u&amp;gt;|| This field shall be filled with the mailbox server protocol (available: &amp;quot;POP3&amp;quot;, &amp;quot;IMAP&amp;quot;, &amp;quot;POP3S&amp;quot;, &amp;quot;IMAPS&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt;|| This field contains values: &amp;quot;Active&amp;quot;, &amp;quot;Inactive&amp;quot;. When it will be saved in &amp;quot;Active&amp;quot;: Privacy-Now® will start to download and elaborate all the email.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Expected Consent Mail Structure and Procedure ====&lt;br /&gt;
A ''consent'' email shall contain the following parameters (one for each row): some of them are mandatory, while some other optional (check the detailed description of each one).&lt;br /&gt;
The email format shall be '''plain text''' (HTML email will not be processed correctly) and shall not contain any signature.&lt;br /&gt;
&lt;br /&gt;
Each mail shall contain one or more ''consent''. Each ''consent'' is manageable only if 3 parameters are present and valorized: &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt; , &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each ''consent'' present in mail will create a new ticket or update an existing ticket in Privacy-Now®. The existence of a consent is matched on &amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt; and the option selected in &amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Source&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory''' and shall be filled with the ''consent'' source (ie: could be the company name or business unit name or web site name). The value of this parameter shall match with the value(s) inserted in '''''Settings/Data Sets/Consents/Consent Sources'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt;|| The value of this parameter is '''mandatory'''. The first name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt;|| The family name of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt;|| The email of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;City&amp;lt;/u&amp;gt;|| The town of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Province_State&amp;lt;/u&amp;gt;|| The province or state of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Country&amp;lt;/u&amp;gt;|| The country of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Phone&amp;lt;/u&amp;gt;|| The phone number of ''data subject''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;User_id&amp;lt;/u&amp;gt;|| The univocal id (integer) of the user corresponding to ''data subject'' in consent source (ie: id of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt;|| The univocal login of the user corresponding to ''data subject'' in consent source (ie: login of user in web site).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;IP_address&amp;lt;/u&amp;gt;|| The ip address used by ''data subject'' during web site browsing.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Lang&amp;lt;/u&amp;gt;|| The main language of ''data subject''. Possible values: &amp;quot;en-GB&amp;quot;, &amp;quot;it-IT&amp;quot; and &amp;quot;fr-FR&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consent_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). At least one Consent_'''[consent name]''' shall exist in the email. The value of this parameter shall be a univocal code corresponding to one of the &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; inserted in '''''Settings/Data Sets/Consents/Consent Types'''''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Value_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Value_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be &amp;quot;1&amp;quot; (''consent'' given) or &amp;quot;0&amp;quot; (''consent'' denied).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt;||'''[consent name]''' shall be replaced by the name of ''consent'' (ie: consent_newseletter). For each of the Consent_'''[consent name]''' defined in the email shall be present a corresponding &amp;lt;u&amp;gt;Date_Time_'''[consent name]'''&amp;lt;/u&amp;gt; (ie: &amp;lt;u&amp;gt;Date_Time_Newsletter&amp;lt;/u&amp;gt;). The value of this parameter shall be the date and time of ''consent'' management in web site. It shall be in format '''dd-mm-yyyy hh:mm:ss''' .&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Example:'''&lt;br /&gt;
 Source:myCompanyName&lt;br /&gt;
 Name:Jhon&lt;br /&gt;
 Surname:Smith&lt;br /&gt;
 Email:jhon.smith@mymail.com&lt;br /&gt;
 City:myTown&lt;br /&gt;
 Province_State:myProvince&lt;br /&gt;
 Country:myCountry&lt;br /&gt;
 Phone:002235468&lt;br /&gt;
 User_id:12345&lt;br /&gt;
 Username:jsmith&lt;br /&gt;
 IP_address:192.168.1.27&lt;br /&gt;
 Lang:en-GB&lt;br /&gt;
 Consent_A:1&lt;br /&gt;
 Value_A:0&lt;br /&gt;
 Date_Time_A:12-10-2018 10:14:50&lt;br /&gt;
 Consent_B:2&lt;br /&gt;
 Value_B:0&lt;br /&gt;
 Date_Time_B:12-10-2018 10:14:50&lt;br /&gt;
 Consent_Newsletter:3&lt;br /&gt;
 Value_Newsletter:1&lt;br /&gt;
 Date_Time_Newsletter:12-10-2018 10:14:50&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;GDPR Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== Notification Settings ===&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Breach Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''data breach'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Authority Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''data breach'' warnings for authority are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Access  Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''access request'' warnings are triggered.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Utility ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Delete ticket ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Ticket Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Ticket''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=591</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=591"/>
				<updated>2018-10-10T12:27:05Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Users Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item lists the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add New''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges as the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=590</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=590"/>
				<updated>2018-10-10T12:19:01Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Delete ticket */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Categories'''''|| The category of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source where the consent is given or denied, for example a &amp;quot;contract&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tools''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identity the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the actual status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mails &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;GDPR Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;br /&gt;
&lt;br /&gt;
=== Utility ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Delete ticket ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Ticket Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Ticket''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=589</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=589"/>
				<updated>2018-10-10T12:18:14Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Tools */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Categories'''''|| The category of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source where the consent is given or denied, for example a &amp;quot;contract&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tools''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identity the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the actual status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mails &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;GDPR Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;br /&gt;
&lt;br /&gt;
=== Utility ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Delete ticket ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Record Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Record''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=588</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=588"/>
				<updated>2018-10-10T12:16:01Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Group Settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Categories'''''|| The category of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source where the consent is given or denied, for example a &amp;quot;contract&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tools''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identity the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the actual status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mails &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;GDPR Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;br /&gt;
&lt;br /&gt;
=== Tools ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Record deletion ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Record Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Record''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=587</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=587"/>
				<updated>2018-10-10T12:13:37Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Group Settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Categories'''''|| The category of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source where the consent is given or denied, for example a &amp;quot;contract&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tools''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identity the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the actual status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mails &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Auditors Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;br /&gt;
&lt;br /&gt;
=== Tools ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Record deletion ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Record Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Record''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=586</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=586"/>
				<updated>2018-10-10T12:10:55Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Consents Settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Categories'''''|| The category of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source where the consent is given or denied, for example a &amp;quot;contract&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tools''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identity the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the actual status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mails &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subject Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Audit Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Audit Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;br /&gt;
&lt;br /&gt;
=== Tools ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Record deletion ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Record Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Record''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=585</id>
		<title>Settings</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Settings&amp;diff=585"/>
				<updated>2018-10-10T12:10:47Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Consents Settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Introduction==&lt;br /&gt;
This part of the guide covers some fundamental settings which are needed to work with Privacy Now®:&lt;br /&gt;
&lt;br /&gt;
* Master data&lt;br /&gt;
* Application settings&lt;br /&gt;
&lt;br /&gt;
== Master data ==&lt;br /&gt;
Master data tables contain the sources data of the fields using single or multi choice options.&lt;br /&gt;
&lt;br /&gt;
Master data tables are preloaded with initial values when the environment is initially created. These values can be later changed by ''users'' with the &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; field set to &amp;quot;Yes&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
Editing of master data table can be done from the left menu '''''Settings/Data Sets''''' or directing from the records using the fields based on the master data (in both cases if the ''user'' has the required privileges).&lt;br /&gt;
&lt;br /&gt;
The table below lists the master data tables and provides a short description of their content.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Access menu !! Description&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Access Requests Types'''''|| The types of ''access requests'', e.g. &amp;quot;Personal data deletion&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Communication Channels'''''|| The communication channels used to acquire the ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Results Notification Methods'''''|| The communication channels to be used to communicate the results of an ''access request'', e.g. &amp;quot;email&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Data Subject Types'''''|| The type of subject requesting the ''access request'', e.g. &amp;quot;employee&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Requests/Relationships to Data Subjects'''''|| The type of relationship between the access request requester and the data subject representative, if any, for example &amp;quot;family relationship&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Access Request/Access Request Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Actions/Action Type'''''|| The type of action, for example &amp;quot;corrective&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Categories'''''|| The category of the consent, for example the consent to send a newsletter. This table is very likely to be updated.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Sources'''''|| The source where the consent is given or denied, for example a &amp;quot;contract&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Subjects'''''|| The subject giving the consent, typically a person.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Consents/Consent Matching Mail'''''|| The email address of the recipient where the consent is sent. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Affected Personal Data Categories'''''|| The categories of subjects whose ''personal data'' are treated during the ''data breach'', for example &amp;quot;employees master data&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Data Breach Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Authority Warning Schedule'''''|| This data set enable the ''user'' to set the plan the sent of warning mail to the Authority.  &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Data Breaches/Type of Breaches'''''|| Identify the type of Breaches , for example &amp;quot;Security Breach&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Issues / Non Conformities/Issue Types'''''|| The type of issue, i.e. an &amp;quot;issue&amp;quot; or a &amp;quot;non conformity&amp;quot;. These values are unlikely to be modified.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Privacy Impact Assessments/PIA Reference Period'''''|| Th timeframe to which the privacy impact assessment refers to, for example &amp;quot;2018 Q4&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Applications'''''|| The applications which may be used to access ''personal data'', for example &amp;quot;web browsers&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Connections'''''|| The connections which may be used when accessing ''personal data'', for example &amp;quot;internet&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Access Devices''''' || The devices which may be used when accessing ''personal data'', for example &amp;quot;personal computer&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Locations'''''|| The locations where the ''personal data'' can be stored during their processing, for example &amp;quot;New York data centre&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Processing Purposes'''''|| The purposes of data processing, for example &amp;quot;marketing activities&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Repositories'''''|| The type of data repositories where ''personal data'' are stored during the ''processing activities'', for example a specific SQL database server.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Subjects'''''|| The types of data subjects whose ''personal data'' are treated during the ''processing activities'' or declared in ''Data Breach'', for example &amp;quot;clients&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Data Types'''''|| The types of data, e.g. identification or judicial data, which are processed during the ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Extra EU Measures'''''|| The types of measures in place to mitigate the risks of extra EU ''processing activities'', e.g. a &amp;quot;code of conduct&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Lawful Basis for Processing'''''|| The lawful basis on which the processing of ''personal data'' is authorized, e.g. &amp;quot;legal obligations&amp;quot;.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Processing Activities'''''|| The types of ''processing activities'' performed during the processing of ''personal data'', e.g. collection, adaptation, etc.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Provision Agreements'''''|| The type of provision agreement with the suppliers of data repository tools, access applications, access devices, connectivity, for example a &amp;quot;software as a service&amp;quot; agreement.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Retention Periods'''''|| The possible retention periods for the ''personal data'' which is processed, for example 10 years.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/Processing Activities/Suppliers'''''|| The suppliers of data repository tools, access applications, access devises or connectivity. &lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Controllers Entities'''''|| The details of the controller entities involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|'''''Settings/Data Sets/ Processors / Data Controller Officers'''''|| The details of the data controller officers involved in ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Application settings ==&lt;br /&gt;
&lt;br /&gt;
This section concerns the preferences and settings which can be defined at application level for Privacy-Now®. These settings are accessible from '''''Settings/Application Settings'''''.&lt;br /&gt;
&lt;br /&gt;
Application settings are accessible only by ''users'' with administration privileges (see below how to set them). The first ''user'' created when Privacy-Now® environment is created is set with administration privileges.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Settings/Application Settings''&amp;lt;/b&amp;gt; link open the ''Setting'' Ticket. &lt;br /&gt;
&lt;br /&gt;
Settings are organized in six sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consents Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Group Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''License Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Purchase History''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tools''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tracking ===&lt;br /&gt;
These setting enable the ''User'' to identity the ''service name'' and the &amp;lt;u&amp;gt;Subscription id&amp;lt;/u&amp;gt; they have subscribed and the actual status of the ''service''&lt;br /&gt;
&lt;br /&gt;
=== Consents Settings ===&lt;br /&gt;
These settings refer to ''consents'' management process. See the [[consents]] guide for more information on the process.&lt;br /&gt;
&lt;br /&gt;
The table below report the settings fields available and a short description of their meaning:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Matching Mails &amp;lt;/u&amp;gt;|| ''Consents'' can be acquired from emails. With this field it is possible to define the recipients of the emails which will be checked to process the ''consents''. Emails in the inbox with other recipients will be ignored.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Consents Warnings Recipients&amp;lt;/u&amp;gt; || This field contains the emails addresses notified when ''consents'' warnings are triggered.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Subjects Matching criteria&amp;lt;/u&amp;gt; || This field allow to define the criteria to match an incoming ''consent'' sent by mail with the existing ''consents'' in Privacy-Now®. After trying to match if the consent subject is found, the existing consent record is updated. If the consent subject is not found, a new consent record is created. This field may have one of the following two values: &amp;quot;Mail&amp;quot; (consent subject is matched using the email address), &amp;quot;Username&amp;quot; (consent subject is matched using the user name identifier, for example the login used by the consent subject to access a website). &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Group Settings ===&lt;br /&gt;
Privacy-Now® has several profiles for ''user'' privileges. The profiles determines what ''users'' can do while executing processes (e.g. ''access requests'', ''consents'', etc.). ''Users'' can be assigned to ''groups'' and ''groups'' can be finally assigned to profiles in each record (e.g. ''access request'', ''consent'' etc.).&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Profile&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Audit Team Profile&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Profile&amp;lt;/u&amp;gt; allow to define which &amp;quot;groups&amp;quot; the ''user'' will be able to see and select in each process.&lt;br /&gt;
&lt;br /&gt;
The fields &amp;lt;u&amp;gt;DPO Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DP Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;DC Default&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Audit Team Default&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Working Team Default&amp;lt;/u&amp;gt; allow to define the default &amp;quot;groups&amp;quot; which will be set everytime a new record is created.&lt;br /&gt;
&lt;br /&gt;
The above fields, shall be defined for each process/workflow, e.g. ''access requests'', ''actions'', ''audits'' management, etc.&lt;br /&gt;
&lt;br /&gt;
In order to update the fields for a process, perform the following steps:&lt;br /&gt;
&lt;br /&gt;
*Choose the process by setting the &amp;lt;u&amp;gt;Process&amp;lt;/u&amp;gt; field&lt;br /&gt;
*Load the set values for all the field by using the '''LOAD''' command&lt;br /&gt;
*Set the values for the fields&lt;br /&gt;
*Save the settings by using the '''SAVE''' command at the bottom of the form.&lt;br /&gt;
&lt;br /&gt;
Repeat the above steps for all the processes you need to configure.&lt;br /&gt;
&lt;br /&gt;
=== License Details ===&lt;br /&gt;
This section allows to view the details of the license active for the current Privacy-Now® environment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;License Package&amp;lt;/u&amp;gt;|| This field shows the type of subscription active.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed User&amp;lt;/u&amp;gt;|| This field shows the number of activated ''users'' (those in status &amp;quot;Active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Access Requests&amp;lt;/u&amp;gt;|| Monthly number of ''access requests'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Licensed Consents&amp;lt;/u&amp;gt;|| Monthly number of ''consents'' that it is possible to open. This numbers is depending on the type of subscription.&lt;br /&gt;
|-&lt;br /&gt;
|'''Check License'''|| This commands launches a system check that refreshes the values of &amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt; and &amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt; fields.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Active Users&amp;lt;/u&amp;gt;|| Number of &amp;quot;users&amp;quot; currently activated (in status &amp;quot;active&amp;quot;).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Access Requests&amp;lt;/u&amp;gt;|| Number of ''access requests'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Monthly Consents&amp;lt;/u&amp;gt;|| Number of ''consents'' opened in the current month.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Initial Activation Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service was initially activated.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Expected End Date&amp;lt;/u&amp;gt;|| The date when the Privacy-Now® service will terminate. Access wont' be possible after this date. The environment and all data will be fully erased 30 days after this date.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Purchase History ===&lt;br /&gt;
In this section, the history of the purchase transaction is reported for control aims.&lt;br /&gt;
Every transaction is added after the last before.&lt;br /&gt;
&lt;br /&gt;
=== Tools ===&lt;br /&gt;
In this sections, special functionalities are grouped.&lt;br /&gt;
&lt;br /&gt;
==== Record deletion ====&lt;br /&gt;
From records management (e.g. ''access requests'', ''consents'') physical deletion is not possible. In other words, records can always be moved to one or more end of life status(es) where no changes are possible. however, normal ''users'' cannot physically delete records. This can be done instead by ''users'' with administrative privileges with this tool.&lt;br /&gt;
&lt;br /&gt;
To delete a record, simply enter the record code to be deleted in &amp;lt;u&amp;gt;Record Code to Delete&amp;lt;/u&amp;gt; and launch the '''Delete Record''' command.&lt;br /&gt;
&lt;br /&gt;
IMPORTANT WARNING: IT WILL NOT BE POSSIBLE TO RESTORE THE RECORD CONTENT AFTER DELETION.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Privacy_Impact_Assessments&amp;diff=584</id>
		<title>Privacy Impact Assessments</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Privacy_Impact_Assessments&amp;diff=584"/>
				<updated>2018-10-10T10:44:40Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Privacy Impact Assessments ==&lt;br /&gt;
In Privacy-Now®, ''Privacy Impact assessments'' are focused to assess the risks associated with data processing activities (actually they are ''Data Protection Impact Assessments'').&lt;br /&gt;
&lt;br /&gt;
The process enables to record ''Privacy Impact Assessments'' and to support their fulfilment. ''Privacy Impact Assessments'' are typically related to one or more ''processing activities'', those to which they refer to. &lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''Privacy Impact Assessment'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Privacy Impact Assessment&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move the ''Privacy Impact Assessment&amp;quot; in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File: Privacy_Impact_Assessment_workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Privacy Impact Assessments workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''Privacy Impact Assessment'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || A ''Privacy Impact Assessment'' in this status is draft.&lt;br /&gt;
|-&lt;br /&gt;
|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''.&lt;br /&gt;
|-&lt;br /&gt;
|Suspended || Activities concerning the ''Privacy Impact Assessment'' are temporarily suspended.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, the assessment is completed. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Privacy Impact Assessment'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Privacy Impact Assessment'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''Privacy Impact Assessment'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''Privacy Impact Assessment'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Risk Assessment Questions''&amp;lt;/u&amp;gt;, containing the preliminary assessment questions;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Impact Assessment Questions''&amp;lt;/u&amp;gt;, if any significant risk is found in the &amp;lt;u&amp;gt;''Risk Assessment Questions''&amp;lt;/u&amp;gt; section, it contains detailed impact assessment questions (''DPIA'');&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Privacy Impact Assessments'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Assessment Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;PIA Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''Privacy Impact Assessments'' can be filtered and exported to excel format from the ''view'' '''''Privacy Impact Assessments'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Privacy Impact Assessments'' can be related to ''processing activities'', ''risks'' and ''issues / non conformities''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Data_Breaches&amp;diff=583</id>
		<title>Data Breaches</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Data_Breaches&amp;diff=583"/>
				<updated>2018-10-10T10:31:05Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Data Breaches ==&lt;br /&gt;
Data breaches workflow provide the mean to manage the lifecycle of ''data breaches''. This means recording and updating the information related to the ''data breach'', supporting the tasks needed for remediation and the needed communication.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''data breach'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Data Breach&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''data breaches&amp;quot; in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Data_Breaches_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Data Breaches workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''data breach'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || A ''data breach'' in this status is raised for analysis.&lt;br /&gt;
|-&lt;br /&gt;
|Analysed || In this status, the analysis of a ''data breach'' is completed. The ''data breach'' is therefore to be cancelled or to be actioned (taken in charge).&lt;br /&gt;
|-&lt;br /&gt;
|In charge || In this status, the ''data breach'' has been taken in charge and it is being actioned. &lt;br /&gt;
|-&lt;br /&gt;
|Notified || In this status, the ''data breach'' has been notified to the interested parties.&lt;br /&gt;
|-&lt;br /&gt;
|Resolved || In this status, all activities related to the ''data breach'' are completed and closure is expected after confirmation of remediation.&lt;br /&gt;
|-&lt;br /&gt;
|Suspended || Activities concerning the ''data breach'' are temporarily suspended.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, all activities related to the ''data breach'' are performed and remediation / communications are completed. This is an end of life status, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Data breach'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Data breach'' records are organized in seven sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''data breach'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''data breach'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Investigator''&amp;lt;/u&amp;gt;, with the details of the resource in charge of investigating the ''data breach'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Data Breach Details''&amp;lt;/u&amp;gt;, with the details of the ''data breach'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Data Breach Impact''&amp;lt;/u&amp;gt;, containing information about the ''data breach'' impact;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Data Breach Notification''&amp;lt;/u&amp;gt;, containing information about the notification of the ''data breach'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Remediation Actions''&amp;lt;/u&amp;gt;, containing information about the remediation actions for the ''data breach''.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Data breaches'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''dta breach'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Investigation Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''data breaches'' can be filtered and exported to excel format from the ''view'' '''''Data Breaches'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Data breaches'' can be related to ''risks'', ''actions'' and ''issues / non conformities''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Risks&amp;diff=582</id>
		<title>Risks</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Risks&amp;diff=582"/>
				<updated>2018-10-10T10:28:10Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Risks ==&lt;br /&gt;
This workflow provides the mean to manage the lifecycle of ''risks'' related to ''personal data'' management. &lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''risk'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Risk&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The workflow enables to move ''risks&amp;quot; in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Risks_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Risks workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''risk'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Draft || A ''risk'' in this status is draft and is not confirmed nor actioned yet.&lt;br /&gt;
|-&lt;br /&gt;
|Potential || A ''risk'' in this status is confirmed and shall be actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Mitigated || In this status, the ''risk'' has been actioned and mitigated. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Risk'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, risk has been threated successfully and no more actions are needed. This is an end of life status, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Risks'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''risk'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''risk'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Pre-mitigation Assessment''&amp;lt;/u&amp;gt;, with the assessment details of the ''risk'' before mitigation actions;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Post-mitigation Assessment''&amp;lt;/u&amp;gt;, with the details of the ''risk'' after mitigation actions.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Risks'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''risk'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Risk Assessment Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''risks'' can be filtered and exported to excel format from the ''view'' '''''Risks'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Risks'' can be related to ''actions'', ''audits'', ''data breaches'', ''issues / non conformities'', ''privacy impact assessments'' and ''processing activities''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Access_Requests&amp;diff=581</id>
		<title>Access Requests</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Access_Requests&amp;diff=581"/>
				<updated>2018-10-10T10:18:18Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Access Requests ==&lt;br /&gt;
''Access requests'' provide the mean for data subjects to exercise their right to access information about the processing of their &lt;br /&gt;
''personal data'' (e.g. according to section 2, article 13 of ''GDPR Regulation'').&lt;br /&gt;
&lt;br /&gt;
The workflow enables to record ''access requests'' and to support their fulfilment.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''access request'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Access Request&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''access requests&amp;quot; in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Access_Requests_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Access Requests workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''access request'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || An ''access request'' in this status is draft and it is not actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Requested || An ''access request'' in this status is confirmed and it is waiting to be actioned.&lt;br /&gt;
|-&lt;br /&gt;
|In charge || In this status, the ''access request'' has been taken in charge and it is being actioned. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Access request'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|Completed || In this status, all activities related to the ''access request'' were completed and closure is expected after confirmation.&lt;br /&gt;
|-&lt;br /&gt;
|Suspended || Activities concerning the ''access request'' are temporarily suspended, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Access request'' records are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''access request'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''access request'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Access Request Details''&amp;lt;/u&amp;gt;, with the details of the ''access request'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Data Subject Details''&amp;lt;/u&amp;gt;, with the details of the ''data subject'' issuing the ''access request'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Data Subject Representative''&amp;lt;/u&amp;gt;, containing the details of the representative of the ''data subject'', if any.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Access request'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
TBC&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''access requests'' can be filtered and exported to excel format from the ''view'' '''''Access Requests'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Access Requests'' can be related to ''processing activities''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=580</id>
		<title>Processing Activities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=580"/>
				<updated>2018-10-10T10:06:16Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Processing Activities ==&lt;br /&gt;
''Processing activities'' are the core element of ''personal data'' management. Many regulations require to document and assess them. &lt;br /&gt;
&lt;br /&gt;
Privacy-Now® dedicated process enables to record ''processing activities'', to maintain them and to use them for assessment or other tasks related to ''personal data'' management.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''processing activity'' can be created using the ''Add New'' functionality and choosing &amp;quot;New Processing Activity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move the ''processing activities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Processing Activities Workflow ENG v1.0.JPG|centre|thumb|800x800px|Processing activities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''processing activity'' is initially created before the first save. &lt;br /&gt;
|-&lt;br /&gt;
|Draft || A ''processing activity'' in this status is draft.&lt;br /&gt;
|-&lt;br /&gt;
|Active || A ''processing activity'' in this status is actually executed by the ''organization''.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Processing activity'' cancelled. It is still possible to recover a ''processing activity'' from this status by enabled ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Processing activities'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''processing activity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Characteristics''&amp;lt;/u&amp;gt;, with the key attributes of the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Information Technology''&amp;lt;/u&amp;gt;, with information about the technologies used to process ''personal data'' by the ''processing activivty''.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Processing activities'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management,&lt;br /&gt;
* revert from &amp;quot;Cancelled&amp;quot; status.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Representative&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''DPO group'' or the ''Data Controller Group''. The &amp;lt;u&amp;gt;Representative&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''processing activities'' can be filtered and exported to excel format from the ''view'' '''''Processing Activities'''''.&lt;br /&gt;
&lt;br /&gt;
Finally, it is possible to print the ''processing activity'' card using the '''Print''' command positioned up right in the ''&amp;lt;u&amp;gt;General&amp;lt;/u&amp;gt;'' form of the ''processing activity'' record.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
Many other entities can be related to ''processing activity'' records, in particular:&lt;br /&gt;
* ''access requests'',&lt;br /&gt;
* ''actions'',&lt;br /&gt;
* ''impact assessments'',&lt;br /&gt;
* ''risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=579</id>
		<title>Issues &amp; Non Conformities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=579"/>
				<updated>2018-10-10T09:54:56Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Issues / Non Conformities ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''issue / non conformity'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Issue or Non Conformity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The workflow enables to move ''issues / non conformities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Issues_non_Conformities_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Issues / non conformities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''issue / non conformity'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Draft || An ''issue / non conformity'' in this status is draft and it is not actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || An ''issue / non conformity'' in this status is confirmed and it is actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Issue / non conformity'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|Completed || In this status, all activities related to the ''issue / non conformity'' were completed and closure is expected after confirmation.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, all activities related to the ''issue / non conformity'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Issue / non conformity'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''issue / non conformity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''issue / non conformity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Issue / Non Conformity Details''&amp;lt;/u&amp;gt;, with the details of the ''issue / non conformity''.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Issue / non conformity'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Protection Officer (DPO) Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Issue / NC Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''issues / non conformities'' can be filtered and exported to excel format from the ''view'' '''''Issues / Non Conformities'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'', ''Privacy Impact Assessment'' and ''Risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=578</id>
		<title>Issues &amp; Non Conformities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=578"/>
				<updated>2018-10-10T09:54:25Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Issues / Non Conformities ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''issue / non conformity'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Issue or Non Conformity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The workflow enables to move ''issues / non conformities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Issues_non_Conformities_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Issues / non conformities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''issue / non conformity'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Draft || An ''issue / non conformity'' in this status is draft and it is not actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || An ''issue / non conformity'' in this status is confirmed and it is actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Issue / non conformity'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|Completed || In this status, all activities related to the ''issue / non conformity'' were completed and closure is expected after confirmation.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, all activities related to the ''issue / non conformity'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Issue / non conformity'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''issue / non conformity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''issue / non conformity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Issue / Non Conformity Details''&amp;lt;/u&amp;gt;, with the details of the ''issue / non conformity''.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Issue / non conformity'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Protection Officer (DPO) Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditor Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Issue / NC Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''issues / non conformities'' can be filtered and exported to excel format from the ''view'' '''''Issues / Non Conformities'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'', ''Privacy Impact Assessment'' and ''Risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=577</id>
		<title>Issues &amp; Non Conformities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=577"/>
				<updated>2018-10-10T09:54:16Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Issues / Non Conformities ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''issue / non conformity'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Issue or Non Conformity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The workflow enables to move ''issues / non conformities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Issues_non_Conformities_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Issues / non conformities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''issue / non conformity'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Draft || An ''issue / non conformity'' in this status is draft and it is not actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || An ''issue / non conformity'' in this status is confirmed and it is actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Issue / non conformity'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|Completed || In this status, all activities related to the ''issue / non conformity'' were completed and closure is expected after confirmation.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, all activities related to the ''issue / non conformity'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Issue / non conformity'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''issue / non conformity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''issue / non conformity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Issue / Non Conformity Details''&amp;lt;/u&amp;gt;, with the details of the ''issue / non conformity''.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Issue / non conformity'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Protection Officer Group (DPO) Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditor Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Issue / NC Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''issues / non conformities'' can be filtered and exported to excel format from the ''view'' '''''Issues / Non Conformities'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'', ''Privacy Impact Assessment'' and ''Risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=576</id>
		<title>Issues &amp; Non Conformities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Issues_%26_Non_Conformities&amp;diff=576"/>
				<updated>2018-10-10T09:51:03Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Issues / Non Conformities ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''issue / non conformity'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Issue or Non Conformity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The workflow enables to move ''issues / non conformities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Issues_non_Conformities_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Issues / non conformities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''issue / non conformity'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Draft || An ''issue / non conformity'' in this status is draft and it is not actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || An ''issue / non conformity'' in this status is confirmed and it is actioned.&lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Issue / non conformity'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|Completed || In this status, all activities related to the ''issue / non conformity'' were completed and closure is expected after confirmation.&lt;br /&gt;
|-&lt;br /&gt;
|Closed || In this status, all activities related to the ''issue / non conformity'' are completed and confirmed. This is an end of life status, meaning no further status transitions are allowed.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Issue / non conformity'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''issue / non conformity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''issue / non conformity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Issue / Non Conformity Details''&amp;lt;/u&amp;gt;, with the details of the ''issue / non conformity''.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Issue / non conformity'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Audit Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Issue / NC Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''groups'' previously described. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''issues / non conformities'' can be filtered and exported to excel format from the ''view'' '''''Issues / Non Conformities'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Issues / non conformities'' can be related to ''actions'', ''audits'' , ''data breaches'', ''Privacy Impact Assessment'' and ''Risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Knowledge_Items&amp;diff=575</id>
		<title>Knowledge Items</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Knowledge_Items&amp;diff=575"/>
				<updated>2018-10-10T09:32:12Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Workflow */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Knowledge Items ==&lt;br /&gt;
''Knowledge items'' provide the mean to publish useful information and knowledge to specific audiences.&lt;br /&gt;
&lt;br /&gt;
The workflow enables to record ''knowledge items'' and to support their lifecycle (publish / unpublish).&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''knowledge item'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Knowledge Item&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''knowledge items'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Knowledge_Items_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Knowledge items workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''knowledge item'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Draft || A ''knowledge item'' in this status is draft and not visible yet to its target audience.&lt;br /&gt;
|-&lt;br /&gt;
|Published || A ''knowledge item'' in this status is published and visible to its target audience. The target audience is the ''group'' set in the ''knowledge item'' &amp;lt;u&amp;gt;Publisher&amp;lt;/u&amp;gt; field.&lt;br /&gt;
|-&lt;br /&gt;
|Dismissed || A ''knowledge item'' in this status is no longer visible and cannot be updated. This is an end of life status. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Knowledge items'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''knowledge item'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Publisher&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Readers&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''knowledge items'' can be filtered and exported to excel format from the ''view'' '''''knowledge items'''''.&lt;br /&gt;
&lt;br /&gt;
== Visibility of Knowledge Items and Knowledge Portal ==&lt;br /&gt;
&lt;br /&gt;
''Knowlegde items'' are published and visibile in the ''knowledge portal'', accessible from '''''Knowledge Portal''''' menu. Note that ''knowledge items'' are visible in the ''knowledge portal'' to ''users'' who are members of the ''group'' they are published to.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=574</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=574"/>
				<updated>2018-10-10T09:18:43Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Consents#Configuration of consents sources|Configuration of consents sources]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set (manually or automatically by an external system) when ……………TBC..&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Consents'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Four levels of warning are foreseen.&lt;br /&gt;
How to set them....&lt;br /&gt;
How to configure related messages...&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Configuration of consents sources ==&lt;br /&gt;
TBC&lt;br /&gt;
Process&lt;br /&gt;
Structure of the incoming email&lt;br /&gt;
Matching criterias&lt;br /&gt;
&lt;br /&gt;
== Removal of consents ==&lt;br /&gt;
&lt;br /&gt;
=== Removal of single consent records ===&lt;br /&gt;
&lt;br /&gt;
=== Bulk removal of consent records ===&lt;br /&gt;
&lt;br /&gt;
TBC&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=573</id>
		<title>Consents</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Consents&amp;diff=573"/>
				<updated>2018-10-10T09:09:55Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Introduction to Consents */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Consents ==&lt;br /&gt;
Consents management provide the mean to acquire, update and use ''consents'' information. For example, it is possible to use Privacy Now® as a central repository of information about all the ''consents''. Information about ''consents'' can be created and updated manually or interfacing Privacy Now® with external system. See the paragraph [[Consents#Configuration of consents sources|Configuration of consents sources]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''consent'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Consent&amp;quot;. Alternatively, a new ''consent'' can be automatically acquired or updated by an external system.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''consents'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Consents_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Consents workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''consent'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Valid || A ''consent'' in this status is valid and its information can be used accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|Wrong email || This status is set (manually or automatically by an external system) when ……………TBC..&lt;br /&gt;
|-&lt;br /&gt;
|Expired || In this status a ''consent'' is expired and therefore should be removed.&lt;br /&gt;
|-&lt;br /&gt;
|To be Removed || In this status, the ''consent'' shall be removed (the status is used to identify ''consents'' by the automatic removal procedure).&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Consent'' records are organized in three sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''consent'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''consent'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Consent Details''&amp;lt;/u&amp;gt;, with the details of the ''consent'';&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Consents'' can be automatically created by authorized external systems or by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
The lifecycle of the ''consent'' 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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have several privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Audit Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
However, some steps may be performed automatically (see the paragraph dedicated to [[Consents#Warning and alerts|warning and alerts]]).&lt;br /&gt;
&lt;br /&gt;
== Warning and alerts ==&lt;br /&gt;
Four levels of warning are foreseen.&lt;br /&gt;
How to set them....&lt;br /&gt;
How to configure related messages...&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''consents'' can be filtered and exported to excel format from the ''view'' '''''Consents'''''.&lt;br /&gt;
&lt;br /&gt;
== Configuration of consents sources ==&lt;br /&gt;
TBC&lt;br /&gt;
Process&lt;br /&gt;
Structure of the incoming email&lt;br /&gt;
Matching criterias&lt;br /&gt;
&lt;br /&gt;
== Removal of consents ==&lt;br /&gt;
&lt;br /&gt;
=== Removal of single consent records ===&lt;br /&gt;
&lt;br /&gt;
=== Bulk removal of consent records ===&lt;br /&gt;
&lt;br /&gt;
TBC&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Glossary&amp;diff=572</id>
		<title>Glossary</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Glossary&amp;diff=572"/>
				<updated>2018-10-05T12:32:33Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* S */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below is a list of terms and definitions used in this documentation.&lt;br /&gt;
&lt;br /&gt;
== A ==&lt;br /&gt;
* ''AC'': see Actions&lt;br /&gt;
* ''AR'': see Access Requests.&lt;br /&gt;
* ''Access Request'': a record which allows to manage the lifecycle of a request to access information on how ''personal data'' are managed by a data subject. A specific workflow in Privacy-Now® supports the lifecycle of ''access requests'' (see [[Access Requests]]). &lt;br /&gt;
* ''Action'': any activity performed by the ''organization'' in order to manage any other process supported by Privacy Now® (i.e. access requests, audits, consents, data breaches, issues, non conformities, privacy impact assessments, records of processing activities). Privacy Now® allows to record and support the lifecycle of ''actions'' with a specific workflow (see [[Actions]]).&lt;br /&gt;
* ''AU'': see Audit.&lt;br /&gt;
* ''Audit'': an inspection, either made by internal, external or independent resources (see ''auditors'') aimed at checking the status of ''personal data'' management system and activities. Privacy Now® supports audit activities with a specific workflow (see [[Audits]]).&lt;br /&gt;
* ''Auditor'': any resource, internal or external of an organization with auditing responsibilities on ''personal data'' management.&lt;br /&gt;
&lt;br /&gt;
== B ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== C ==&lt;br /&gt;
*''CO'': see Consents.&lt;br /&gt;
*''Consent'': the authorization (or denial) to manage ''personal data'' given by a ''data subject''. In Privacy-Now® ''consents'' lifecycle is supported by the consent management workflow (see [[Consents]] for more information).&lt;br /&gt;
&lt;br /&gt;
== D ==&lt;br /&gt;
* ''Dashboard'': an information management tool that visually tracks, analyzes and displays key performance indicators (KPI), metrics and key data points to monitor the health of ''privacy management processes''.&lt;br /&gt;
* ''DB'': see Data Breaches.&lt;br /&gt;
* ''Data breach'': a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed.&lt;br /&gt;
* ''Data controller'': means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data.&lt;br /&gt;
* ''Data subject'': a ''natural person'' whose personal data are managed by the ''organization''.&lt;br /&gt;
* ''Data Protection Impact Assessment'': an assessment designed to help an organization to assess the risks associated with data processing activities that could compromise the rights and freedoms of individuals. In Privacy-Now® ''data protection impact assessments'' are managed using the ''privacy impact assessment'' workflow (see [[Privacy Impact Assessments]]).&lt;br /&gt;
* ''Data Protection Officer'': a data protection officer is an enterprise security leadership role required by the General Data Protection Regulation (GDPR). Data protection officers are responsible for overseeing data protection strategy and implementation to ensure compliance with GDPR requirements.&lt;br /&gt;
* ''Data Processor'': means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller.&lt;br /&gt;
* ''DPIA'': see ''data protection impact assessment''.&lt;br /&gt;
* ''DPO'': see ''Data Protection Officer''.&lt;br /&gt;
&lt;br /&gt;
== E ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== F ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== G ==&lt;br /&gt;
* ''Group'': a set of people which can be assigned to a profile to grant specific privileges to manage a process (e.g. ''Actions'' management). See [[Users &amp;amp; Groups]] for more information on how to manage ''groups''.&lt;br /&gt;
&lt;br /&gt;
== H ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== I ==&lt;br /&gt;
* ''INC'': see Issues &amp;amp; Non Conformities.&lt;br /&gt;
* ''Issue'': an important topic or problem for debate or discussion related to ''personal data management''. A specific workflow in Privacy-Now® supports the lifecycle of ''issues'' (See [[Issues &amp;amp; Non Conformities]]).&lt;br /&gt;
&lt;br /&gt;
== K ==&lt;br /&gt;
* ''Knowledge item'': a piece of information or a knowledge record concerning the protection of ''personal data''. ''Knowledge items'' can be added and managed by the ''users'' but some are by the team of Privacy-Now® and cannot be edited by the ''users''.&lt;br /&gt;
* ''Knowledge portal'': a functionality of Privacy-Now® which presents ''knowledge items'' organized in categories. In the portal, ''knowledge items'' are visible to the members of the ''group'' they are published to.&lt;br /&gt;
&lt;br /&gt;
== L ==&lt;br /&gt;
* ''Login'': TBC&lt;br /&gt;
&lt;br /&gt;
== M ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== N ==&lt;br /&gt;
* ''Non conformity'': a deviation from the agreed policies and/or ''personal data'' management processes and procedures. A specific workflow in Privacy-Now® supports the lifecycle of ''non conformities'' (See [[Issues &amp;amp; Non Conformities]]).&lt;br /&gt;
&lt;br /&gt;
== O ==&lt;br /&gt;
* ''Organization'': the organisation using Privacy Now® to manage ''data subjects''' ''personal data''.&lt;br /&gt;
&lt;br /&gt;
== P ==&lt;br /&gt;
* ''PA'': see Processing Activities.&lt;br /&gt;
* ''Personal data'': it means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.&lt;br /&gt;
* ''Personal data breach'': see ''data breach''.&lt;br /&gt;
* ''PIA'': see ''Privacy Impact Assessment''.&lt;br /&gt;
* ''Privacy Impact Assessment'': a systematic process which identifies and evaluates from the perspectives of all stakeholders the potential effects on privacy of a project, initiative or proposed system or scheme and which includes a search for ways to avoid or mitigate negative privacy impacts. In Privacy-Now®, ''privacy impact assessment'' are focused to assess the impact on ''processing activities'' (see ''data protection impact assessment'').&lt;br /&gt;
* ''Privacy management processes'': the processes and corresponding workflows automated by Privacy-Now® and aimed to support effective and efficient ''personal data'' management to achieve compliance against policies and regulations.&lt;br /&gt;
* ''Processing activities'': means any operation or set of operations which is performed on ''personal data'' or on sets of ''personal data'', whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. Privacy Now® supports ''processing activities'' lifecycle with a specific workflow (see [[Processing Activities]]).&lt;br /&gt;
&lt;br /&gt;
== Q ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== R ==&lt;br /&gt;
* ''RI'': see Risks.&lt;br /&gt;
* ''Risks'': TBD&lt;br /&gt;
&lt;br /&gt;
== S ==&lt;br /&gt;
* ''Save &amp;amp; Next'': basic function of the system that enable the ''User'' to save the ticket information and move the ticket status to the Next one. If more than one status is possible the ''User'' has to select the final status to be reach.&lt;br /&gt;
* ''Settings'': settings which can be updated for Privacy Now® service.&lt;br /&gt;
&lt;br /&gt;
== T ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== U ==&lt;br /&gt;
* ''User'': users of Privacy Now®.&lt;br /&gt;
&lt;br /&gt;
== V ==&lt;br /&gt;
&lt;br /&gt;
* ''View'': a list of records concerning a specific ''privacy management process''. It is possible to access to ''views'' from the left menu of the application. See also [[How To]] for more information on how to use ''views''.&lt;br /&gt;
&lt;br /&gt;
== X ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Y ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Z ==&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=571</id>
		<title>Processing Activities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=571"/>
				<updated>2018-10-05T10:57:12Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Processing Activities ==&lt;br /&gt;
''Processing activities'' are the core element of ''personal data'' management. Many regulations require to document and assess them. &lt;br /&gt;
&lt;br /&gt;
Privacy-Now® dedicated process enables to record ''processing activities'', to maintain them and to use them for assessment or other tasks related to ''personal data'' management.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''processing activity'' can be created using the ''Add New'' functionality and choosing &amp;quot;New Processing Activity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move the ''processing activities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Processing Activities Workflow ENG v1.0.JPG|centre|thumb|800x800px|Processing activities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''processing activity'' is initially created before the first save. &lt;br /&gt;
|-&lt;br /&gt;
|Draft || A ''processing activity'' in this status is draft.&lt;br /&gt;
|-&lt;br /&gt;
|Active || A ''processing activity'' in this status is actually executed by the ''organization''.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Processing activity'' cancelled. It is still possible to recover a ''processing activity'' from this status by enabled ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Processing activities'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''processing activity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Characteristics''&amp;lt;/u&amp;gt;, with the key attributes of the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Information Technology''&amp;lt;/u&amp;gt;, with information about the technologies used to process ''personal data'' by the ''processing activivty''.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Processing activities'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management,&lt;br /&gt;
* revert from &amp;quot;Cancelled&amp;quot; status.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Audit Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Representative&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''DPO group'' or the ''Data Controller Group''. The &amp;lt;u&amp;gt;Representative&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''processing activities'' can be filtered and exported to excel format from the ''view'' '''''Processing Activities'''''.&lt;br /&gt;
&lt;br /&gt;
Finally, it is possible to print the ''processing activity'' card using the '''Print''' command positioned up right in the ''&amp;lt;u&amp;gt;General&amp;lt;/u&amp;gt;'' form of the ''processing activity'' record.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
Many other entities can be related to ''processing activity'' records, in particular:&lt;br /&gt;
* ''access requests'',&lt;br /&gt;
* ''actions'',&lt;br /&gt;
* ''impact assessments'',&lt;br /&gt;
* ''risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=570</id>
		<title>Processing Activities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=570"/>
				<updated>2018-10-05T10:55:10Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Processing Activities ==&lt;br /&gt;
''Processing activities'' are the core element of ''personal data'' management. Many regulations require to document and assess them. &lt;br /&gt;
&lt;br /&gt;
Privacy-Now® dedicated process enables to record ''processing activities'', to maintain them and to use them for assessment or other tasks related to ''personal data'' management.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''processing activity'' can be created using the ''Add New'' functionality and choosing &amp;quot;New Processing Activity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move the ''processing activities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Processing Activities Workflow ENG v1.0.JPG|centre|thumb|800x800px|Processing activities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''processing activity'' is initially created before the first save. &lt;br /&gt;
|-&lt;br /&gt;
|Draft || A ''processing activity'' in this status is draft.&lt;br /&gt;
|-&lt;br /&gt;
|Active || A ''processing activity'' in this status is actually executed by the ''organization''.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Processing activity'' cancelled. It is still possible to recover a ''processing activity'' from this status by enabled ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Processing activities'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''processing activity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Characteristics''&amp;lt;/u&amp;gt;, with the key attributes of the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Information Technology''&amp;lt;/u&amp;gt;, with information about the technologies used to process ''personal data'' by the ''processing activivty''.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Processing activities'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management,&lt;br /&gt;
* revert from &amp;quot;Cancelled&amp;quot; status.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Audit Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Representative&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''DPO group'' or the ''Data Controller Group''. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''processing activities'' can be filtered and exported to excel format from the ''view'' '''''Processing Activities'''''.&lt;br /&gt;
&lt;br /&gt;
Finally, it is possible to print the ''processing activity'' card using the '''Print''' command positioned up right in the ''&amp;lt;u&amp;gt;General&amp;lt;/u&amp;gt;'' form of the ''processing activity'' record.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
Many other entities can be related to ''processing activity'' records, in particular:&lt;br /&gt;
* ''access requests'',&lt;br /&gt;
* ''actions'',&lt;br /&gt;
* ''impact assessments'',&lt;br /&gt;
* ''risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=569</id>
		<title>Processing Activities</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Processing_Activities&amp;diff=569"/>
				<updated>2018-10-05T10:54:41Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Processing Activities ==&lt;br /&gt;
''Processing activities'' are the core element of ''personal data'' management. Many regulations require to document and assess them. &lt;br /&gt;
&lt;br /&gt;
Privacy-Now® dedicated process enables to record ''processing activities'', to maintain them and to use them for assessment or other tasks related to ''personal data'' management.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''processing activity'' can be created using the ''Add New'' functionality and choosing &amp;quot;New Processing Activity&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move the ''processing activities'' in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Processing Activities Workflow ENG v1.0.JPG|centre|thumb|800x800px|Processing activities workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''processing activity'' is initially created before the first save. &lt;br /&gt;
|-&lt;br /&gt;
|Draft || A ''processing activity'' in this status is draft.&lt;br /&gt;
|-&lt;br /&gt;
|Active || A ''processing activity'' in this status is actually executed by the ''organization''.&lt;br /&gt;
|-&lt;br /&gt;
|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. &lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Processing activity'' cancelled. It is still possible to recover a ''processing activity'' from this status by enabled ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Processing activities'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''processing activity'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Characteristics''&amp;lt;/u&amp;gt;, with the key attributes of the ''processing activity'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Information Technology''&amp;lt;/u&amp;gt;, with information about the technologies used to process ''personal data'' by the ''processing activivty''.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Processing activities'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management,&lt;br /&gt;
* revert from &amp;quot;Cancelled&amp;quot; status.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Audit Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Owner&amp;lt;/u&amp;gt; || This role can be assigned to a single user among members of the ''DPO group'' or the ''Data Controller Group''. The &amp;lt;u&amp;gt;Owner&amp;lt;/u&amp;gt; has several privileges:&lt;br /&gt;
* transition to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''processing activities'' can be filtered and exported to excel format from the ''view'' '''''Processing Activities'''''.&lt;br /&gt;
&lt;br /&gt;
Finally, it is possible to print the ''processing activity'' card using the '''Print''' command positioned up right in the ''&amp;lt;u&amp;gt;General&amp;lt;/u&amp;gt;'' form of the ''processing activity'' record.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
Many other entities can be related to ''processing activity'' records, in particular:&lt;br /&gt;
* ''access requests'',&lt;br /&gt;
* ''actions'',&lt;br /&gt;
* ''impact assessments'',&lt;br /&gt;
* ''risks''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=568</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=568"/>
				<updated>2018-10-05T08:59:38Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Search */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit from the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the record in the destination status (if a reload of the record data is done, the status will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or manage attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. However, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Two main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=567</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=567"/>
				<updated>2018-10-05T08:46:58Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Delete */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit from the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the record in the destination status (if a reload of the record data is done, the status will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or manage attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. However, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=566</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=566"/>
				<updated>2018-10-05T08:40:30Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit from the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the record in the destination status (if a reload of the record data is done, the status will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or manage attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=565</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=565"/>
				<updated>2018-10-05T08:07:58Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit from the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the record in the destination status (if a reload of the record data is done, the status will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=564</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=564"/>
				<updated>2018-10-05T08:02:35Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit from the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the record in the destination status (if a reload of the record data is done, the status will will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=563</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=563"/>
				<updated>2018-10-05T07:58:26Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit from the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the the record in the destination status (if a reload of the record data is done, the status will will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=562</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=562"/>
				<updated>2018-10-05T07:42:26Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Update */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functionalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit form the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the the record in the destination status (if a reload of the record data is done, the status will will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=561</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=561"/>
				<updated>2018-10-05T07:15:19Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Menus and Views */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected records list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functinoalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit form the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the the record in the destination status (if a reload of the record data is done, the status will will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Audits&amp;diff=560</id>
		<title>Audits</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Audits&amp;diff=560"/>
				<updated>2018-09-28T15:24:31Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Privileges */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Introduction to Audits ==&lt;br /&gt;
''Audits'' provide a control mechanism over ''personal data'' management system and activities. &lt;br /&gt;
&lt;br /&gt;
The process enables to record ''audits'' information and to support their fulfilment.&lt;br /&gt;
&lt;br /&gt;
== Workflow ==&lt;br /&gt;
A new ''audit'' can be created using the '''Add New''' functionality and choosing &amp;quot;New Audit&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
A workflow enables to move ''audits&amp;quot; in several statuses as shown in the following picture.&lt;br /&gt;
&lt;br /&gt;
[[File:Audits_Workflow_ENG_v1.0.JPG|centre|thumb|800x800px|Audits workflow and statuses.]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The following table explains the meaning of each status:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Status !! Description&lt;br /&gt;
|-&lt;br /&gt;
|Default || A temporary status when the ''audit'' is initially created before the first save.&lt;br /&gt;
|-&lt;br /&gt;
|Opened || An ''audit'' in this status is draft and it is not actioned yet.&lt;br /&gt;
|-&lt;br /&gt;
|Planned || An ''audit'' in this status is planned for execution.&lt;br /&gt;
|-&lt;br /&gt;
|In progress || In this status, the ''audit'' is in progress. &lt;br /&gt;
|-&lt;br /&gt;
|Completed || In this status, all activities related to the ''audit'' were completed and closure is expected after confirmation.&lt;br /&gt;
|-&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|Cancelled || ''Audit'' cancelled. This is an end of life status.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Information ==&lt;br /&gt;
''Audit'' records are organized in four sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;, where identification data of the ''audit'' are recorded,&lt;br /&gt;
* &amp;lt;u&amp;gt;''Ownership &amp;amp; Organization''&amp;lt;/u&amp;gt;, containing the assignment of the key roles enabled to manage the ''audit'';&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;, with the details of the ''audit'' to accomplish;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Results''&amp;lt;/u&amp;gt;, with the conclusions of the ''audit''.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Additional information can be found in the secondary forms of the record: attachments, related items, messages and history. See [[How To]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Privileges ==&lt;br /&gt;
''Audit'' can be created by the ''users'' to whom the corresponding privilege is granted (see [[Users &amp;amp; Groups]] for more information on how to set this privilege).&lt;br /&gt;
&lt;br /&gt;
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'').&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Role !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;DPO Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have full privileges. They can:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible,&lt;br /&gt;
* update ''data sources'' directly in record management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Controller Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Data Processor Group&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Working Team&amp;lt;/u&amp;gt; || Members of this ''group'' have several privileges. They can manage the entire lifecycle, being enabled to:&lt;br /&gt;
* transition records to any compatible status,&lt;br /&gt;
* update fields when possible.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;Auditors Supervisory Team&amp;lt;/u&amp;gt; || Members of the ''group'' assigned to this role have view (read) privileges.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
The list of ''audits'' can be filtered and exported to excel format from the ''view'' '''''audits'''''.&lt;br /&gt;
&lt;br /&gt;
== Related processes ==&lt;br /&gt;
''Audits'' can be related to ''risks'' and ''issues / non conformities''.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=559</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=559"/>
				<updated>2018-09-27T15:50:23Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the Overview ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected recors list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functinoalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit form the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the the record in the destination status (if a reload of the record data is done, the status will will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=558</id>
		<title>How To</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=How_To&amp;diff=558"/>
				<updated>2018-09-27T15:48:24Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section of Privacy-Now® guide introduces how to use the main functionalities of the tool.&lt;br /&gt;
&lt;br /&gt;
== Dashboards ==&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are automatically presented when logging to the system for the first time. The following ''dashboards'' are available:&lt;br /&gt;
&lt;br /&gt;
* Privacy Overview&lt;br /&gt;
* ''Access Requests''&lt;br /&gt;
* ''Actions''&lt;br /&gt;
* ''Audits''&lt;br /&gt;
* ''Consents''&lt;br /&gt;
* ''Data Breaches''&lt;br /&gt;
* ''Issues / Non Conformities''&lt;br /&gt;
* ''Privacy Impact Assessments''&lt;br /&gt;
* ''Processing Activities''&lt;br /&gt;
* ''Risks''&lt;br /&gt;
&lt;br /&gt;
Apart from the General ''dashboard'', which presents information from several processes, each ''dashboard'' is dedicated to a ''privacy management process''.&lt;br /&gt;
&lt;br /&gt;
''Dashboards'' are composed of widgets (see the figure below).&lt;br /&gt;
&lt;br /&gt;
[[File:Dashboard_Widget_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''dashboard'' widget.]]&lt;br /&gt;
&lt;br /&gt;
Widgets are generally configured to be interactive. Clicking on a part of the widget with the left mouse button opens a context menu which presents the following options:&lt;br /&gt;
&lt;br /&gt;
- '''Open Ticket List''', allowing to open a list of the records which correspond to the result clicked in the widget;&lt;br /&gt;
&lt;br /&gt;
- '''Break Down''', allowing to drill down into the shown dimension;&lt;br /&gt;
&lt;br /&gt;
- '''Back''', allowing to return to the upper dimension from which the drill down was done.&lt;br /&gt;
&lt;br /&gt;
Depending on the subscribed packaged, ''dashboards'' can be directly created or configured by ''users''. However, the guide to customize them is not included in this wiki.&lt;br /&gt;
Additionally, ''Dashboards'' are continuously improved and clients suggestions are welcome to this aim.&lt;br /&gt;
&lt;br /&gt;
Finally, remember that the trial subscription has limited access to the '''dashboards'''.&lt;br /&gt;
&lt;br /&gt;
== Menus and Views ==&lt;br /&gt;
Menu items are accessible from the left menu bar of the and they may launch functionalities or ''views''.&lt;br /&gt;
&lt;br /&gt;
[[File:View_ENG_v1.0.JPG|centre|thumb|800x800px|Example of ''view''.]]&lt;br /&gt;
&lt;br /&gt;
In ''views'' records can be sorted with column headers and paged with paging commands.&lt;br /&gt;
&lt;br /&gt;
It is also possible to filter data. Pressing on the magnifier icon activates the grid filtering fields. They work logically in AND and they filter the records in ''view''. The '''GO''' command activates the entered criteria and the '''RESET''' command removes them.&lt;br /&gt;
&lt;br /&gt;
'''PRINT''' prints the selected (using tick boxes column) records cards. A new browser window is opened for each card. '''PRINT LIST''' prints the selected recors list. '''EXPORT TO EXCEL''' export the selected data in Excel format.&lt;br /&gt;
&lt;br /&gt;
== News ==&lt;br /&gt;
News is a service functionality used by Privacy Now®  staff to publish information about the service. Typical information may be announcements of new features or information on maintenance windows or service issues. News are scrolling titles in the news box positioned after below the left application menu. Just click on a scrolling news to access its detailed content.&lt;br /&gt;
&lt;br /&gt;
== Records Management ==&lt;br /&gt;
&lt;br /&gt;
=== Create ===&lt;br /&gt;
Creating new records, including ''users'', is done by accessing and navigating the '''''Add New''''' menu item.&lt;br /&gt;
&lt;br /&gt;
[[File:Add_New_Self_Service_ENG_v1.0.JPG|centre|thumb|800x800px|Self service area to add new records.]]&lt;br /&gt;
&lt;br /&gt;
Just click on the item you want to create and this opens a dialog box where you can enter the related description or just press '''Create''' to generate a new record. Press ''Close'' to exit without creating.&lt;br /&gt;
&lt;br /&gt;
=== Update ===&lt;br /&gt;
&lt;br /&gt;
Updating a record can be done immediately after creating it or later when saved. See [[How_To#Search|Search]] section for more information on how to search existing records. &lt;br /&gt;
&lt;br /&gt;
When focused on a record, the command bars allow to save it and additional tasks on the record:&lt;br /&gt;
&lt;br /&gt;
* '''Save''' - simply saves the record;&lt;br /&gt;
* '''Save &amp;amp; Exit''' - saves the record and exits from the update form;&lt;br /&gt;
* '''Save &amp;amp; Next''' - this command first performs a save and then immediately enables to move the record to the next desired step in the workflow;&lt;br /&gt;
* '''Cancel''' - exits from the record without saving (unsaved updates will be lost);&lt;br /&gt;
* '''Reload''' - reloads the record (unsaved updates will be lost);&lt;br /&gt;
* '''Print''' - prints the record;&lt;br /&gt;
* ''' Quick Actions''': enables a context menu showing some shortcuts for commands enabling functinoalities.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Update_Record_v1.0.JPG|centre|thumb|800x800px|Record update screen.]]&lt;br /&gt;
&lt;br /&gt;
When saving, remember to update all mandatory fields which are marked with a red asterisk in the form. If some mandatory content is missing, the system will warn by showing a textual message before the update form where the missing fields are reported. The ''User'' will then have the possibility to update and save again.&lt;br /&gt;
&lt;br /&gt;
'''Save &amp;amp; Next''' command opens a dialog form to choose the workflow transition to perform (and therefore the target status).&lt;br /&gt;
&lt;br /&gt;
[[File:SaveNext_v1.0.JPG|centre|thumb|800x800px|'''Save&amp;amp;Next''' dialog form.]]&lt;br /&gt;
&lt;br /&gt;
In the dialog form, the ''user'' shall select the transition to perform and the command to execute:&lt;br /&gt;
&lt;br /&gt;
* '''Cancel''' - to exit form the form without executing any transition;&lt;br /&gt;
* '''Apply''' - to execute the selected transition without saving the record in the destination status (if a reload of the record data is done before saving, the status will remain unchanged);&lt;br /&gt;
* '''Apply &amp;amp; Save''' - to execute the selected transition and save the the record in the destination status (if a reload of the record data is done, the status will will be the target one).&lt;br /&gt;
&lt;br /&gt;
Note that the '''Apply &amp;amp; Save''' command won't be enabled if mandatory fields are missing to save the record in the target status. In such a case, use the '''Apply''' command, fill the missing values and then save the record.&lt;br /&gt;
&lt;br /&gt;
In the ''Save &amp;amp; Next'' dialog box by clicking the &amp;lt;u&amp;gt;Transition Comment&amp;lt;/u&amp;gt; tick box it is possible to enter a comment for the transition (e.g. the reason to perform it) which will be visibile in the history of the record.&lt;br /&gt;
&lt;br /&gt;
If the ''user'' is lost and doesn't know how to proceed (which are the next posible workflow statuses), the ''Explore Workflow'' command will help by opening the explorer workflow window (see the figure above).&lt;br /&gt;
&lt;br /&gt;
In this window, the workflow is graphically presented. Each rectangle represents a workflow status and arrows connect possible transitions. The current status is yellow, the past ones grey, the target ones red (if the ''user'' hasn't privileges on a transition needed to move the record in the target status) or green (if the ''user'' has the privileges to execute a transition moving the record to the target status). The form is interactive:&lt;br /&gt;
&lt;br /&gt;
* the ''user'' can see details about the roles and resources enabled to perform a transition by clicking on the &amp;lt;u&amp;gt;details&amp;lt;/u&amp;gt; label on the same transition;&lt;br /&gt;
* the ''user'' can recall the ''Save &amp;amp; Next'' dialog box by double clicking with the left mouse button on a green status (this will start the dialog box with a preselected transition).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the record, the ''user'' can move to the different content form by using the form selector (see the figure above). Depending on the type of record and the privileges of the 'user'', the visible form are:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; - containing the main information of the records;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Attachments''&amp;lt;/u&amp;gt; - allowing to view or mange attachments;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Related Items''&amp;lt;/u&amp;gt; - allowing to view and manage related records (e.g. ''risks'' related to a ''processing activity'');&lt;br /&gt;
* &amp;lt;u&amp;gt;''Messages''&amp;lt;/u&amp;gt; - allowing to view and manage messages (mails) which will remain related to the record;&lt;br /&gt;
* &amp;lt;u&amp;gt;''History''&amp;lt;/u&amp;gt; - showing the history of the changes performed for the record.&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
''Privacy management processes'' are designed with end of life statuses for records (e.g. cancellation or completion). Therefore, the physical cancellation of records should not be necessary. however, should there be a reason to physically delete a record, this is possible for ''users'' with administrative privileges from the settings management. Go to [[Settings]] for more information on how to deleted specific records.&lt;br /&gt;
&lt;br /&gt;
== Reports ==&lt;br /&gt;
Available reports are accessible from the left application menu or via command buttons in the records.&lt;br /&gt;
&lt;br /&gt;
A main source for reporting is the export to excel functionality present in all ''views'' of data (see [[How_To#Menus_and_Views|Views]]). &lt;br /&gt;
&lt;br /&gt;
Additionally, ''dashboards'' are available (see [[How_To#Dashboards|Dashboards]]).&lt;br /&gt;
&lt;br /&gt;
== Search ==&lt;br /&gt;
Teo main mechanisms support the search for record and information.&lt;br /&gt;
&lt;br /&gt;
* search tool;&lt;br /&gt;
* views and grid filtering.&lt;br /&gt;
&lt;br /&gt;
=== Search tool ===&lt;br /&gt;
The search tool is positioned in the top right corner of the application and it is shown in the picture below.&lt;br /&gt;
&lt;br /&gt;
[[File:Search_ENG_v1.0.JPG|centre|thumb|800x800px|Search tool.]]&lt;br /&gt;
&lt;br /&gt;
Before starting to search, it is necessary to set the search context among one of the possible values: &amp;quot;Text&amp;quot; or &amp;quot;Ticket&amp;quot;. By default, &amp;quot;Ticket&amp;quot; is set if no value is entered.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Ticket&amp;quot; search context assumes that the ''user'' is trying to access a record directly, by knowing its id (code). Therefore, just enter the id and press enter or the magnifier icon. If the corresponding record exists and the ''user'' has privileges to view it, the system will directly open the record form.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Text&amp;quot; search context assumes that the ''user'' is searching a string text. Therefore, just enter the text and press enter or the magnifier icon. The system will present the list of the records where the text is found and the ''user'' will be able to access any by clicking on the list.&lt;br /&gt;
&lt;br /&gt;
=== Views and grid filtering ===&lt;br /&gt;
By accessing and filtering views, it is possible to search and access records. See [[How_To#Menus_and_Views|Views]] for more information.&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=557</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=557"/>
				<updated>2018-09-27T14:48:19Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Add group */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item lists the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add New''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges as the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=556</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=556"/>
				<updated>2018-09-27T14:04:15Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Groups Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item lists the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add New''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=555</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=555"/>
				<updated>2018-09-27T13:24:38Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Groups Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item lists the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add Group''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=554</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=554"/>
				<updated>2018-09-27T13:20:13Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Groups Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item lists the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller]]'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add Group''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=553</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=553"/>
				<updated>2018-09-27T13:18:52Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Groups Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item list the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller]]'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add Group''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=552</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=552"/>
				<updated>2018-09-27T13:03:02Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Users Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group Management''&amp;lt;/b&amp;gt; menu item list the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller]]'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add Group''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=551</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=551"/>
				<updated>2018-09-27T13:00:50Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Users Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group Management''&amp;lt;/b&amp;gt; menu item list the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller]]'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add Group''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	<entry>
		<id>http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=550</id>
		<title>Users &amp; Groups</title>
		<link rel="alternate" type="text/html" href="http://wiki.privacy-now.eu/en/index.php?title=Users_%26_Groups&amp;diff=550"/>
				<updated>2018-09-27T12:59:15Z</updated>
		
		<summary type="html">&lt;p&gt;Cbisso: /* Users Management */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Users Management==&lt;br /&gt;
New ''users'' can be created using '''''Add New''''' and choosing '''New User''' in the self service menu. &lt;br /&gt;
Existing ''users'' can be update selecting &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Users Management''&amp;lt;/b&amp;gt; menu and selecting the record to manage from the list.&lt;br /&gt;
Access to ''users'' creation and administration is limited to ''users'' having administrative role (see later).&lt;br /&gt;
&lt;br /&gt;
''Users'' shall be activated (in status &amp;quot;Active&amp;quot;) to be operational. In other statuses, ''users'' are not active (they cannot login into Privacy-Now®) nor they are counted as licensed ''users''.&lt;br /&gt;
&lt;br /&gt;
''Users'' information are organized in five sections:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;&lt;br /&gt;
* &amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; || Unique ''user'' identifier, automatically created by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Tracking''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Project/Service&amp;lt;/u&amp;gt; || Environment identifier, corresponding to the organization owner of Privacy-Now® subscription and automatically managed by the system.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Type&amp;lt;/u&amp;gt; || Record type identifier, automatically managed by the system. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Identification''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Ticket Op Status&amp;lt;/u&amp;gt; || Status of the ''user''. Possible statuses are &amp;quot;Inactive&amp;quot; (when initially created) or ''Active''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; || Name of the ''user''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Surname&amp;lt;/u&amp;gt; || Surname of the ''user''&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Username&amp;lt;/u&amp;gt; || Login name used to access Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Email&amp;lt;/u&amp;gt; || Email of the ''user''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Admin&amp;lt;/u&amp;gt; || This field may have two possible values &amp;quot;Yes&amp;quot; or &amp;quot;No&amp;quot;. If set to &amp;quot;Yes&amp;quot; the ''user'' has administrative privileges and can perform special tasks such as ''users'' and ''groups'' administration but also manage [[Settings#Introduction|settings]].&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Language&amp;lt;/u&amp;gt; || The application interface language set for the ''user''. Supported languages are currently &amp;quot;English&amp;quot;, &amp;quot;French&amp;quot; and &amp;quot;Italian&amp;quot;. &amp;quot;Spanish&amp;quot; will come next.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Details''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Timezone&amp;lt;/u&amp;gt; || The time zone of the ''user'' who will see time accordingly.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Access Request Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''access requests''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Action Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''actions''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Audit Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''audits''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;s|| &amp;lt;u&amp;gt;Consent Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''consents''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Data Breach Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''data breaches''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Privacy Impact Assessment Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''privacy impact assessments''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Issue / NC Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''issues / non conformities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Processing Activity Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''processing activities''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Risk Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''risks''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Process Settings''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Knowledge Item Creator&amp;lt;/u&amp;gt; || If set to &amp;quot;Yes&amp;quot;, it enables the user to create new ''knowledge items''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Password Management''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Old Password&amp;lt;/u&amp;gt;, &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; || These fields work together, enter a new password in &amp;lt;u&amp;gt;New Password&amp;lt;/u&amp;gt;, enter the previous password in &amp;lt;u&amp;gt;Old Password&amp;lt;/u, confirm the new password in &amp;lt;u&amp;gt;Confirm New Password&amp;lt;/u&amp;gt; and press '''CHANGE PASSWORD''' to change the ''user'' password. &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Note that when the environment is initially created, a ''user'' with administrative role is created and activated using subscription information. The access credentials of this ''user'' are sent by mail.&lt;br /&gt;
&lt;br /&gt;
For more information on how to manage the ''user'' record, visit [[How_To#Records_Management|records management]].&lt;br /&gt;
&lt;br /&gt;
==Groups Management==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group Management''&amp;lt;/b&amp;gt; menu item list the available ''groups'' and allows to manage ''groups'' (create, modify, delete). Only ''users'' with administrative privileges have the rights to perform ''group'' management.&lt;br /&gt;
&lt;br /&gt;
When a Privacy-Now® environment is created, a set of default ''groups'' are generated. They are:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Group!! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - AUD || Designed to include the ''auditors'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DC || Designed to include the ''data controller]]'' ''users''.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DP || Designed to include the ''data processor'' ''users''. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;organization&amp;gt; - DPO || Designed to include the ''data protection officers'' ''users''&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the table above, &amp;lt;organization&amp;gt; is to be replaced with the name of the organization used for Privacy-Now® subscription.&lt;br /&gt;
&lt;br /&gt;
Note that ''groups'' are only collections of ''users'' and that actual privileges are defined in process records (e.g. ''access requests'') by assigning a ''group'' to one of the available profiles (see process guides). &lt;br /&gt;
&lt;br /&gt;
The pre configured groups cannot be deleted but they can be renamed and modified in terms of belonging members.&lt;br /&gt;
&lt;br /&gt;
If Privacy process defined at ''Company'' level required the implementation of others roles, the ''Administrator'' can define all the other necessary Groups,to make the standard process complaint the company one using the &amp;lt;b&amp;gt;''Add Group''&amp;lt;/b&amp;gt; function&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Add group ===&lt;br /&gt;
&amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Add Group''&amp;lt;/b&amp;gt; menu item enables to create a new ''group''.&lt;br /&gt;
&lt;br /&gt;
The table below reports the fields belonging to a ''group'' and a short description of them:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Section !! Field !! Description&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Name&amp;lt;/u&amp;gt; ||The name of the group.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; ||A description for the group (e.g. its purpose).&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Default&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Non editable, automatically managed by Privacy-Now®.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Code&amp;lt;/u&amp;gt; ||The ''user'' identifier of the member, not editable and automatically managed by Privacy-Now®. &lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Full Name&amp;lt;/u&amp;gt; ||Surname and Name of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;User Login&amp;lt;/u&amp;gt; ||Login identifier of the member, not editable here because assigned in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Group Manager&amp;lt;/u&amp;gt; ||Used to identify and mark if the member of the ''group'' is the manager of the group. Actually, the manager will have the same privileges has the members.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;Status&amp;lt;/u&amp;gt; ||Status of the member, not editable here because modified in ''user'' management.&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt;|| &amp;lt;u&amp;gt;VIP Type&amp;lt;/u&amp;gt; ||Field not used.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''General''&amp;lt;/u&amp;gt; form, use '''SAVE''' or '''SAVE&amp;amp;EXIT''' to update the ''group''. Use '''DELETE''' to delete a ''group''.&lt;br /&gt;
&lt;br /&gt;
In the &amp;lt;u&amp;gt;''Members''&amp;lt;/u&amp;gt; form see the figure below for the available commands.&lt;br /&gt;
&lt;br /&gt;
[[File:Groups_management_ENG_v1.0.JPG|centre|thumb|800x800px|Groups management controls and commands.]]&lt;br /&gt;
&lt;br /&gt;
=== Modify group ===&lt;br /&gt;
Use &amp;lt;b&amp;gt;''Users &amp;amp; Groups Management / Groups Management''&amp;lt;/b&amp;gt; menu item to see the list of available ''groups'' and click on the one to update. Modify using the features and commands described above in [[Users_&amp;amp;_Groups#Add_group|Add group]].&lt;/div&gt;</summary>
		<author><name>Cbisso</name></author>	</entry>

	</feed>