Data stored in IncidentAnalytix can be sensitive. The Privacy Control Feature that allows you to control the visibility of data that contains Personally Identifiable Information (like a Person, Witness, etc.). This is particularly important when the data relates to minors, or to staff members and you need to limit who can view the data. The following Data Types now have Privacy Control built-in:

With each of these data types you can set them to Visible (the default when an item is created) or Not Visible (private). The Privacy Control section for this is in the Administration Configuration Section which is also secured by User Access Roles allowing you to control what User Roles are able to manage Visibility.

When an item is marked as Not Visible it is no longer displayed in the main Incident User Section and it can only be accessed from the Privacy area in the Configuration Section. Since IncidentAnalytix uses a data hierarchy structure with the Incident Event as the top of the hierarchy, if the Incident itself is marked as Not Visible, no one will see it in the main Search Incident Event Grid and all of the sub-tables connected to an Incident will not be discoverable through the interface. You can choose to keep the Incident Visible and make only those sub-tables that you chose to be Not Visible (ex. Person, Staff, etc.). 

Making a data type Not Visible does not change the data displayed in the Analytics Dashboards. Dashboards still include all data since individual records are generally not identifiable.

Locate the Privacy Section in the Configuration Menu

Select a particular record and control the Visibility status by checking either the Visible - Yes or Visible - No status. You must also indicate a reason for the Visibility status. For Visible the default reason is 'Visible'. For Not Visible there can be numerous values in the Visibility Reason dropdown list which are controlled through the Visibility Reason Lookup Table.

Role-based Security is an important element in managing Privacy. Organizations may wish to grant only certain individuals the ability to set data as Private/Not Visible. The Role Permission that controls this access is the Privacy Edit Permission. For example, if a User has permission to Edit the Person Privacy, then when creating a new Person, they will see the Make Person Visible checkbox control and the Visible Reason dropdown list. If the User does not have the Person Privacy Edit Permission, then these controls are not rendered and the default values of Visible = Yes and Visible Reason = Visible will be inserted in the new record.

 if a Role has Person Privacy Edit enabled, Users in this Role will be able to change a Person record from Visible to Not Visible and from Not Visible to Visible. This Permission can also be available when the Person record is initially created.