Installation and configuration

The PI Detect and Data Breach Response application will be installed into your instance by Relativity. Once the application has been installed at the instance level, you will need to install the application into any workspaces you want to use it in.

Prerequisites

Following are prerequisites for using the PI Detect application:

  • There are four applications that must be installed in the Review workspace where the PI Detect and Data Breach Response application is installed.
    • Installed at the instance level Installed at the workspace level
    Hydro Review interface Relativity Review Services
    Redact NativeMarkupMetadata
    Note: PI Detect uses facade redactions to mark redactions on documents. The instance must have Facade Redactions turned on to leverage the redact capabilities offered with this product.
  • PI Detect relies on the Control Number field. This field must be populated in the Document ID data settings field mapping before ingesting documents.
  • We recommend creating dedicated groups for PI Detect users, for example, a PI Detect Lead or PI Detect First Level Reviewer group.
    Permissions can be assigned to these groups using the instructions below.
  • The PI Detect application requires long text fields such as Extracted Text, OCR and Translations to be stored in Data Grid.

Configuring permissions

To access to the Privacy Workflow tab within the PI Detect and Data Breach Response application in Relativity follow the instructions below:

  1. From your workspace, navigate to Workspace details.
  2. Click Manage Workspace Permissions.
    An image of the Manage Workspace Permissions option found under the Relativity Utilities section.
  3. Assign group permissions for the workspace in the Object Security tab. There are four permission options, all of which are assigned at the workspace level.
    For more instructions on editing and deleting permissions, see Setting workspace permissions. 
    An image of group permission options.

    4. User roles and permissions

    Following is a list of user roles for the PI Detect and Data Breach Response application and the permissions available to them.
    Role Permissions
    PI Detect and Data Breach Response - Lead Users assigned a lead role have access to all features in PI Detect and Data Breach Response:
    • Jobs
    • Batches
    • Data Settings
    • Privacy Workflow
      • Document Ingestion
      • Incorporate Feedback
      • Document Search
      • Excel Reports
      • Quality Control
      • Report Generation
      • Settings
    • Error Codes
    • Configuration
    • Document Reports
    • PI and Entity Search
    • Reviewing documents in the Viewer
      • PI Detection panel
      • Linked Entities panel
      • Table card
    PI Detect and Data Breach Response - Annotator Annotators can access the following features:
    • Reviewing documents in the Viewer
      • PI Detection panel
      • Linked Entities panel
      • Table card
    PI Detect and Data Breach Response - FLR First level reviewers can access the following features:
    • Reviewing documents in the Viewer
      • PI Detection panel
      • Linked Entities panel
      • Table card
    PI Detect and Data Breach Response - QC Quality control reviewers can access the following features:
    • Reviewing documents in the Viewer
      • PI Detection panel
      • Linked Entities panel
      • Table card
    Note: Users included in the workspace admin group must still be added to the PI Detect and Data Breach Response - Lead group.
  4. Click Save.
  5. The Privacy Workflow tab will appear in the workspace once ingestion is run for the first time. See Ingest documents for more information.
    An image of the Privacy Workflow tab.

Setting data settings in workspaces

To set the application settings in a workspace:

  1. Navigate to the workspace containing the documents to send to PI Detect.
  2. Navigate to the PI Detect and Data Breach Response tab.
  3. Select Data Settings.
    An image of the Data Settings option found under the PI Detect and Data Breach Response tab.
  4. Click New PI_Data Settings.
    An image of the New PI Data Settings button.
  5. Click Save.
Note: The PI Detect and Data Breach Response application sends the text located in the Extracted Text field. If a record has no extracted text, it should be Imaged/OCRed and the results written to the Extracted Text field. The other mandatory property is that the native file must exist for the documents being sent.
Note: PI Detect currently requires you to have a field named Control Number when you run an ingestion job. If you have given your Control Number field a Friendly Name or otherwise changed the name of the field, you may see no field to map in your Data Settings.
  1. Navigate to the Jobs tab.
  2. Click the Add button next to Data Settings Name.
  3. Map Relativity Workspace fields to Privacy fields.
  4. Click Save.

Defaulting the PI Detect and Data Breach Response application tab

Once the application is installed, you can set it as a default tab:

  1. Click on Workspace Setup and select Tabs.
  2. Find the PI Detect and Data Breach Response Application.
  3. Click the pencil icon to edit.
  4. Enable Visible under Tab Information.
  5. Enable Show in Sidebarunder Tab Location.
  6. Pick an icon.
  7. Click Save.

  8. The PI Detect and Data Breach Response Application should now be visible in the sidebar.
    An image of the PI Detect and Data Breach Response Application icon in the sidebar.

Frequently asked questions

An example image of a blank Privacy Workflow tab with no information populated.

The Privacy Workflow tab will not populate until an ingestion job is run. During the first ingestion job, the application backend will be prepared for the project and the Privacy Workflow tab can be accessed when the job is completed.