# RelativityOne User Documentation > This site contains an overview and the product documentation for RelativityOne, an e-discovery platform hosted in the cloud. This site contains detailed content, tutorials and user guides specific to using RelativityOne, including features, products, and functionalities. This content helps users and administrators understand how to use RelativityOne. ## Core Pages - [Homepage](https://help.relativity.com/RelativityOne/Content/index.htm): Main entry point. ### Active Learning - [Active Learning Project validation statistics] (https://help.relativity.com/RelativityOne/Content/Relativity/Active_Learning/Project_Validation_Statistics.htm): The Active Learning application is only available in Relativity Server. For RelativityOne's assisted review application, see Review Center. - Second paragraph: If you are not redirected automatically in 3 seconds, click on Review validation statistics. - Headings: H1: Active Learning Project Validation statistics - [Active Learning security permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Active_Learning/Security_permissions.htm): This page contains information on the security permissions required for creating and interacting with an Active Learning project. - Second paragraph: If you are not redirected automatically in 3 seconds, click on Review Center security permissions. - Headings: H1: Active Learning security permissions - [Best practices for Active Learning review] (https://help.relativity.com/RelativityOne/Content/Relativity/Active_Learning/Best_practices_for_Active_Learning_review.htm): The Active Learning application is only available in Relativity Server. For RelativityOne's assisted review application, see Review Center. - Second paragraph: If you are not redirected automatically in 3 seconds, click on Best practices for Review Center review. - Headings: H1: Best practices for Active Learning review ### Advice Hub Solutions - [Auto increment field on object] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Auto_increment_field_on_object.htm): The Auto Increment Field on Object solution calculates and adds an incremental value to a field automatically each time a user creates a new record for an object. - Second paragraph: The Auto Increment Field on Object solution calculates and adds an incremental value to a field automatically each time a user creates a new record for an object. This solution is not supported for the document object. - Headings: H1: Auto increment field on object | H2: Before you begin | H3: Supported versions | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Preparing the workspace | H3: Creating a configuration record | H3: Associating the object type | H2: Running the solution | H2: Viewing the results - [Batch Set Cleanup] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Batch_Set_Cleanup.htm): Batch Set Cleanup removes all documents contained in the saved search of each batch set you specify. - Second paragraph: Batch Set Cleanup removes all documents within a saved search of each batch set you specify. - Headings: H1: Batch Set Cleanup | H2: Migrating from Remove documents from batch sets | H2: Before you begin | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H3: Install the Review application to your workspace | H2: Running Batch Set Cleanup | H3: Create a new job | H3: Configure the job | H3: Canceling a job | H3: Purging a job | H2: Viewing the results - [Change redaction type] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Change_redaction_type.htm): The Change Redaction Type solution changes existing black, white, or text redactions in a specific set of documents to a type of redaction that you specify. - Second paragraph: The Change Redaction Type solution changes existing black, white, cross, or text redactions in a specific set of imaged documents to a type of redaction that you specify. This solution does not change redactions on native files. - Headings: H2: Before you begin | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Running the solution | H2: Viewing the results - [Collect folder path data] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Collect_folder_path_data.htm) - Headings: H1: Collect folder path data - [Copy redactions across markup sets] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Copy_redactions_across_markup_sets.htm): The Copy Redactions Across Markup Sets solution copies redactions from one markup set to another. - Second paragraph: The Copy Redactions Across Markup Sets application copies redactions placed on images from one markup set to another. This solution does not copy redactions to native files. To download the solution files, visit the Relativity Community. - Headings: H2: Before you begin | H3: Supported versions | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Running the solution | H2: Viewing the results - [Copy redactions across workspaces] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Copy_redactions_across_workspaces.htm): The Copy Redactions Across Workspaces solution copies redactions from a source markup set to a destination markup set in a separate workspace. - Second paragraph: To download the solution files, visit the Relativity Community. - Headings: H2: Before you begin | H3: Supported versions | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Running the solution | H3: Running the Setup script | H3: Running the Read Source Markup Set script | H3: Running the Write Destination Markup Set script | H2: Viewing the results - [Date field parsing] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Date_field_parsing.htm): The Date Field Parsing solution parses the date and time from a Date field and writes each value to a separate field for each document that - Second paragraph: The Date Field Parsing application parses date and time values from date source field. It adds these values to two different destination fields. The source is a Date field, while the destinations are Fixed-Length Text or Long Text fields. The application completes this process and all the documents are returned by a specific saved search. When configuring the application, you need to specify the following items: - Headings: H2: Before you begin | H3: Accessing the application | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H3: Adding the application to the Application Library | H3: Creating the destination fields | H2: Running the solution | H2: Viewing the solution results - [Disable inactive users] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Disable_inactive_users.htm): The Disable Inactive Users solution can either present a report of users who are considered inactive or disable users who are considered inactive based on selected criteria. - Second paragraph: The Disable Inactive Users solution generates a report listing report of inactive users. It can also disable inactive users based on selected criteria. - Headings: H1: Disable inactive users | H2: Supported versions | H2: Before you begin | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Preparing the workspace | H2: Running the Solution | H2: Viewing the results - [Document unitization] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Document_unitization.htm): The Document Unitization solution allows you to split an imaged document into multiple child documents. This solution is one component of the Document Utilities application. Visit the Relativity Customer Portal to download the Document Utilities application. - Second paragraph: The Document unitization solution can be used to split an imaged document into multiple child documents. This solution is one component of the Document Utilities application along with the move to folder path mass operation. - Headings: H1: Document unitization | H2: Before you begin | H3: Supported versions | H3: Components | H3: Permissions | H3: Considerations | H2: Deploying and configuring the solution | H3: Configuring padding settings for child documents | H2: Running the solution | H2: Viewing the results | H2: Handling errors | H3: Error messages | H2: Uninstalling Document Utilities | H2: Performance expectations - [Environment-level user login and workspace] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Environment-level_user_login_and_workspace.htm): The Environment-Level User Login and Workspace Access solution queries and reports data about login and access actions that individual users performed in a Relativity instance during a time period that you specify. - Second paragraph: In RelativityOne, the system stores audit records in SQL for a limited time before migrating them to the main data sink. The PostMigrationPersistencePeriod instance setting controls how long records remain in SQL: - Headings: H1: Environment-level user login and workspace access | H2: Before you begin | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Preparing the workspace | H2: Running the solution | H2: Viewing the results - [File validation application] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/File_validation.htm): The File Validation Agent solution searches for document files on a file server, uses a field that you specify to indicate whether any of those files are missing from the server, and provides a report containing a detailed list of the files that are missing. - Second paragraph: The File Validation application solution determines whether any document files are missing from the file server. The solution performs the following tasks: - Headings: H2: Before you begin | H3: Supported versions | H3: Components | H3: Permissions | H2: Deploying and configuring the solution | H3: Downloading the application | H3: Adding the solution to the Application Library | H2: Preparing the workspace | H3: Installing the solution application | H3: Creating the missing files indicator field | H2: Running the solution | H3: Canceling a job | H2: Viewing the results | H2: Handling errors | H2: Rerunning the solution | H2: FAQ - [Normalize redactions across a relational group] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Normalize_redactions_across_relational_group.htm): The Normalize Redactions Across Relational Group script facilitates normalizing redactions across duplicate documents. - Second paragraph: The Normalize Redactions Across Relational Group script facilitates normalizing redactions across duplicate imaged documents. This solution does not affect redactions on native files. - Headings: H2: Before you begin | H3: Supported versions | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Preparing the workspace | H2: Running the solution | H2: Viewing the results - [Populate Parent ID and Child ID] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Populate_Parent_ID_and_Child_ID.htm): The Populate Parent ID and Child ID solution is a workspace-level script that populates Parent ID and Child ID fields on a document for each relational group in a saved search. - Second paragraph: The Populate Parent ID and Child ID solution is a workspace-level script that populates a production Parent ID and Child ID on a document for a production set. - Headings: H2: Supported versions | H2: Special considerations | H2: Performance | H2: Preparing the workspace | H3: Installing the script | H3: Creating the fields | H2: Running the solution | H2: Viewing the results - [Propagate coding post-import] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Propagate_coding_post-import.htm): The Propagate Coding Post-Import solution propagates the value of one or more fields to documents that are part of the same relational group, and it reports any coding variances within those groups. - Second paragraph: The Propagate Coding Post-import solution performs several tasks to help you assign field values from one document to others that are part of the same relational group and returned by a saved search that you specify. You can customize the solution by specifying which field defines relational groups, which fields to propagate values to, and whether and how to address any coding variances within relational groups. The solution also reports coding variances, which can help you work with reviewers to address the variances. This solution provides two primary ways to propagate values. The first is a set of scripts, agents, and other components that propagate values to multiple fields when you run the solution manually or automatically according to a schedule that you define. The second is a script that propagates values to only one field when you run the script manually, "on demand." To learn more about the script, see Propagating to one field on demand. - Headings: H1: Propagate coding post-import | H2: Before you begin | H3: Components | H3: Considerations | H3: Performance | H2: Deploying and configuring the solution | H3: Downloading and adding the application to the Application Library | H2: Preparing the workspace | H3: Creating and configuring the propagation job | H3: Defining a schedule for running the propagation job | H2: Running the solution | H3: Running the job manually | H3: Viewing job status and history | H2: Understanding parent to child results | H2: Viewing the results | H3: Viewing coding variances | H3: Deleting job results | H2: Propagating to one field on demand | H3: Running the script | H3: Example | H3: Upgrading this application - [Reproduce a redaction to a document universe] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Reproduce_redaction_to_document_universe.htm): The Reproduce Redaction to Document Universe solution reproduces a redaction made on one primary document in a source markup set to all pages of all documents in the specified saved search in the destination markup set. - Second paragraph: This solution reproduces the redactions made on all pages of all documents in a selected saved search from a source markup set to a destination markup set. This solution does not apply redactions to native files. - Headings: H2: Before you begin | H3: Supported versions | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Running the solution | H2: Viewing the results - [Set native time zone offset with DST] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Set_native_time_zone_offset_with_DST.htm): This solution takes a configurable date field value and time zone and updates each newly loaded document’s Relativity Native Time Zone Offset field to account for Daylight Saving Time (DST). The solution also sets the Single-Object Time Zone field on the document object to be used for imaging profiles. - Second paragraph: The offset value changes based on daylight savings time. For example: - Headings: H1: Set native timezone offset with Daylight Saving Time | H2: Before you begin | H3: Compatibility matrix | H3: Components | H3: Considerations | H2: Deploying the solution | H3: Adding the Relativity script | H3: Adding the Relativity application | H3: Setting up the Time Zone Agent Errors Relativity group | H2: Preparing the workspace | H2: Running the solution | H3: Viewing workspaces and their statuses | H2: Viewing the results | H3: Viewing the returned output | H3: Optionally resetting the last checked date | H3: Resetting script behavior | H3: Support | H3: Disclaimer - [Track document field edits by reviewer] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Track_document_field_edits_by_reviewer.htm): The Track Document Field Edits by Reviewer solution populates fields that you specify with information about changes that users made to a specific field. The solution tracks which user made a change and when they made the change. - Second paragraph: The Track Document Field Edits by Reviewer solution tracks the first or most recent change to a field that you specify and it populates two other fields, Reviewed By (User) and Reviewed On (Date), with information about those changes. An event handler will monitor the tracked fields and update the Reviewed On and Reviewed By fields based on the tracker's settings. - Headings: H2: Before you begin | H3: Components | H3: RelativityOne considerations | H3: Considerations | H2: Deploying and configuring the solution | H2: Preparing the workspace | H3: Creating the tracking fields | H3: Configuring the application | H2: Populating Historical Records | H2: Viewing the results - [User counts per workspace] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/User_counts_per_workspace.htm): The User Counts per Workspace solution is an environment-level script that calculates the distinct number of standard users and system admins that had access to a workspace in a Relativity instance for a selected month and year. - Second paragraph: The User Counts per Workspace solution is an environment-level script. It calculates the distinct number of standard users and system admins with access to a workspace in a Relativity instance. It performs this calculation the selected month and year. - Headings: H2: Before you begin | H3: Supported versions | H3: Components | H3: Considerations | H2: Preparing the workspace | H2: Running the solution | H2: Viewing the results - [User Import Application] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/User_Import_Application.htm): The Relativity User Import Application allows you to efficiently manage multiple users. You can import users from CSV files, including their Relativity settings, and export lists of users with their settings for backup or transfer. - Second paragraph: Make sure you're logged in with your valid Relativity Community credentials. - Headings: H2: Downloading Community Files | H3: Supported Versions | H2: Category | H3: Special considerations | H2: Deploying and configuring the solution | H2: Preparing the workspace | H3: Installing the application | H2: Export utility job | H3: Viewing export errors | H2: Import utility job | H3: Progress | H3: Viewing import errors | H2: Performance metrics - [User workspace access and last login] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/User_workspace_access_and_last_login.htm): The User Workspace Access and Last Login solution displays a list of current Relativity users, the date when they last logged in to Relativity, and the workspaces that they currently have access to. - Second paragraph: Use the link in the Supported version section to download the solution from the Relativity Community. - Headings: H1: User workspace access and last login | H2: Before you begin | H3: Supported version | H3: Category | H3: Considerations | H2: Deploying and configuring the solution | H2: Running the solution | H2: Viewing the results - [Workspace folder group security] (https://help.relativity.com/RelativityOne/Content/Advice_Hub_Solutions/Workspace_folder_group_security.htm): This script reports the security permissions for each folder in the Document object. To download the solution files, visit the Relativity Customer Portal. - Second paragraph: The Workspace folder group security solution provides a script that reports on the security permissions for each folder in the Document object. - Headings: H1: Workspace folder group security | H2: Before you begin | H3: Supported versions | H3: Components | H2: Deploying and configuring the solution | H2: Running the solution | H2: Viewing the results ### aiR Assist - [aiR Assist (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/aiR_Assist.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: aiR Assist is a conversational search tool integrated within RelativityOne, designed to empower legal teams to interact with their data using natural language. By leveraging advanced AI, aiR Assist helps to surface potential insights, reveal possible connections, and uncover themes more efficiently. This can enhance the process they use to analyze and interpret legal data more effectively, potentially leading to quicker understanding, better decisions, and defensible workflows when validated by users. - Headings: H1: aiR Assist (Advanced Access) | H2: How aiR Assist works | H3: LLM model in use | H3: Important Limits | H3: Understanding aiR Assist responses | H2: Language support | H2: Supported use cases | H2: Release notes - [Best practices (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Best_Practices.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Refer to the best practices below to effectively use aiR Assist. - Headings: H1: Best practices (Advanced Access) | H2: Prompting | H2: Indexing - [Feedback options (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Feedback_options.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: aiR Assist provides ways to submit feedback about the responses generated. - Headings: H1: Feedback options (Advanced Access) | H2: Feedback controls for responses (thumbs up/thumbs down) | H2: In-product feedback survey - [Frequently asked questions] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Frequently_Asked_Questions.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Listed are questions you might have using the aiR Assist application. - Headings: H1: Frequently asked questions (Advanced Access) | H2: Question FAQs | H2: Answer/Response FAQs | H2: Conversation FAQs | H2: Index FAQs | H2: Document FAQs - [Index Management (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Using_Index_Manager.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: The Index Manager provides centralized access to indexes created in aiR Assist or aiR for Case Strategy. An index within aiR Assist consists of a collection of documents that the system searches to generate responses to prompts. Each index is constructed from the extracted text of documents available in public saved searches within a workspace. Users may select the appropriate index for their prompts to ensure relevant and informed responses. Additionally, they can switch between indexes when submitting prompts, facilitating exploration of varied subjects or collections within the current workspace. - Headings: H1: Index Management (Advanced Access) | H2: Indexes created in aiR for Case Strategy | H2: Indexes created within aiR Assist | H2: Throughput expectations - [Installation and permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Installation.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: aiR Assist does not need to be installed. It is available in all workspaces with aiR for Case Strategy enabled, provided that a Fact Extraction or Transcript Summary job has been completed. - Headings: H1: Installation (Advanced Access) - [Intent detection (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Intent_Detection.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Intent detection is one of the mechanisms that aiR Assist uses to understand the purpose behind each prompt and respond in the most appropriate way. Instead of simply matching keywords, aiR Assist analyzes the intent of a query to determine whether it should: - Headings: H1: Intent detection (Advanced Access) - [Metadata mapping (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Metadata_Mapping.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Incorporating metadata mapping helps improve how aiR Assist retrieves documents by allowing the AI model to use structured metadata as part of the retrieval process, in addition to semantic relevance. This leads to more accurate, context appropriate results when answering user questions. - Headings: H1: Metadata mapping (Advanced Access) | H2: Configuring metadata mapping | H2: Using metadata for prompting - [Permissions (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Permissions.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: System administrators can control access to aiR Assist per group within a workspace using Features Permissions for Index Management, Prompting, and Access Management. This is helpful when different teams are responsible for different tasks, such as only using indexing or only asking questions. See Feature permissions and Setting workspace permissions for more information. - Headings: H1: Permissions (Advanced Access) - [Prompting (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Asking_a_question.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: You can ask aiR Assist about indexed documents in natural, conversational language. Follow-up prompts build on earlier ones, and aiR Assist uses the conversation context and any people or events mentioned. See Best practices (Advanced Access) for prompt-writing tips. - Headings: H1: Prompting (Advanced Access) | H2: Navigating the prompt composer | H2: Navigating the responses | H2: Submitting prompts | H2: Starting a new prompt conversation | H2: Copying a response | H2: Conversation history and sessions - [Using Conversation Manager (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Using_Conversation_Manager.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Conversation Manager lets you access and manage all your conversations. You can see a list of your conversations, rename them, or delete any unneeded threads. It also enables you to switch between different conversations and return to previous ones to continue your inquiries. See Conversation history and sessions for additional information. - Headings: H1: Using Conversation Manager (Advanced Access) | H2: Navigating the Conversations panel | H2: Opening conversation manager | H2: Renaming a conversation | H2: Deleting a conversation - [Working with indexes (Advanced Access)] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/aiR_Assist/Working_with_indexes.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Users with the permission to use Index Manager can create new indexes, rebuild existing ones, and delete indexes. See Permissions for details on the Index Management permission. - Headings: H1: Working with indexes (Advanced Access) | H2: Navigating the Index Manager | H2: Indexing rules and limitations | H2: Creating a new index | H2: Rebuilding an index | H2: Deleting an index | H2: Monitoring the index build process | H2: Error handling and retrying index jobs ### aiR for Case Strategy - [aiR for Case Strategy] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Case_Strategy/aiR_for_Case_Strategy.htm): aiR for Case Strategy uses Generative AI to support and potentially accelerate the building of your case strategy. With aiR for Case Strategy, you can automatically identify and extract potential facts from key documents, generate customizable document summaries to assist with review, and use collections of these facts to help draft witness summaries and deposition outlines to support preparation for interviewing individuals. - Second paragraph: Before using AI, we recommend learning about how it works so that you can leverage it effectively. For more information, see Generative AI considerations in aiR for Case Strategy. - Headings: H1: aiR for Case Strategy | H2: Installing aiR for Case Strategy | H2: Permissions | H3: aiR for Case Strategy billing and usage | H2: Deployment and processing geographies - [Creating a fact chronology] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Case_Strategy/Creating_a_fact_chronology.htm): aiR for Case Strategy transforms your key document set into a structured fact chronology, to help you understand who did what and when. As part of fact extraction, facts are grouped and in some cases, higher-level facts are constructed to deliver a succinct chronology that minimizes fact duplicates. - Second paragraph: Once extracted, you can view facts in a chronological list, gather them to prepare a witness summary or a deposition outline, or use the facts in customizable workflows. To learn more, see Creating witness summaries and deposition outlines. - Headings: H1: Creating a fact chronology | H2: Facts | H3: Create a fact chronology | H3: Prompt criteria | H3: aiR Fact fields | H3: Fact extraction considerations | H3: aiR Facts view | H3: Fact Types and fact extraction QC | H3: Editing facts using inline editing | H3: Mass editing aiR Entities | H3: Edit the aiR Entities field | H3: Overlay the aiR Entities field values | H3: Document Preview panel | H2: General writing guidelines | H2: Size limitations | H3: Job email results - [Creating witness summaries and deposition outlines] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Case_Strategy/Creating_witness_summaries_and_deposition_outlines.htm): After facts have been extracted using aiR for Case Strategy to create a fact chronology, you can create a witness summary and a deposition outline to aid your case. To learn more, see Creating a fact chronology. - Second paragraph: Before using AI-based capabilities, we recommend learning about how the AI components in aiR for Case Strategy work so that you can leverage the features effectively. For more information, see Generative AI considerations in aiR for Case Strategy. - Headings: H1: Creating witness summaries and deposition outlines | H2: Witness summaries | H3: Create a witness summary | H2: Deposition outlines | H2: Create a deposition outline | H3: Prompt criteria | H3: Deposition outline and witness summary considerations | H2: Interacting with related documents or facts | H3: Viewing the documents associated with a deposition outline or witness summary | H3: Viewing the facts associated with a deposition outline or witness summary | H2: Working with deposition outlines and witness summaries | H3: Downloading a deposition outline or witness summary | H3: Editing a deposition outline or witness summary | H3: Deleting a witness summary or deposition outline | H3: Document Preview panel | H2: General writing guidelines | H2: Size limitations | H3: Job email results - [Fact Navigator] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Case_Strategy/Fact_Navigator.htm): Using Fact Navigator, you can review facts in a consolidated fact list designed to help streamline analysis, apply advanced filters to focus on details that may be most relevant, and visualize a generated chronology of events with the Timeline, based on extracted facts. - Second paragraph: To access Fact Navigator, navigate to the Case Home tab and click on the Try Fact Navigator button. - Headings: H1: Fact Navigator | H2: Fact list | H2: Fact Detail card | H3: Editing a fact | H2: Filter panel | H2: Timeline | H2: Issues tab | H3: Facts sub-tab | H3: Entities sub-tab | H3: Documents sub-tab - [Generative AI considerations in aiR for Case Strategy] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Case_Strategy/Generative_AI_considerations_in_aiR_for_Case_Strategy.htm): Generative AI technology, specifically large language models (LLMs) are central to the capabilities of aiR for Case Strategy. While powerful, these technologies do carry risk, and it’s important that you understand the extent of those limitations as you use the product. - Second paragraph: Broadly speaking, we expect the users of aiR for Case Strategy to always have a human overseeing the work produced by the AI. In particular, the possibility exists that the AI can do the following: - Headings: H1: Generative AI considerations in aiR for Case Strategy | H2: Non-determinism | H2: Possibility of hallucinations | H2: Extracted text only | H2: Fact fields used for generating case documents | H2: No memory from document to document ### aiR for Data Breach Response - [aiR for Data Breach Response] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/aiR_for_Data_Breach_Response.htm): aiR for Data Breach Response is a Relativity product purpose-built to support and help streamline the process of identifying, extracting, and linking Personal Information (PI) and Personal Health Information (PHI) to the relevant individual or organization, and generating a consolidated list of potentially impacted individuals using generative artificial intelligence (AI). - Second paragraph: aiR for Data Breach Response is available as a Relativity application (RAP). You can install the application into a RelativityOne Review workspace that runs within a RelativityOne production environment. (The data used for analysis never leaves the RelativityOne security boundary, which aligns with security and compliance requirements defined in RelativityOne contracts.) - Headings: H1: aiR for Data Breach Response | H2: Conceptual workflow | H2: Document requirements | H2: Unstructured and Structured documents | H3: Supported file types | H2: Considerations | H2: Shared LLM resources | H2: Security and privacy | H2: Deployment and processing geographies | H2: Language support in aiR for Data Breach Response | H2: Running aiR for Data Breach Response | H2: Personal Information detectors - [Blocklisting] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Blocklisting.htm): A blocklist is a list of banned or excluded PI Values. Using the blocklisting tool, you can identify potential PI tagged within the application and blocklist those that were falsely tagged - Second paragraph: With Blocklisting, you can: - Headings: H1: Blocklisting | H2: Requirements | H2: Blocklisting | H2: Excluded Cell Values | H2: Reviewing and Blocklisting terms | H3: Suggested Blocklisting workflow | H3: Blocklisting PI values | H3: Removing PI values from the Blocklist | H3: Viewing Excluded PI values from structured documents | H3: Overriding excluded PI Values | H2: Considerations - [Conflicts] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Conflicts.htm): During entity normalization, aiR for Data Breach Response may identify records that share some — but not all — Personal Information (PI) identifiers. These are called conflicts. A conflict occurs when two or more records have overlapping PI (such as a shared email address) but also contain contradictory PI (such as different SSNs), making it unclear whether they represent the same individual or different individuals. - Second paragraph: After the normalization process completes, you can review conflicts on the Conflicts subtab under Entity Analysis. Resolving conflicts helps you determine whether entities should be merged or kept separate before you finalize your entity report. - Headings: H1: Conflicts | H2: Review Conflicts | H3: Recommended workflow | H2: Conflicts fields | H3: Example conflict logic - [Data Analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Data_analysis.htm): The Incorporate Feedback pipeline is a combination of machine stages that make predictions, perform calculations, curate machine output, and generate reports. - Second paragraph: To run Data Analysis: - Headings: H1: Data Analysis | H2: Run Data Analysis | H2: Choose stages to run | H3: Data Analysis stages | H2: Monitor Data Analysis status | H3: Overall progress | H3: Blocklisting | H3: PI Detection | H3: Entity Normalization & Deduplication | H3: Compile Insights | H2: Data Analysis and document review | H2: Cancel and retry Data Analysis | H2: Document errors | H2: Data Analysis history | H3: Run details | H3: Stage history - [Data Breach Response (Legacy)] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Data_Breach_Response__Legacy_.htm): Data Breach Response is an AI-powered solution used to reduce the time, cost, and risk to produce an entity notification list. - Second paragraph: Data Breach Response is a Relativity application purpose-built to simplify and accelerate the complex process of identifying sensitive information and matching it to the relevant entity, generating a notification list of impacted individuals. - Headings: H1: Data Breach Response | H2: Conceptual workflow | H2: Document requirements | H2: Structured and Unstructured documents | H3: Supported file types | H2: Language support in Data Breach Response | H2: Limitations | H2: Out of the box detectors | H3: Enable and disable detectors | H3: PI level detectors | H2: Frequently asked questions - [Detector QC] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Detector_QC.htm): Detector QC is the process by which humans adjust detectors for precision and recall before the review team begins their review. - Second paragraph: QC batches typically fall into one of two categories, batches containing PI and batches not containing PI. The following steps assume you have created Review Queues as outlined in Quality control. - Headings: H1: Detector QC | H2: QC batches that contain PI | H2: QC batches that do not contain PI - [Document flags] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Document_flags.htm): Data Breach Response uses document flags in a number of ways to denote information about a document. - Second paragraph: A document can have multiple reasons for failure. However, the error log records only the first issue encountered and produces a flag for that issue. Analysis stops at that point, so any additional issues with the document are not evaluated until you correct the initial error and resubmit the document. - Headings: H1: Document flags | H2: System flags | H3: System default flag types - [Document ingestion] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Document_ingestion.htm): Learn about document ingestion. - Second paragraph: Before you create an ingestion job, verify the following: - Headings: H1: Document ingestion | H2: Prerequisites | H2: Create a new ingestion job | H3: Tracking job progress | H2: Job details | H3: Understanding document counts | H3: Job failures | H2: Frequently asked questions - [Entities] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Entities.htm): The Entities subtab is part of the Entity Analysis tab in aiR for Data Breach Response. An entity is a unique individual identified by their name and associated Personal Information (PI), such as Social Security Number, date of birth, or full address. Entities are assigned a unique Entity ID and are composed of one or more records. For definitions of related terms like Record and Conflict Cluster, see Entity Analysis. - Second paragraph: The Entities tab lists all identified entities such as names, organizations, and locations across the dataset with frequency and context. This is also where you can create an Entity Report. The Entity Report shows Total Entity Records, Total Entities, and information about each Entity. - Headings: H1: Entities | H2: Review Entities | H2: Entity Report fields | H2: Entity information | H2: Save as List | H2: Download - [Entity Analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Entity_analysis.htm): Learn about entity normalization in Data Breach Response. - Second paragraph: The following terms are used throughout this section: - Headings: H1: Entity Analysis | H2: Frequently asked questions - [Installation and configuration] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Installation_and_configuration.htm): 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. - Second paragraph: Before you begin, verify the following: - Headings: H1: Installation and configuration | H2: Prerequisites | H2: Installation to workspaces | H2: User roles and permissions | H3: Configure permissions | H2: Set the aiR for Data Breach Response application as a default tab | H2: Frequently asked questions - [Manually Merge and Unmerge Entities] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Manually_Merge_and_Unmerge_Entities.htm): During entity normalization, aiR for Data Breach Response automatically groups records into entities based on name similarity and Personal Information (PI) matches. If the system makes an error during this process, you can manually correct it by merging or unmerging records and entities. - Second paragraph: The following terms are used throughout this topic: - Headings: H1: Manually Merge and Unmerge Entities | H2: Merge Entities | H2: Merge Records | H2: Unmerge records from entities - [Personal information detectors] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Personal_Information_detectors.htm): From the Project Settings page, you can view all detectors and tags, add new detectors and tags, and turn detector tags on and off. - Second paragraph: Deduplication Identifiers - Determine how entities are normalized during Entity Analysis. - Headings: H1: Personal Information detectors | H2: Definitions | H2: Permissions | H2: Viewing detectors | H3: Detectors fields | H2: Supported Personal Information detectors | H2: Creating custom detectors | H2: Editing detectors | H2: Limitations | H2: Frequently asked questions | H3: RegEx recommendations - [PI and entity search] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/PI_and_Entity_Search.htm): With PI and Entity Search you can search documents with PI and Data Breach Entities that have been identified by Data Breach Response. - Second paragraph: To create a search query: - Headings: H1: PI and Entity Search | H2: Create a PI and Entity Search query | H3: Searchable fields | H3: Operators | H3: Example search strings - [Project Dashboard] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Project_dashboard_.htm): Project Dashboard is available to project leads and provides access to available key information. You can use Project Dashboard to derive insights across your Data Breach Response project. - Second paragraph: You can review details of all flagged documents in the Document panel at the bottom of the dashboard. See Document flags for descriptions of each flag and suggested next steps. - Headings: H1: Project Dashboard | H2: Job Progress | H2: PI Types | H2: Document Types | H2: Document List | H3: Column customization | H3: Manage annotations | H3: Save as List | H3: Export the Document List - [Quality control] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Quality_control.htm): The Quality Control (QC) process is an optional step that occurs prior to review by the Project Lead. The goal of this step is to ensure that there is a minimization of documents with over and under predictions. - Second paragraph: Changes you make during these steps take effect only after you re-run Data Analysis. Keep documents unlocked during pre-review QC so that you can continue making updates to them. - Headings: H1: Quality control | H2: QCing unstructured documents for recall | H3: Create QC review queues with no identified PI | H3: Review documents | H3: Refining custom detectors | H2: QCing unstructured documents for precision | H3: Create QC review queues containing PI | H3: Review documents | H3: Refining detectors | H2: QC of detectors and boundaries in spreadsheets | H3: Spreadsheet QC for recall | H3: Spreadsheet QC for precision | H2: Frequently asked questions - [Records] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Records.htm): A Record is a pairing of a raw name and PI data from a single document. If the same individual appears in multiple documents, each appearance creates a separate Record. After normalization, Records with matching PI may be consolidated into a single Entity — a unique individual identified by their name and associated PI, such as SSN, date of birth, or full address. - Second paragraph: Use the Records tab to view and investigate each identified instance of an individual at the document level. You can trace how normalization consolidated individual Records into your final Entity List. - Headings: H1: Records | H2: Review Records | H3: Workflow example | H2: Records fields | H2: Invalid Reasons | H2: Entity information | H2: Save as List | H2: Download - [Review documents] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Review_documents.htm): Learn about common tasks and interfaces used by Reviewers when working with Data Breach Response. - Second paragraph: aiR for Data Breach Response categorizes documents as either Structured or Unstructured, each requiring a distinct approach to identifying PI. - Headings: H1: Review documents | H2: Unstructured documents | H2: Structured documents | H2: Frequently asked questions - [Spreadsheet QC tool] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Spreadsheet_QC_tool.htm): Spreadsheet QC allows a Project Lead to view and edit the headers of columns detected as PI, and view which search terms are being tagged by the machine in spreadsheets. - Second paragraph: You can access Spreadsheet QC from the Spreadsheet QC tab in the aiR for Data Breach Response application. - Headings: H1: Spreadsheet QC tool | H2: Spreadsheet QC fields | H2: Recommended workflow | H3: Prioritizing headers for review | H3: Reviewing headers - [Structured document review] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Structured_document_review.htm): Structured documents contain data organized in a predefined way, typically in tables with columns and rows where each data point has a specific data type. Examples include spreadsheets (.xlsx, .xls) and CSV files. - Second paragraph: aiR for Data Breach Response identifies table boundaries, column headers, and the personal information within those tables. Individuals and their PI appearing in the same table row are automatically linked and appear on the Entity Report. - Headings: H1: Structured document review | H2: Review PI | H2: Create and edit tables | H3: Create a table | H3: Edit a table | H2: Capture PI | H3: Add PI | H3: Edit PI | H3: Delete PI | H3: Add partial cell PI | H3: Edit partial cell PI: | H3: Remove partial cell PI: | H3: Lock detections - [Unstructured document review] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Data_Breach_Response/Unstructured_document_review.htm): Unstructured documents contain unlabeled or otherwise unorganized data. The content in these files typically consists of natural language. Examples include emails, word processing documents, PDFs, and forms. - Second paragraph: When you review unstructured documents in aiR for Data Breach Response, the goal is to validate the PI predictions that aiR highlights in each document. aiR uses the context of the document to differentiate types of Personal Information (PI) and automatically links detected PI to individuals. PI detections identified by aiR are indicated by a sparkle (✦) icon. - Headings: H1: Unstructured document review | H2: Review PI | H2: Capture PI | H3: Add PI | H3: Edit PI | H3: Remove PI | H3: Add drawn annotations | H2: Entity links | H3: Autolinking PI to individuals | H3: Add links from the Viewer | H3: Add links through the Records panel | H3: Remove links | H3: Lock detections | H2: Errors ### aiR for Privilege - [aiR for Privilege] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/aiR_for_Privilege.htm): aiR for Privilege is an AI-powered solution that uses generative AI, large language models, natural language processing, machine learning, and social network graphs to analyze documents and predict whether they are privileged or not and provide a draft privilege log description. - Second paragraph: aiR for Privilege provides value to users across global jurisdictions by: - Headings: H1: aiR for Privilege | H2: Conceptual workflow | H2: Requirements | H2: Deployment and processing geographies | H2: Considerations | H3: RSMF considerations | H2: Billing | H2: Brain | H3: Universal Brain | H3: Client Brain | H3: Matter Brain - [aiR for Privilege Analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/aiR_for_Privilege_analysis.htm): Once you have run aiR for Privilege on a set of documents, you can open each document in the Viewer and see highlighted aiR results and detailed analysis of the results. - Second paragraph: The following permissions are required to use aiR for Privilege Analysis: - Headings: H1: aiR for Privilege Analysis | H2: Permissions | H2: Reviewing aiR for Privilege Analysis results | H2: aiR for Privilege Analysis highlighting - [aiR for Privilege errors] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/aiR_for_Privilege_error_dictionary.htm): If the status of a pipeline step becomes Run Failed or Apply Annotations Failed then there was an error in the action. Check the Error Details field within the Pipeline Steps category or refer to the error message that appears on screen for detailed error information including steps to resolve the issue. - Second paragraph: Following is a list of possible error codes and error messages: - Headings: H1: aiR for Privilege errors - [Calculate accuracy] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Calculate_accuracy.htm): Calculating accuracy, specifically precision and recall, is crucial to understanding the model’s performance. You can use precision and recall analysis to better understand how aiR for Privilege performs with any data set and help guide the prioritization of reviewing documents in future batches. - Second paragraph: Following are key concepts to consider when calculating the accuracy of aiR for Privilege. - Headings: H1: Calculate accuracy | H2: Key concepts | H2: Considerations | H2: Identifying input numbers | H2: Identify Underpredictions when Priv on Own codings are unavailable - [Classify Domains] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Classify_Domains.htm): The Classify Domains pipeline step locates email address domains used to communicate within your data set and uses AI to categorizes each as Law Firm or Third Party. This drives attorney, privilege conferring individual, discovery that influences privileged predictions. - Second paragraph: Following are requirements for the Classify Domains pipeline step: - Headings: H1: Classify Domains | H2: Requirements | H2: Actions | H2: Errors - [Confirm Privilege Status] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Confirm_Privilege_Status_annotation.htm): Confirm Privilege Status annotation occurs on the Final Privilege Status field on the Domains and Entity objects. This annotation is intended to identify whether a Law Firm Domain or Legal Entity is either Privilege Conferring, Privilege Neutral, or Privilege Breaking. - Second paragraph: If a specific Entity plays a dual role, both legal and business, we suggest that you give them a Final Privilege Status of Privilege Conferring. This will drive higher Recall as part of populate privilege results, and our analysis will still be able to determine documents where the individual is sharing business advice rather than legal advice. - Headings: H1: Confirm Privilege Status | H2: Requirements | H2: Final Privilege Status definitions | H3: Domains | H3: Entities | H2: Annotating in RelativityOne | H3: Mass entity annotation | H2: Annotating in Excel | H2: Annotate Final Privilege Status fields | H2: Suggested annotation workflow | H3: Default decision logic - [Confirm Privilege Status] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Confirm_Privilege_Status.htm): The Confirm Privilege Status pipeline step provides an opportunity to optimize results for a specific project by allowing your end-client to confirm or correct decisions made by you and the AI regarding the privilege conferring status of domains and entities. - Second paragraph: Before running the Apply Annotations action make sure you and your end-client have performed annotations on the domains and entities. Quality check the decisions made by your team for accuracy. - Headings: H1: Confirm Privilege Status | H2: Requirements | H2: Actions | H2: Errors - [Create a project] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Create_a_project.htm): An aiR for Privilege project defines the documents you want to analyze. Each project has a dedicated set of pipeline steps that when completed are designed to generate document results. Learn to create an aiR for Privilege project. - Second paragraph: Before creating a project, reference this checklist to make sure you’ve completed all the requirements: - Headings: H1: Create a project | H2: Pre project checklist | H3: Saved search requirements | H2: Creating a project | H3: Project form fields - [Domains] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Domains.htm): A domain is the web address that comes after the @ symbol in an email address. aiR for Privilege extracts domains from communicating email addresses found across all email segments within email documents in the data set. Learn about annotating Domains in aiR for Privilege. - Second paragraph: During the Classify Domains pipeline step, our AI processes domains and categorizes them as Law Firm, Personal Email Service, or Other. These domains are populated on the Domains (Priv) tab, where you can confirm or deny the initial prediction using the process outlined in Suggested annotation workflow. Annotating a domain on the Annotator Decision field as In-House, Law Firm,Personal Email Service, or Other changes how the entities communicating under these domains are classified in the Validate Entities pipeline step. - Headings: H1: Domains | H2: Requirements | H2: Single domain annotation | H2: Mass domain annotation | H2: Annotate domains fields | H2: Suggested annotation workflow - [Entities] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Entities.htm): Entities are the individuals communicating within the data set. They communicate by way of their aliases, which are most commonly full email addresses, user ids, short names, and appear within the documents being analyzed. Learn to annotate Entities in aiR for Privilege. - Second paragraph: During the Validate Entities pipeline step our AI will group the aliases in the data set under a specific entity and then make an AI prediction as to whether the entity is playing a Legal Role in the matter. This information is populated on the Entities (Priv) tab for you to annotate on the Annotator Decision field using the process outlined in Suggested annotation workflow, adjust aliases that belong to each entity using the Merge and Move operations, and populate more extensive entity information. Annotating each entity allows for the AI to understand who could be privilege conferring within the matter and what documents they communicated on driving client-attorney privilege predictions. Like other annotation workflows, you will perform one round of annotating entities and then perform the Apply Annotations Action as specified in Validate Entities. - Headings: H1: Entities | H2: Requirements | H3: Mass entity annotation | H3: Annotate entities fields | H2: Merge mass operation | H2: Move and Create New Entity operations | H2: Suggested annotation workflow - [Equivalent Domains] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Equivalent_Domains.htm): Equivalent domains are identified domain pairs that belong to the same organization. Learn to annotate Equivalent Domains in aiR for Privilege. - Second paragraph: During the Match Equivalent Domains pipeline step, our AI predicts pairs of domains that might belong to the same business entity. These predicted pairings populate on the Equivalent Domains (Priv) tab, allowing you to annotate on the Annotator Decision field using the process outlined in Suggested annotation workflow. Annotating an equivalent domain on the Annotator Decision field as equivalent will allow you to link different aliases with these two domains to the same entity. Each pair of domains also has an Impacted Aliases field. This field notes how many Aliases share both domains, and you should use it to prioritize the annotation of domain pairings that have a higher Impacted Aliases count. - Headings: H1: Equivalent Domains | H2: Requirements | H2: Single equivalent domain annotation | H2: Mass equivalent domain annotation | H2: Annotate equivalent domains fields | H2: Suggested annotation workflow - [General settings] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/General_settings.htm): General settings apply to all aiR for Privilege projects within the workspace and must be populated prior to starting any aiR for Privilege project. Learn about general settings in aiR for Privilege. - Second paragraph: To update general settings: - Headings: H1: General settings | H2: Client Brain | H3: Client Brain fields | H2: Reviewer Privilege Decision Mapping | H2: Document Field Mapping | H3: Validating document field mappings - [Installation and configuration] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Installation_and_configuration.htm): This section outlines instance level and workspace level installation of the aiR for Privilege application and provides an overview of steps you must take to configure aiR for Privilege before beginning a project. - Second paragraph: The aiR for Privilege application will automatically be installed within your RelativityOne instance. This process takes 1-5 business days from the completion of aiR for Privilege contracting. - Headings: H1: Installation and configuration | H2: Instance level installation | H2: Workspace level installation | H2: Configuration | H2: General settings in a workspace | H3: Client Brain - [Known items] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Known_items.htm): A known item is information that you already know about the matter or about how to identify privilege. aiR for Privilege will use this information to start a project and create consistency across projects. - Second paragraph: These known items apply to all projects within the workspace and you must populate them before starting any project. - Headings: H1: Known items | H2: Known Attorneys | H3: Known Attorney fields | H2: Known Law Firms | H3: Known Law Firm fields - [Match Equivalent Domains] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Match_Equivalent_Domains.htm): The Match Equivalent Domains pipeline step identifies email address domains that are different but belong to the same underlying organization and decides what communicating email addresses belong to the same individual. - Second paragraph: Following are requirements for the Match Equivalent Domains pipeline step: - Headings: H1: Match Equivalent Domains | H2: Requirements | H2: Actions | H2: Errors - [Perform annotations] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Perform_annotations.htm): Certain pipeline steps require you to confirm the predictions made by the AI, which is called performing annotations. This increases the accuracy of the system and ensures privileged documents are not missed. - Second paragraph: The Annotator user group must perform annotations. For more information see Roles and security permissions. - Headings: H1: Perform annotations - [Populate Privilege Results] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Populate_Privilege_Results.htm): The Populate Privilege Results pipeline step uses decisions made within prior pipeline steps and generative AI to generate a prediction of whether a document may be Privileged or Not Privileged. - Second paragraph: Once the Confirm Privilege Status pipeline step is complete, the system will automatically run Populate Privilege Results and the status will change to Run In Progress. - Headings: H1: Populate Privilege Results | H2: Actions | H2: Errors - [Prepare Project] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Prepare_Project.htm): The Prepare Project pipeline step organizes the documents in the linked saved search for AI analysis using both the project settings and general settings. Learn about the Prepare Project pipeline step. - Second paragraph: The Prepare Project step also retrieves and organizes information from the Client Brain depending on your general settings and the known items if populated. Changes to these items after running the Prepare Project step on a project are not reflected for that specific project. - Headings: H1: Prepare Project | H2: Requirements | H2: Billing | H2: Actions | H2: Errors | H3: Documents with parsing errors - [Prioritize documents for review] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Prioritize_documents_for_review.htm): Once Populate Privilege Results is complete, aiR for Privilege will populate various Result fields to help filter and prioritize categories of documents for review. - Second paragraph: When prioritizing documents for aiR for Privilege, it is important to understand the concepts of Precision and Recall: - Headings: H1: Prioritize documents for review | H2: Predicted Privileged documents | H2: Predicted Not Privileged documents - [Privilege results] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Privilege_results.htm): Once the Populate Privilege Results pipeline step completes successfully results will begin to populate on documents. Learn about privilege results and more. - Headings: H1: Review privilege results - [Privilege results fields] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Privilege_results_fields.htm): Once the Populate Privilege Results pipeline step completes successfully, results will begin to populate on documents at about 2,000 documents per hour. To check if the results have been populated, run a search that looks at Priv::Prediction is SET and Priv Project=[the name of the current project] and confirm the document count matches number of documents in the original project saved search. - Second paragraph: Results will never be overwritten or updated after the completion of  Populate Privilege Results. - Headings: H1: Privilege results fields | H2: Variability of results | H2: Results fields | H2: Privilege categories | H2: Document errors | H3: Error messages | H2: Ungrounded Citations - [Project pipeline steps] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Project_pipeline_steps.htm): Each aiR for Privilege project has a dedicated set of pipeline steps that must be completed in sequential order to generate document results. Learn about project pipeline steps. - Second paragraph: Pipeline steps should be performed by a Project Manager. For more information see Roles and security permissions. - Headings: H1: Project pipeline steps | H2: Privilege project version | H2: Pipeline step throughput benchmarks | H2: Pipeline step notifications | H2: Abandon a project - [Propagate results to family members] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Propagate_results_to_family_members.htm): aiR for Privilege focuses on analyzing the text within the four corners of each document. aiR for Privilege bases privilege determinations solely on the content of the individual document. Determinations are not automatically propagated to family member documents such as email attachments or related threads. - Second paragraph: Following is the suggested workflow for propagating results to family members: - Headings: H1: Propagate results to family members | H2: Suggested workflow - [Roles and security permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Roles_and_security_permissions.htm): We suggest creating three user groups to complete an aiR for Privilege project. Learn about each user group and required permissions. - Second paragraph: The aiR for Privilege option found on the Features tab consists of a collection of the required permissions from the other three tabs. Once you enable the aiR for Privilege toggle, its associated permissions are automatically enabled. - Headings: H1: Roles and security permissions | H2: Manual permissions | H2: Instance level permissions - [Use Draft Log Descriptions] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Use_Draft_Log_Descriptions.htm): aiR for Privilege generates Draft Log Descriptions for documents predicted as Privileged. Each description is generated individually for each document based on available content within the extracted text and insights identified by the aiR for Privilege pipeline steps. - Second paragraph: aiR for Privilege utilizes a standardized format as a guide to write all draft log descriptions. The draft log description is typically structured with the following sections: - Headings: H1: Use Draft Log Descriptions | H2: Handling Draft Log Descriptions for family propagations - [Validate Attorneys] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Privilege/Validate_Attorneys.htm): The Validate Attorneys pipeline step locates email addresses and other alias formats used to communicate within your data set, assigns them an individual owner or entity. Learn about the Validate Attorneys pipeline step. - Second paragraph: This step will influence the default Entity Privilege Designation which can be revised on the Confirm Entity Privilege Designation step. - Headings: H1: Validate Entities | H2: Requirements | H2: Actions | H2: Errors ### aiR for Review - [aiR Custom Analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/CustomAnalysisType.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: We’re excited to invite you to participate in the Advanced Access (AA) program for Custom Analysis; a new RelativityOne capability that introduces unprecedented flexibility to document review and extensibility to additional legal data intelligence (LDI) use cases. - Headings: H1: aiR Custom Analysis (Advanced Access) | H2: Overview | H2: The Custom Analysis Framework | H2: AA Program Plan | H2: Feedback | H2: Help and Support | H2: Key Features Available in the Custom Analysis Advanced Access Program | H3: Custom Fields | H3: Behavior and Output | H3: Managing Custom Analysis Fields | H2: Feature documentation | H3: Installation | H3: Configuration | H3: Setting Up a Project | H3: Creating and Managing Custom Analysis Fields | H3: Running an Analysis Job | H3: Viewing the Results | H2: Frequently Asked Questions - [aiR for Review] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/aiR_for_Review.htm): aiR for Review is powered by generative AI, large language models (LLM), and natural language processing to examine extracted document text based on your prompt instructions. It helps pinpoint significant documents, explains their significance, and provides citations from those documents. - Second paragraph: A few benefits of application include: - Headings: H1: aiR for Review | H2: aiR for Review process overview | H2: aiR for Review phases | H2: Analysis review types | H2: How it works | H2: Security and privacy | H2: Generating document summaries | H2: aiR units and billing | H2: Deployment and processing geographies | H2: Language support | H2: Analyzing emojis - [aiR for Review prompt criteria validation] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/aiR_for_Review_prompt_criteria_validation.htm): Using aiR for Review and Review Center in tandem, the prompt criteria validation process gathers statistical metrics to check whether the prompt criteria are effective and defensible before using them on a larger data set. You can set up a smaller document sample, oversee reviewers, compare aiR's relevance predictions to actual coding results, and iterate on prompt criteria as needed. - Second paragraph: This functionality is currently only enabled for the Relevance and Relevance & Key analysis types. See Choosing an analysis type for descriptions of these analysis types. - Headings: H1: aiR for Review prompt criteria validation | H2: Prerequisite | H2: Benefits of validation | H2: How validation fits into aiR for Review | H2: High-level prompt criteria validation workflow - [Analyzing aiR for Review results] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/aiR_for_Review_results.htm): When aiR for Review analyzes documents, it makes predictions about the relevance of documents to different topics or issues. If it predicts that a document is relevant or relates to an issue, it includes a written justification of that prediction, as well as a counterargument and in-text citations. You can view these predictions, citations, and justifications either from the Viewer, or as fields on document lists. - Second paragraph: After analyzing a document, aiR for Review provides a Prediction, a Score with recommendations on how to categorize the document, and the supporting Rationale for prediction. You can use this information to help update and improve your prompt criteria. - Headings: H1: Analyzing aiR for Review results | H2: How aiR for Review analysis results work | H3: Document summaries | H3: Predictions versus document coding | H3: Variability of results | H2: Understanding document scores | H2: How document errors are handled | H2: Ungrounded citations - [Archiving and restoring workspaces with aiR for Review] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Archiving_and_restoring_workspaces.htm): Workspaces with aiR for Review installed can be archived and restored using the ARM application. For more information on using ARM, see ARM overview. - Second paragraph: When you use ARM to archive workspaces with aiR for Review installed, select the Include Extended Workspace Data option under Extended Workspace Data Options. If this option is not selected, the aiR for Review features in the restored workspace will not be fully functional. If this happens, you must reinstall aiR for Review in the restored workspace. See Installing aiR for Review for installation steps. - Headings: H1: Archiving and restoring workspaces with aiR for Review | H2: Archiving workspaces | H2: Restoring workspaces - [Best practices] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Best_Practices.htm): Refer to the tips and recommendations below for prompt criteria and sample document sets to effectively use aiR for Review for all analysis types. - Second paragraph: The prompt criteria entered often aligns with a traditional review protocol or case brief in that they describe the matter, entities involved, and what is pertinent to the legal issues at hand. - Headings: H1: Best practices | H2: Tips for writing prompt criteria | H2: General prompt criteria iteration workflow | H2: Tips for creating sample documents set - [Best practices guide for Custom Analysis field descriptions] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Best_practices_for_Custom_Analysis_field_descriptions.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: Small changes in how you write your field descriptions can dramatically improve quality and consistency. - Headings: H1: Best practices guide for Custom Analysis field descriptions (Advanced Access) | H2: General tips | H3: Ask for one thing at a time | H3: Describe how to handle edge cases | H3: Give brief positive and negative examples | H3: Specify the output format | H3: Assign a role for context | H2: Extraction tips | H3: Normalize extracted values | H3: Handle multi-value fields | H3: Anchor to document structure | H2: Classification tips | H3: Define all valid categories up front | H3: Include a catch-all category | H3: Define decision boundaries for ambiguous cases | H2: Narrative/Insight tips | H3: Constrain output length and focus | H3: Require evidence and citations | H3: Separate observations from inferences - [Creating an aiR for Review project] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Creating_an_aiR_for_Review_project.htm): The instructions you give aiR for Review are called prompt criteria. They often mimic a traditional review protocol or case brief in that they describe the matter, entities involved, and what is relevant to the legal issues at hand. To help improve results, we recommend analyzing a small set of documents, tweaking the prompt criteria as needed, then finally analyzing a larger set of documents. Starting with a small set allows you to evaluate how aiR for Review's coding compares to a human reviewer's coding and adjust the prompts accordingly. - Second paragraph: Refer to Best practices for more information on prompt criteria tips, sample workflow guidance, and iteration workflow. - Headings: H1: Creating an aiR for Review project | H2: Project workflow | H2: Job capacity, size limitations, and speed | H3: Size limits | H3: Volume limits | H3: Speed - [Creating document views and saved searches] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Creating_document_views_and_saved_searches.htm): In addition to using the dashboard, you can view and compare the results for large groups of documents by adding their fields to document views and saved searches. - Second paragraph: Each field name is formatted as aiR ::. For example, the Prediction field for a Relevance analysis is called aiR Relevance Analysis::Prediction. - Headings: H1: Creating document views and saved searches | H2: Creating an aiR for Review results view | H2: aiR for Review results fields | H3: aiR Summaries fields | H3: aiR Relevance Analysis fields | H3: aiR Issues Analysis fields | H3: aiR Key Analysis fields | H3: aiR Confidential Business Information Analysis fields - [Deleting an aiR for Review project] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Deleting_a_project.htm): Use Mass Operations to delete one or more projects from the project list. For more information on Mass delete, see Mass delete documentation. - Second paragraph: Mass delete is permanent action, so be sure to double-check your selections before proceeding. This operation cannot be undone. - Headings: H1: Deleting an aiR for Review project | H2: Hiding document analysis results in the Viewer after deleting a project - [Developing Prompt Criteria] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Developing_prompt_criteria.htm): The prompt criteria are a set of inputs that provide aiR for Review with the necessary context it needs to understand the matter and evaluate each document based on the provided criteria. Developing these criteria is essential for training aiR for Review as a "reviewer," paralleling the process of preparing a human reviewer. See Best practices for tips and workflow suggestions. - Second paragraph: Depending on the selected analysis type during set up, the prompt criteria panel in the dashboard will display different tabs. To assist in writing your initial prompt criteria, fields include italicized, grayed-out helper text offering example entries. Use it for reference when drafting your own criteria. - Headings: H1: Developing prompt criteria | H2: General prompt criteria workflow | H2: Entering prompt criteria | H2: Prompt criteria tabs and fields | H3: Case Summary tab | H3: Relevance tab | H3: Key Documents tab | H3: Issues tab | H3: Confidential Business Information tab | H2: Using prompt kickstarter | H2: Editing and collaboration | H2: How prompt criteria versioning works | H2: How prompt criteria versions affect the Viewer - [Exporting analysis results] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Exporting_Analysis_Results.htm): The Export to File (.xlsx) feature in Mass Ops lets you easily export your analysis results to an Excel (.xlsx) file so you can view data offline, share it with others, and compare information. - Second paragraph: If you want to send analysis results to Review Center, see Using aiR for Review with Review Center. - Headings: H1: Exporting analysis results | H2: Export capacity | H2: Exported file structure | H2: Exporting document summaries - [Exporting Prompt Criteria] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Exporting_prompt_criteria.htm): You can export the contents of all available criteria tabs for the currently displayed prompt criteria to an MS Word (.docx) file. This can be helpful for reviewing criteria, saving it to use later, and collaborating with others on it. - Second paragraph: Audit logs track all export actions from your project. - Headings: H1: Exporting prompt criteria - [Installation] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Installing_aiR_for_Review.htm): aiR for Review is available as a secured application from the Application Library. You must have an active aiR for Review contract to use it. It is not available for repository workspaces. - Second paragraph: To install it in the workspace: - Headings: H1: Installing aiR for Review | H2: Object types available | H2: Tabs available | H2: Configuring aiR for Review job size limits - [Managing aiR for Review jobs] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Monitoring_aiR_for_Review_jobs.htm): Use the aiR for Review Jobs tab to monitor job progress, view prompt criteria details, or cancel the job. You can also view completed jobs and choose which analysis results are connected to the documents. Additionally, authorized administrators can configure job size limits per user group at the instance level to help control and manage the size of jobs that users execute. - Second paragraph: There are two versions of the aiR for Review Jobs tab: one at the instance level, and one at the workspace level. - Headings: H1: Managing aiR for Review jobs | H2: aiR for Review Jobs tab | H2: Setting aiR for Review job size limits | H2: How aiR for Review document linking works | H2: Managing jobs and document linking | H2: Viewing job details | H2: Jobs tab fields - [Navigating the aiR for Review dashboard] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Navigation.htm): When you select a project from the aiR for Review Projects tab, a dashboard displays showing the project's prompt criteria, the list of documents, and controls for editing the project. If the project has been run, it also displays the results. - Second paragraph: At the top of the dashboard, the project details strip displays: - Headings: H1: Navigating the aiR for Review dashboard | H2: Project details strip | H2: Prompt criteria panel | H2: Aspect selector bar | H2: Project metrics section | H3: Version Metrics tab | H3: History tab | H2: Results and summaries | H3: Analysis Results tab | H3: Summaries tab | H3: Viewing inline highlighting and citations in the Viewer | H3: Filtering and selecting documents for analysis | H3: Clearing selected documents | H3: Saving selected documents as list - [Permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Permissions.htm): Feature Permissions is the primary location for managing access to Relativity features. Use the Features tab to quickly set permissions at the instance level and per group user role at the workspace-level: Administrators, Power Users, Basic Users, and Reviewers user roles. When you enable a feature, Relativity automatically applies the required permissions in the background so authorized users can access it. Permissions need to be configured at the instance level and the workspace level. - Second paragraph: For details on Features Permissions, see Feature permissions. See Instance-level permissions and Workspace-level permissions for details on setting up aiR for Review permissions. - Headings: H1: Permissions | H2: Instance-level permissions | H2: Workspace-level permissions - [Prompt Criteria validation in Review Center] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/aiR_for_Review_validation_in_RC.htm): When you validate aiR for Review Prompt Criteria, the validation process compares aiR for Review's AI-based relevance predictions to human coding decisions. Review Center calculates the validation statistics and helps you organize, track, and manage the human side of the coding process. - Second paragraph: See these related pages: - Headings: H1: Prompt Criteria validation in Review Center | H2: How Review Center fits into the validation process | H2: Managing the coding process | H3: Administering the queue | H3: Coding in the queue | H2: Reviewing validation statistics | H3: Choosing a cutoff score | H2: Accepting or rejecting results | H3: Manually rejecting validation results | H3: Viewing results for previous validation queues | H2: How changes affect the validation results | H3: Scenarios that require recalculation | H3: Scenarios that require a new validation queue | H3: Recalculating validation results - [Prompt Criteria validation statistics] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/aiR_for_Review_validation_statistics.htm): aiR for Review Prompt Criteria validation provides several metrics for evaluating your Prompt Criteria. Together, these metrics can help you determine whether the Prompt Criteria will work as expected across the full data set. - Second paragraph: Because Prompt Criteria validation is checking the effectiveness of the Prompt Criteria, rather than checking completeness of a late-stage review, these statistics are calculated slightly differently than standard Review Center validation statistics. For the standard Review Center metrics, see Review validation statistics. - Headings: H1: Prompt Criteria validation statistics | H2: Defining the validation statistics | H2: How documents are categorized for calculations | H3: Variables used in the metric calculations | H3: How validation handles skipped documents | H2: Prompt Criteria validation metric calculations | H3: Elusion rate | H3: Precision | H3: Recall | H3: Richness | H3: Error rate | H2: How the confidence interval works | H2: How Prompt Criteria validation differs from other validation types - [Revising the Prompt Criteria] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Revising_the_prompt_criteria.htm): After running an aiR for Review job for the first time on the sample set, the initial results on the dashboard can be used as feedback for refining the prompt criteria. The cycle of examining the results, revising the prompt criteria, then running a new job on the sample documents is known as iterating on the prompt criteria. Refer to Best practices for more information. Also see Job capacity, size limitations, and speed for details on document and prompt limits. - Second paragraph: In particular, ask the following questions about each document: - Headings: H1: Revising the prompt criteria - [Running the analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Applying_the_analysis.htm): After setting up the project and developing the prompt criteria, you're ready to run the analysis against the prompt criteria. - Second paragraph: To run the analysis: - Headings: H1: Running the analysis - [Setting up aiR for Review prompt criteria validation] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Setting_up_aiR_for_Review_Prompt_Criteria_validation.htm): Prompt criteria validation is currently only available for the Relevance and Relevance & Key analysis types. See Choosing an analysis type for descriptions of these analysis types. - Second paragraph: The general workflow involves: - Headings: H1: Setting up aiR for Review prompt criteria validation | H2: Applying the validated results or developing different prompt criteria | H2: Validation Settings fields - [Setting up the project] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Setting_up_the_project.htm): Begin by configuring the aiR for Review project, selecting the appropriate type of analysis, and specifying the desired data source (saved search). The aiR for Review project serves as a repository for all iterative project sets—develop, validate, and apply—that are created during the refinement of prompt criteria. - Second paragraph: After the project is set up, proceed with developing prompt criteria and running an analysis. - Headings: H1: Setting up the project | H2: Choosing the data source | H2: Choosing an analysis type | H2: Setting up an aiR for Review project - [Using aiR for Review with Review Center] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Using_aiR_for_Review_with_Review_Center.htm): You can use aiR for Review and Review Center in tandem as part of a larger review workflow. When you use them together, aiR for Review provides the set of documents to Review Center, and Review Center helps you serve the selected documents to human reviewers. - Second paragraph: Validating aiR for Review prompt criteria involves comparing AI-generated relevance predictions generated in aiR with human coding results in Review Center on a sample of the document set. After it’s validated, you can choose to run the prompt criteria on the larger document population. For more information, see aiR for Review prompt criteria validation. - Headings: H1: Using aiR for Review with Review Center | H2: Using prompt criteria validation | H2: Using aiR to create a Review Center queue | H3: Selecting documents to add to a queue | H3: Creating a saved search queue through the aiR for Review dashboard - [Using project sets] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Using_Project_Sets.htm): Project sets make it easier to manage and refine prompt criteria for aiR for Review projects. They let you create new sets within a single aiR project so you can iterate without having to start over with a new aiR project. You can use these sets to change saved searches (data sources) during prompt criteria development, to switch between sets to review results, or to start prompt criteria validation in Review Center. - Second paragraph: The project set workflow outlined below aligns with aiR for Review’s phases (see aiR for Review phases). - Headings: H1: Using project sets | H2: Navigating the project set details strip | H2: Creating a new project set | H2: Validating the prompt criteria | H2: Applying the prompt criteria - [Viewing and filtering analysis results] (https://help.relativity.com/RelativityOne/Content/Relativity/aiR_for_Review/Viewing_and_filtering_results.htm): aiR for Review analysis results can be viewed from the dashboard or the Viewer. - Second paragraph: Within a project, you can view results using the aiR for Review dashboard. This dashboard includes not just results fields, but calculated metrics such as the number of documents with predictions that conflict with human coding. - Headings: H1: Viewing and filtering analysis results | H2: Viewing results from the aiR for Review dashboard | H2: Viewing results for individual documents from the Viewer | H3: Citations and highlighting | H3: Adding aiR for Review fields to layouts | H2: Filtering and sorting aiR for Review results ### Analytics - [Alias object] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Alias_object.htm): The “aliases” for an author are other textual representations of the author that are equated as the same entity. For example, John Doe sends an email using the email address john.doe@example.com. He may have another email address, such as john.doe@gmail.com. Based on these email addresses, the Analytics engine finds they are related and can make an alias list that would include "John Doe" and "Doe, John" and "john.doe@gmail.com" and "john.doe@example.com. - Second paragraph: Aliases are identified during the name normalization operation in Analytics. For more information, see Name normalization. You can also manually create an alias. - Headings: H1: Alias object | H2: Creating and editing an alias | H2: Assign to Entity | H2: Deleting an alias - [Analytics categorization set tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Analytics_categorization_sets.htm): Using categorization, you can create a set of example documents that Analytics uses as the basis for identifying and grouping other conceptually similar documents. Categorization is useful early in a review projects when you understand key concepts of a case and can identify documents that are representative examples of these concepts. As you review documents in the Relativity viewer, you can designate examples and add them to various categories. You can then use these examples to apply categories to the rest of the documents in your workspace. - Second paragraph: Using categorization, you can create a set of example documents that Analytics uses as the basis for identifying and grouping other conceptually similar documents. Categorization is useful early in a review project when you understand key concepts of a case and can identify documents that are representative examples of these concepts. After you review documents in the Relativity viewer, you can designate examples and add them to various categories. You can then use these examples to apply categories to the rest of the documents in your workspace. - Headings: H1: Analytics categorization sets | H2: Creating a categorization set | H3: Fields | H2: Identifying effective example documents | H3: Best practices for adding example documents | H2: Categorizing documents | H2: Searching on categorization results - [Analytics index quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Analytics_index_QRG.htm): For more detailed information, see the Analytics section of the documentation site. - Second paragraph: Index creation consists of three stages: Population, Building, and Activating. The following steps occur during each stage: - Headings: H1: Analytics index quick reference guide | H2: Creating an Analytics conceptual index | H2: Index stages | H3: Population | H3: Building | H3: Activating | H3: Common workflows - [Analytics indexes] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Analytics_indexes.htm): Unlike traditional searching methods like dtSearch, Analytics is an entirely mathematical approach to indexing documents. It doesn’t use any outside word lists, such as dictionaries or thesauri, and it isn’t limited to a specific set of languages. The language, concepts, and relationships are defined entirely by the contents of your documents and learned by the index. Unlike textual indexing, word order is not a factor. The indexing process is based solely on term co-occurrence. - Second paragraph: The basis of conceptual analytics is a conceptual index. This uses Latent Semantic Indexing (LSI) to discover concepts between documents. This indexing process is based solely on term co-occurrence. The language, concepts, and relationships are defined entirely by the contents of your documents and learned by the index. For more information, see Analytics and Latent Semantic Indexing (LSI). - Headings: H1: Analytics indexes | H2: Analytics and Latent Semantic Indexing (LSI) | H3: Concept space | H3: Concept rank | H2: Creating an Analytics index | H3: Index creation fields | H2: Securing an Analytics index | H2: Data source and training data source considerations | H3: Training data source considerations | H3: Optimize training set | H3: Data source considerations | H3: Identifying data source and training data source documents | H2: Index and document size limits | H3: Index size limits | H3: Document size limits | H2: Analytics index console operations | H3: Populating the index | H3: Building the index | H3: Monitoring population/build status | H3: Document breakdown fields | H3: Activating the index | H3: Retrying exceptions | H3: Viewing index document exceptions | H3: Showing population statistics | H3: Showing index statistics | H2: Best practices for updating an index | H3: Incremental population considerations | H2: Linking repeated content filters to an index | H3: Automatically linking repeated content filters | H3: Manually linking repeated content filters - [Analytics overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Analytics.htm): Relativity Analytics helps you organize and assess the semantic content of large, diverse and/or unknown sets of documents. Using these features, you can cut down on review time by more quickly assessing your document set to facilitate workflow. - Headings: H1: Analytics | H2: Structured Analytics | H2: Conceptual Analytics | H2: Sentiment Analysis | H2: AV Transcription | H2: Knowledge base articles | H2: On-demand training | H2: White papers - [Analytics profiles] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Analytics_profiles_tab.htm): Analytics profiles apply to email threading and name normalization structured analytics sets. Before creating a structured analytics set for email threading or name normalization, you must create an Analytics profile to map applicable email field settings. Analytics profiles are reusable and transferable, which means you don - Second paragraph: The Analytics application must be installed in the workspace in order to set the fields on an Analytics profile. - Headings: H1: Analytics profiles | H2: Creating or editing an Analytics profile | H2: Fields | H3: Message ID Email Metadata - [Best practices for name normalization] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Best_practices_for_name_normalization.htm): This topic provides best practices for setting up a structured analytics set to run name normalization. - Second paragraph: See these related pages: - Headings: H1: Best practices for name normalization | H2: Pre-work | H2: Setting up the structured analytics set | H3: Dealing with mixed-language data sets | H3: Mapping fields | H3: Identifying a priority custodian | H2: Handling unclear or unexpected results | H2: Alternative workflow using regular expressions (RegEx) - [Cluster Visualization] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Cluster_visualization.htm): Cluster Visualization renders your cluster data as an interactive map allowing you to see a quick overview of your cluster sets and quickly drill into each cluster set to view subclusters and conceptually-related clusters to assist with the following. - Second paragraph: This can assist you with the following actions: - Headings: H1: Cluster visualization | H2: Visualizing a cluster | H3: Adding a cluster visualization widget to your Dashboard | H3: Selecting a new cluster set to visualize | H2: Understanding the types of cluster visualizations | H3: Circle pack | H3: Dial visualization | H3: Nearby clusters | H2: Using the Document Breakdown chart | H2: Applying filters to visualized clusters | H3: Applying cluster filters from the circle pack visualization panel | H3: Applying filters from the dial visualization | H3: Applying cluster filters from the nearby clusters visualization panel | H3: Editing cluster filters | H3: Applying saved search and field filter conditions to your cluster visualization | H3: Applying views to Cluster Visualization | H2: Understanding the Cluster Visualization heat map | H3: Circle pack Visualization | H3: Dial Visualization | H3: Highlighting matches (circle pack) | H2: Working with the document list | H2: Sampling clusters - [Clustering] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Clustering.htm): Analytics uses clustering to create groups of conceptually similar documents. With clusters, you can identify conceptual groups in a workspace or subset of documents using an existing Analytics index. Unlike categorization, clustering doesn - Second paragraph: When you submit documents for clustering, the Analytics engine determines the positions of the documents in the conceptual index. Depending on the conceptual similarity, the index identifies the most logical groupings of documents and places them into clusters. Once the Analytics engine creates these clusters, it runs a naming algorithm to label each node in the hierarchy appropriately to refer to the conceptual content of the clustered documents. - Headings: H1: Clustering | H2: Creating or replacing a cluster | H3: Fields | H2: Default settings for automatically created clusters | H2: Replacing an existing cluster | H2: Viewing clusters | H2: Deleting a cluster - [Communication Analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Communication_analysis.htm): The Communication Analysis widget is a new dashboard widget for Analytics. After running the name normalization operation within structured analytics, you can use this widget to visualize communication frequencies, patterns, and networks between the entities linked to the documents in the view. - Second paragraph: The Communication Analysis Widget permission grants group members permission to add the Communication Analysis widget to a dashboard via the Add Widget drop-down menu. Groups without this permission can still view and interact with the Communication Analysis widget assuming they have access to the dashboard the widget is part of. - Headings: H1: Communication Analysis | H2: Security permissions | H2: Adding the Communication Analysis widget to your dashboard | H2: Understanding the Communication Analysis widget | H3: Nodes | H3: Links | H3: Communication Analysis widget options | H2: Filtering the Communication Analysis widget - [Concept searching] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Concept_searching.htm): You can use Concept searching to find information without a precisely phrased query by applying a block of text against the database to find documents of similar conceptual content. This can help prioritize or find important documents. - Second paragraph: Concept searching is very different from keyword or metadata search. A concept search performed in Analytics reveals conceptual matches between the query and the document quickly and efficiently, so you can focus on the concepts that you deem important. The following table illustrates the differences between standard searching and concept searching. - Headings: H1: Concept searching | H2: Benefits of concept searching | H2: Permissions and special considerations | H2: Running a concept search from the viewer | H3: Navigating results | H3: Changing the active index | H2: Running a concept search from the Documents tab - [Conceptual analytics] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Conceptual_analytics.htm): Conceptual analytics helps you organize and assess the semantic content of large, diverse and/or unknown sets of documents. Unlike structured analytics, which relies on the specific structure of the content, conceptual analytics focuses on related concepts within documents, even if they don - Second paragraph: After using structured data analytics to group your documents, you can run Analytics operations to identify conceptual relationships present within them. For instance, you can identify which topics contain certain issues of interest, which contain similar concepts, and which contain various permutations of a given term. - Headings: H1: Conceptual analytics | H2: Conceptual analytics versus structured analytics - [Conceptual analytics setup basics] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Conceptual_analytics_setup_basics.htm): Set up a saved search which will become the data source for the index. This searches for documents with Extracted Text smaller than 30 MB. - Second paragraph: Use the following conditions and fields: - Headings: H1: Conceptual analytics setup basics | H3: Creating the Analytics index | H3: Adding repeated content filters | H2: Analytics categorization sets | H3: Creating workspace fields | H3: Creating a category designations layout and assigning examples | H3: Sample layout | H3: Creating the categorization set | H2: Clustering | H2: Find similar documents, keyword expansion, and concept searching - [Email thread visualization] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Email_thread_visualization.htm): The email thread visualization tool is available for any email threading jobs run as full builds. Upon job completion, the visualization is available from the document viewer when you open a document. - Second paragraph: Email thread visualization can improve efficiency as follows: - Headings: H1: Email thread visualization | H2: Requirements for email thread visualization | H3: Security permissions | H2: Launching the email thread visualization tool | H2: Common icons and navigation | H3: Loading documents from the visualization pane | H3: Navigation icons | H3: Email type icons | H3: Message and file type icons | H3: Using zoom controls | H3: Using the legend | H3: Using the email icon hover tooltip | H2: Selecting a different structured analytics set | H2: Mass editing using email thread visualization | H2: Using coding highlighting | H3: Coding highlighting considerations | H3: Changing the color associated with a coding choice - [Email threading] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Email_threading.htm): Relativity Analytics Email Threading greatly reduces the time and complexity of reviewing emails, by gathering all forwards, replies, and reply-all messages together. Email threading identifies email relationships, and extracts and normalizes email metadata. Email relationships identified by email threading include. - Second paragraph: This page talks about how email threading works. For steps to set it up, see Running structured analytics. - Headings: H1: Email threading | H2: Email threading overview | H2: Minimum threading requirements | H2: Email threading fields | H2: Email duplicate spare messages | H3: Properties considered during Email Duplicate Spare analysis | H3: Properties ignored during Email Duplicate Spare analysis | H3: Email duplicate spare information storage | H2: How email threading handles unsupported header languages | H2: Optional email threading fields | H3: Email threading and the Gmail metadata fields | H3: Email threading and the Microsoft Conversation ID field | H2: Using an exclusion list for email threading | H3: Guidelines for writing exclusion lists | H2: Indentation levels and the email threading ID | H3: Example 1 | H3: Example 2 | H2: General email threading considerations - [Email threading and TND setup basics] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Email_threading_and_TND_setup_basics.htm): This quick reference guide contains basic workflows for setting up the following: - Second paragraph: For more detailed information, see the Analytics section of the documentation site. - Headings: H1: Email threading and TND setup basics | H2: Email threading only setup | H3: 1. Workspace fields setup | H3: 2. Saved Search Setup | H3: 3. Analytics Profile Setup | H3: 4. Creating a structured analytics set | H3: 5. Email Threading views | H2: Textual near duplicate identification (TND) only setup | H3: 1. Workspace fields setup | H3: 2. Saved Search Setup | H3: 3. Creating a structured analytics set | H3: 4. TND views | H2: Email Threading & TND Setup | H3: 1. Workspace Fields Setup | H3: 2. Saved Search Setup | H3: 3. Analytics Profile Setup | H3: 4. Structured Analytics Set | H3: 5. Views - [Email threading results] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Email_threading_results.htm): After running an email threading operation, we recommend reviewing the available reports. You can then create an Email Threading view in the Documents tab to inspect your email threading results. - Second paragraph: Inclusive, non-duplicate emails have black square indentation squares in the Email Threading Display field. If the emails with black indentation squares aren't actually inclusive, your extracted text format doesn't meet the formatting requirements. See Supported email header formats. - Headings: H1: Email threading results | H2: Viewing the Email Threading Summary | H2: Setting up an email threading view | H2: Thread Groups in the related items pane | H2: Email Threading Display | H3: Indentation squares | H3: Message and file type icons | H2: Working with email threading results | H3: Using the email thread visualization (ETV) tool | H3: Branched emails in thread - [Find similar documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Similar_document_detection.htm): Find similar documents identifies a group of related documents and displays them as search results in the Related Items Pane. The documents are ranked based on conceptual similarity of their content in the concept space rather than a strict word comparison. - Second paragraph: When you click Find Similar Documents in the Viewer, the entire document is submitted as a query string. The process is similar to a concept search, except instead of a query string, the whole document's position in the concept space is used as the query. A hit sphere with minimum concept rank of 60 is drawn around the document, and any documents that are within that hit sphere are returned as search results. This minimum rank value is not configurable. - Headings: H1: Find similar documents | H2: Permissions and special considerations | H2: Running find similar documents from the viewer | H2: Navigating results | H2: Changing the active index | H2: Changing the results panel columns - [Inclusive emails] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Inclusive_emails.htm): There are two types of email messages in Structured Analytics. - Second paragraph: By reviewing only inclusive emails and skipping duplicates, your review process will be much more efficient. The Analytics engine derives the email threads and determines which subset of each conversation constitutes the minimal inclusive set. Non-inclusive emails are redundant because all non-inclusive content is also contained in inclusive emails. The inclusiveness analysis ensures that even small changes in content will not be missed by reviewers. - Headings: H1: Inclusive emails | H2: Common inclusive emails | H2: How signature blocks affect inclusivity | H3: How signature blocks are identified | H3: Example signature block scenarios - [Keyword expansion] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Keyword_expansion.htm): Analytics can position any term, block of text, or document into its spatial index and return the closest documents. It can also return the closest terms. Submitting a single term provides you with a list of highly correlated terms, synonyms, or strongly related terms in your document set. When you submit a block of text or a document, you get a list of single terms that are strongly related to that content. Therefore, because the terms returned are based on the concepts that comprise the search index - Second paragraph: Relativity limits the threshold of this function to 50. Only words with a coherence score greater than 50 will be returned. - Headings: H1: Keyword expansion | H2: Permissions and special considerations | H2: Running keyword expansion from the viewer | H3: Navigating results | H3: Changing the active index | H2: Running keyword expansion from the Documents tab - [Language identification] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Language_identification.htm): Language identification examines the extracted text of each document to determine the primary language and up to two secondary languages present. This allows you to see how many languages are present in your collection, and the percentages of each language by document. You can then easily separate documents by language and batch out files to native speakers for review. - Second paragraph: This page talks about how language identification works. For steps to set it up, see Running structured analytics. - Headings: H1: Language identification | H2: How language identification works | H2: Choosing a field for analysis | H2: Supported languages - [Language identification results] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Language_identification_results.htm): After running language identification, you can review the operation report to get an overview of the results. - Second paragraph: We then recommend using language identification results to organize your workflow. See Using language identification results to drive workflow. - Headings: H1: Language identification results | H2: Viewing the Language Identification Summary | H2: Using language identification results to drive workflow - [Language identification setup basics] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Language_identification_setup_basics.htm): The setup for running language identification is comprised of three components: - Second paragraph: Use the following conditions and fields to create the saved search used for language identification. You do not need to set a sort order on this search. - Headings: H1: Language identification setup basics | H2: Language identification setup | H3: 1. Saved Search Setup | H3: 2. Structured Analytics Set | H3: 3. Language ID view - [Name normalization] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Name_normalization.htm): Name Normalization analyzes email document headers to identify all aliases (proper names, email addresses, etc.) and the entities (person, distribution group, etc.) those aliases belong to. - Second paragraph: This page talks about how name normalization works. For steps to set it up, see Running structured analytics. - Headings: H1: Name normalization | H2: Name normalization overview | H2: Using new name normalization (beta) logic | H3: Why this feature is flagged as beta | H3: Attempting to merge undefined aliases | H2: Using enhanced domain filtering | H3: Differences between default and enhanced domain fields | H3: Creating and exporting a list of domains | H2: Using an exclusion list for name normalization | H3: Guidelines for writing exclusion lists | H2: Adding a Classification value for Legal Hold | H2: Document linking limits | H2: Special considerations - [Name normalization quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Name_normalization_QRG.htm): Name normalization analyzes the email headers, both top-level and embedded, of parent emails. This process creates aliases which are linked to entities. Both aliases and entities are linked to the emails that they participate in. Entities can be pre-populated prior to the name normalization process from other Relativity applications, or from other workspaces. For instance, you can import people subject to Legal Hold as entities to be used by name normalization. - Second paragraph: This quick reference guide provides high-level instructions for running name normalization and various workflows for using its results. Note that some steps might not be necessary to your use case, but we still recommend you review each section to understand what might apply to your situation. - Headings: H1: Name normalization quick reference guide | H2: Special considerations | H3: Requirements | H2: Pre-work | H3: Create and tag entities: custodian, key people, other known participants | H3: Create aliases and assign to pre-created entities | H3: Save aliases or entities as backup | H2: Running the name normalization operation | H3: Create a saved search for emails | H3: Set up the Analytics profile | H3: Create a structured analytics set | H3: Run name normalization | H2: Post-run: verify and clean your results | H3: Delete aliases and re-run | H3: Clean up entities and aliases - [Name normalization results] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Name_normalization_results.htm): After you run the name normalization operation, the structured analytics set displays the number of aliases identified and the number of new aliases. If an alias already exists in Relativity, it isn - Second paragraph: Analytics adds aliases into Relativity under the Alias RDO. You can view these aliases from the Aliases tab under the Entities parent tab. For more information, see Alias object. - Headings: H1: Name normalization results | H2: Aliases | H2: Entities | H2: Documents | H2: Adjusting results | H3: Assign to Entity | H3: Merge | H2: Deleting all data to re-run - [Name normalization setup basics] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Name_normalization_setup_basics_QRG.htm): This quick reference guide contains a basic workflow for setting up name normalization. For more detailed information, see Analytics. - Second paragraph: The setup for running name normalization has three parts: - Headings: H1: Name normalization setup basics | H2: Name normalization setup | H3: 1. Saved search setup | H3: 2. Analytics profile setup | H3: 3. Structured analytics set - [Repeated content filters] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Repeated_content_filters_tab.htm): You can create a repeated content filter or a regular expression filter on the Repeated Content Filters tab in order to improve the quality of an Analytics index. Using a structured analytics set, you can allow Relativity to automatically create repeated content filters by running the repeated content identification operation on a set of documents. - Second paragraph: A repeated content filter finds the text wherever it occurs in each document that matches your configuration parameters and suppresses it from the Analytics index. We recommended using this filter to ensure that the authored content of a document isn't overshadowed by content such as confidentiality footers or standard boilerplates. If included in an Analytics index, disclaimers and other repeated content can create false positive relationships between documents. - Headings: H1: Repeated content filters | H2: Creating a repeated content filter | H2: Fields | H2: Evaluating repeated content identification results | H3: Repeated content filters naming convention - [Repeated content identification setup basics] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Repeated_content_identification_QRG.htm): This quick reference guide contains a basic workflow for setting up repeated content identification. For more detailed information, see Analytics. - Second paragraph: The setup for running repeated content identification is comprised of two components: - Headings: H1: Repeated content identification setup basics | H2: Repeated content identification setup | H3: 1. Saved Search Setup | H3: 2. Structured Analytics Set - [Running name normalization on email headers] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Running_name_normalization_on_email_headers.htm): When running name normalization, email header formats in the extracted text can have a lot of variation and are generally less clean than the top-level headers. Because of this, you may want to initially run name normalization on only the top-level headers (To, From, Cc, Bcc) to produce cleaner results. These results can then be used to help seed additional runs of name normalization. - Second paragraph: See these related pages: - Headings: H1: Running name normalization on email headers | H2: Using email header settings for name normalization | H3: Email header setting combinations | H2: Using regular expressions to force metadata use | H2: Additional regular expression resources - [Running structured analytics] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Running_structured_data_analytics.htm): After creating a structured analytics set, use the Structured Analytics Set console to run your selected operations and view summary reports for each operation type. - Second paragraph: Before you begin working with structured analytics sets, make sure that your user group has the following permissions: - Headings: H1: Running structured analytics | H2: Setting up permissions for structured analytics | H2: Creating a structured analytics set | H3: Structured analytics fields | H3: Email threading fields | H3: Name normalization fields | H3: Textual near duplicate identification fields | H3: Language identification fields | H3: Repeated content identification fields | H2: Structured Analytics Set console | H3: Run structured analytics | H3: Available reports | H3: Error Handling | H3: Deleting a structured analytics set | H3: Status values | H2: Identifying documents in your structured analytics set | H2: Analyzing your results | H2: Copy to Legacy Fields | H3: Using the Copy to Legacy Fields button | H2: Special considerations for structured analytics - [Sampling for repeated content] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Sampling_for_repeated_content.htm): This recipe provides information on using random samples to achieve repeated content identification in a much quicker fashion and with significantly lower resource utilization than running on the full collection - all without sacrificing the quality of the results. - Second paragraph: This topic provides a method of running repeated content identification on random samples from a large document set. The sampling method is more efficient and uses fewer resources than running it on the full set, without sacrificing the quality of the results. - Headings: H1: Sampling for repeated content | H2: Creating the sample | H2: Saving the sample as a list and a saved search | H2: Running repeated content identification as Structured Analytics set | H2: Review results | H2: Setting the minimum number of occurrences - [Structured Analytics] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Structured_analytics_set_tab.htm): Structured analytics operations analyze text to identify the similarities and differences between the documents in a set. - Second paragraph: Use structured analytics to quickly assess and organize a large, unfamiliar set of documents. On the Structured Analytics Set tab, you can run structured data operations to shorten review time, improve coding consistency, optimize batch set creation, and improve Analytics indexes. - Headings: H1: Structured analytics | H2: Structured analytics operations | H2: Structured analytics versus conceptual analytics | H2: Setting up your environment | H2: Archiving and restoring workspaces with structured analytics sets - [Structured analytics quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Analytics/Structured_analytics.htm): This guide provides step-by-step instructions for creating and administering structured analytics. In particular, it discusses how to take advantage of running multiple structured analytics sets on the email threading and textual near duplicate operations. The main sections are as follows: - Second paragraph: This quick reference guide does not explain the operations themselves, but focuses on the administration of the structured analytics features. - Headings: H1: Structured analytics quick reference guide | H2: Creating a Structured Analytics Set | H2: Running and Re-running a Structured Analytics Set | H2: Using the Copy to Legacy Fields button - [Supported email header formats] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Supported_email_header_formats.htm): Email threading and name normalization results may be incorrect if the extracted text isn - Second paragraph: Analytics uses a best-effort approach to parse email messages, but it will not handle all possible cases of badly formed email messages. - Headings: H1: Supported email header formats | H2: Supported email header formats | H2: Supported email header fields | H2: Supported date formats | H2: Reformatting extracted text - [Textual near duplicate identification] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Textual_near_duplicate_identification.htm): While textual near duplicate identification is simple to understand, the implementation is very complex and relies on several optimizations so that results can be delivered in a reasonable amount of time. The following is a simplified explanation of this process. - Second paragraph: This page talks about how textual near duplicate identification works. For steps to set it up, see Running structured analytics. - Headings: H1: Textual near duplicate identification | H2: Textual near duplicate identification overview | H3: How the principal document is determined | H2: Minimum Similarity Percentage | H2: Fields - [Textual near duplicate identification results] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Textual_near_duplicate_identification_results.htm): After running a textual near duplicate identification operation, we recommend reviewing the results using the following. - Second paragraph: See Using near duplicate analysis in review for more details on near duplicates. - Headings: H1: Textual near duplicate identification results | H2: Setting up a Textual Near Duplicates view for a structured analytics set | H3: Textual Near Duplicates view advanced settings | H3: Textual Near Duplicates view fields | H3: Textual Near Duplicates view conditions | H3: Textual Near Duplicates view sorting | H2: Assessing similarities and differences with Document Compare | H2: Viewing the Textual Near Duplicates Summary | H2: Viewing Near Dup Groups in the related items pane - [Using Near Duplicate Analysis in Review] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Using_near_duplicate_analysis_in_review.htm): Relativity can identify textually similar documents to assist in and speed up the review process. Near duplicate analysis is best suited for grouping documents which can then be batched for review based on the similarity, or used to create new document sets for further analysis. The goal is for reviewers to have the ability to see similar documents at the same time based on their textual similarity. - Second paragraph: System admins should create a Textual Near Duplicates (TND) view for the review team. This view will contain only documents that appear in TND groups, not documents which were submitted to the engine but found to be non-matches. - Headings: H1: Using near duplicate analysis in review | H2: Near duplicate analysis overview | H2: Creating a textual near duplicates view | H3: Using the TND view in review | H3: Example - [Using regular expressions with structured analytics] (https://help.relativity.com/RelativityOne/Content/Relativity/Analytics/Using_regular_expressions_with_structured_analytics.htm): When running a structured analytics set for email threading or textual near duplication analysis, it - Second paragraph: By using regular expressions (RegEx), you can filter out extraneous text from structured analytics sets and conceptual analytics indexes. Analytics uses Java's implementation of RegEx. - Headings: H1: Using regular expressions with structured analytics | H2: Textual Analysis | H3: Line breaks | H3: Spaces | H2: Create a sample set | H2: RegEx metacharacters | H2: RegEx groups | H2: RegEx alternation and quantifiers | H2: RegEx flags | H2: Escaping RegEx metacharacters | H2: Analytics RegEx filter examples | H2: RegEx: dtSearch vs. structured analytics ### Applications - [Exporting applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Exporting_applications.htm): You can export applications that you want to install in other workspaces or instances of Relativity. In addition, you may want to export an application for upgrading in your development environment. - Second paragraph: In the Application Library, click on an application to open the details window. You can download the Application File by clicking the link. - Headings: H1: Exporting applications | H2: Downloading application .rap files | H2: Avoiding errors during application export | H2: Application state settings on export | H2: Exporting an application - [Installing applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Installing_applications.htm): Relativity provides you with several different options for installing applications. - Second paragraph: You can add applications across multiple workspaces by installing them to the Application Library. You can do this by installing applications as external files or pushing them from a single workspace. - Headings: H1: Installing applications | H2: Installing applications to the Application Library | H3: Installing an application from an external file to the Application Library | H3: Pushing an application from a workspace to the Application Library | H2: Pushing an application from the Application Library to a workspace | H2: Installing applications to workspaces | H3: Installing applications from the Application Library | H3: Installing an application from an external file to a workspace | H3: Installing applications containing saved searches | H3: Mapping fields | H3: Viewing import status - [Locking and unlocking applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Locking_and_unlocking_applications.htm): Relativity provides you with the ability to edit applications by unlocking them. You can also lock applications to prevent any modifications to them. On the Relativity Application tab, you can use the Lock Application and Unlock Application buttons to perform these operations. You must have the appropriate system admin permissions to lock or unlock an application. - Second paragraph: You can't lock or unlock system secured applications that are shipped with Relativity. The Relativity Application tab doesn't display these options for system secured applications. See System secured applications. - Headings: H1: Locking and unlocking applications | H2: Locking an application | H2: Customizing locked applications | H2: Modifying saved searches in a locked application | H2: Unlocking an application - [Relativity applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Relativity_applications.htm): Relativity applications extend core functionality by providing specialized features or workflows. When you install Relativity, your environment is automatically updated with several applications that are called system secured. - Second paragraph: In addition, you may have workflow requirements or other business needs that require custom applications designed specifically for your organization. Business analysts or third-party developers can implement these applications using Relativity Dynamic Objects (RDOs), the Application Deployment System (ADS), and custom code. For more information about integrations built by Relativity or our Community, see the App Hub. - Headings: H1: Relativity applications | H2: System secured applications | H3: Applications installed in the Application Library | H3: Applications installed in workspaces | H2: Relativity custom applications | H2: Administering Relativity applications | H3: Auditing Relativity applications | H2: Global applications | H3: Viewing global applications - [Troubleshooting application installation errors] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Troubleshooting_application_installation_errors.htm): You can use this page to identify the causes of common application installation errors. - Second paragraph: Use the following table to identify common causes of errors that may occur when you attempt to install an application. You can resolve some of these errors manually through the target workspace or you may be able to resolve them as you install the application. - Headings: H1: Troubleshooting application installation errors | H2: Installation error list | H2: Resolving installation errors | H3: Locking conflicts | H3: Name conflicts | H3: Other errors | H2: Pre and Post Install event handler errors | H3: Failure of Pre Install event handler | H3: Failure of Post Install event handler | H2: Checking the error statuses - [Uninstalling and deleting applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Uninstalling_and_deleting_applications.htm): You can control the applications that workspaces contain by exporting, uninstalling, and deleting them. When you export an application, you have a file that you can use to import it into other workspaces. You can also uninstall or delete applications that you no longer want in a workspace. - Second paragraph: When you uninstall an application, Relativity deletes all child objects and associative objects, unless other applications or dependencies prevent their removal. Relativity also deletes any saved searches your application includes, but retains the associated indexes in the workspace because they are not part of the application. You need system admin permissions to lock or unlock an application. For more information, see Workspace security. - Headings: H1: Uninstalling and deleting applications | H2: Uninstalling applications | H3: Uninstalling an application | H3: Uninstall and modification alerts | H3: Viewing application uninstall errors | H3: Auditing the uninstall process | H3: Manually uninstalling custom pages | H2: Deleting applications - [Upgrading applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Applications/Upgrading_applications.htm): You can upgrade an existing application by using the Upgrade Application option available on its detail view. - Second paragraph: Before you upgrade an application, review the following information: - Headings: H1: Upgrading applications | H2: Upgrading an application | H3: Upgrading an application in a workspace | H3: Upgrading an application through the Application Library | H3: Application resource file purge | H2: Troubleshooting application upgrades | H3: Exporting choices attached to single or multiple choice fields | H3: Custom pages not working properly when multiple application versions exist on the same server | H3: Applications can't be downgraded ### ARM - [ARM] (https://help.relativity.com/RelativityOne/Content/ARM/ARM_Overview.htm): The ARM application allows you to archive, restore, and move Relativity workspaces between Relativity installations or SQL servers. You can also use this application to convert a DBMT archive into an ARM archive. ARM is supported in Relativity versions 9.0-9.3. - Second paragraph: You can run two types of jobs in ARM: - Headings: H1: ARM overview | H2: Job types | H2: Security permissions | H2: Unsupported Relativity data | H2: Considerations before using ARM | H3: General considerations | H3: Analytics considerations | H3: Processing data considerations | H2: Performance considerations for RelativityOne | H2: ARM Jobs tab | H3: Jobs view - [ARM Configuration] (https://help.relativity.com/RelativityOne/Content/ARM/ARM_Configuration.htm): From the ARM tab, select the Configuration subtab to display the Configuration Settings page. Click Edit to modify these settings. - Second paragraph: Click Add to add a new archive location. To delete one from the list, click the trashcan icon. - Headings: H1: ARM Configuration | H2: ARM Archive Locations | H2: Email Notification Settings - [Creating and running a Restore job] (https://help.relativity.com/RelativityOne/Content/ARM/Creating_and_running_a_Restore_job.htm): To create a new Restore job, click New Restore at the top of the ARM Jobs page. The New Restore Job page appears. - Second paragraph: Review the following before running a Restore job: - Headings: H1: Creating and running a Restore job | H2: Considerations | H2: Creating a Restore job | H3: Source & Destination fields | H3: Options fields | H3: Notifications fields | H3: Archive Settings section | H3: Mapping groups | H3: Mapping users | H3: Application restore | H2: Running a Restore job | H3: Job phases and stages | H3: Job statuses | H3: Summary page - [Creating and running an Archive job] (https://help.relativity.com/RelativityOne/Content/ARM/Creating_and_running_an_Archive_job.htm): To create a new Archive job, click New Archive at the top of the ARM Jobs page. The New Archive Job page appears. - Second paragraph: Complete the following steps to create a new Archive job: - Headings: H1: Creating and running an Archive job | H2: Creating an Archive job | H3: Source & Destination fields | H3: Options fields | H3: Processing Options fields | H3: Notifications fields | H2: Running an Archive job | H3: Job phases and stages | H3: Job statuses | H3: Summary page ### Assisted Review - [Assisted Review] (https://help.relativity.com/RelativityOne/Content/Relativity/Assisted_Review/Assisted_Review.htm): Relativity Assisted Review is a feature of Relativity that uses a search technology called categorization to teach Relativity how to determine whether a document is responsive or non-responsive, as well as what issues apply to that document. - Second paragraph: If you are not redirected automatically in 3 seconds, click on Review Center. ### Audit - [Audit] (https://help.relativity.com/RelativityOne/Content/Relativity/Audit/Audit.htm): Audit is an application that you can use to monitor and run reports on audited user activity. With Audit, you can use pivots and visualizations to quickly identify audit activity in your Relativity instance. - Second paragraph: To learn more about common workflows, see Reporting and Monitoring using Audit. - Headings: H1: Audit | H2: Permissions | H3: Key benefits | H2: Supported Audit tab functionality | H3: Audit agents | H2: Audit tab | H3: Advanced Filtering Audit records | H3: Details column | H3: Exporting workspace audits | H2: Instance audits | H3: Filtering on multi-workspace audits | H3: Reverting audited actions | H2: Audit Migration Reports tab | H3: Migration Error Report | H3: Migration Error Retry Script | H3: Migration Status Report | H2: Audit Workspace Settings tab | H3: HistoryTabVisibleOnUpgrade | H2: Audited actions - [Reporting and Monitoring using Audit] (https://help.relativity.com/RelativityOne/Content/Relativity/Audit/Reporting_and_Monitoring_using_Audit.htm): The following use cases cover a few common ways you can use the Audit application to report, monitor, and search through Relativity’s audit records. Use these workflows to help familiarize yourself with the functions and capabilities of the Audit application to help monitor activity in your Relativity instance. - Second paragraph: This use case highlights how you can use Relativity scripts run in a workspace or instance to determine who is running the scripts and if the scripts are causing performance issues in your environment. - Headings: H1: Reporting and monitoring using Audit | H2: Identifying Relativity scripts and long-running queries | H2: Identifying incorrect coding and performing a mass revert | H2: Tracking user access and identifying potential breaches | H2: Aggregating the number of errors over time ### Authentication - [Authentication] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Authentication.htm): Relativity uses several industry-standard technologies, enabling versatile authentication options. It supports local (such as password related), or external (such as smart cards, or external identity providers) authentication methods. You can add and enable each type individually, as well as assigning at least one, and in some instances multiple methods, for each user. You can use authentication providers to configure single sign-on (SSO). - Second paragraph: Review the following sections to learn more about the authentication methods, the object model, and the permissions model supported by Relativity: - Headings: H1: Authentication | H2: Permissions | H2: Authentication overview | H2: Configuring Relativity authentication | H3: Enabling RelativityOne Connect | H2: Authentication provider settings - [Centralized Authentication] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Centralized_Authentication.htm): The Sanitizer object is a Relativity system object that stores the Sanitizer Whitelist information. The Sanitizer Whitelist is used to parse embedded HTML code in HTML-enabled and custom text fields and labels. - Second paragraph: Centralized Authentication supports all types of user authentication, including password and single sign-on (SSO) methods. For SSO, it supports Security Assertion Markup Language (SAML) and OpenID Connect (OIDC). - Headings: H1: Centralized Authentication | H2: Prerequisites | H3: Centralized Authentication workflow | H2: Setting up your Authentication Provider | H3: SSO setup | H3: Edit an SSO Provider | H2: Password Provider setup | H3: Password requirements | H3: Edit a Password Provider | H3: Trusted IP Support | H3: Setting up Trusted IP addresses | H2: Inviting users | H3: Centralized Authentication tab invitation | H3: User tab invitation | H2: Managing user transition | H3: Monitor progress by Authentication Provider | H2: User accepts the invitation | H2: Logging in to RelativityOne | H3: Transition period to Centralized Authentication | H3: Centralized Authentication migration | H3: Reset a User’s Authenticator App - [Federated instances] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Federated_instances.htm): Federated instances provide a way for reviewers to easily switch to other Relativity environments, for example, RelativityOne. In Relativity, links to federated instances appear in the User drop-down. - Second paragraph: For more information, see User options. - Headings: H1: Federated instances | H2: Creating or editing a federated instance | H2: Deleting a federated instance | H2: Viewing a federated instance audit history - [Logging into RelativityOne] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Logging_in_to_Relativity.htm): Relativity offers several ways to log in and it - Second paragraph: For help with single sign-on error messages, please see the SSO Troubleshooting console. - Headings: H1: Logging into RelativityOne | H2: Logging in to RelativityOne with a password | H2: Password | H2: Two-factor authentication | H2: OpenID Connect | H2: SAML 2.0 | H2: Creating or resetting a password - [Managing User Authentication Methods] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Managing_users_authentication_methods.htm): As a system admin, you must assign at least one authentication method to each user in order for them to log in. A user can have multiple login methods but only one from among Password, RSA, and Active Directory. - Second paragraph: A significant security improvement to the Relativity authentication process is that the system admin no longer knows or can set user passwords. The invitation workflow, called that because you invite users to log in to Relativity, is the new mechanism for them to set and to manage their own passwords. Now, a system admin (when creating a new user), or a user (if they forget their password) initiates an email sent to them at their specified address, and they create or reset their password directly within Relativity. - Headings: H1: Managing user authentication methods | H2: Invitation workflow | H3: Password | H3: Two-factor authentication | H3: Password Outside Trusted IP | H3: To define a Trusted IP range: | H3: Password reset | H2: Manually setting passwords | H2: OpenID Connect | H2: SAML 2.0 - [Microsoft Entra ID - OpenID Connect] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Microsoft_Entra_ID_OpenID_Connect.htm): Microsoft Entra ID can be set up as an OpenID Connect authentication provider to log users into a different Relativity instance. You need to complete some steps within Microsoft Entra ID and Relativity to user Entra ID OpenID Connect. - Second paragraph: We support B2C (business-to-customer) SSO integration through the OIDC and SAML2 protocols. Customers whose provider supports either of these protocols can integrate with RelativityOne. The following steps focus on registering an Azure application and credentials for Entra ID. If you're setting up Relativity with EntraID External ID (formerly known as AzureAD B2C), please refer to Microsoft's documentation. - Headings: H1: Microsoft Entra ID - OpenID Connect | H2: Registering an Azure application and credentials | H2: Configuring Entra ID OpenID Connect | H3: Authentication provider information | H3: Authentication provider settings - [OAuth2 clients] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/OAuth2_clients.htm): OAuth2 clients allow you to configure external services and applications to authenticate against Relativity in a secure manner. For example, a client application can present the user with the Relativity login page to get an access token to call Relativity APIs. The application can then use the API to perform tasks for customizing eDiscovery workflows and automation. - Second paragraph: OAuth2 clients can be used in conjunction with Relativity authentication providers and federated instances in different enterprise integration scenarios, including: - Headings: H1: OAuth2 clients | H2: Creating or editing an OAuth2 client | H2: Resetting a client secret | H2: Deleting an OAuth2 client | H2: Viewing an OAuth2 client audit history - [Okta OpenID Connect] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Okta_OpenID_Connect.htm): Okta can be set up as an OpenID Connect authentication provider to log users into a different Relativity instance. - Second paragraph: In Relativity, navigate to the Authentication Provider tab. On the Authentication Provider, fill in the fields as follows: - Headings: H1: Okta OpenID Connect | H2: Pre-requisites | H2: Configuring Okta OpenID Connect | H3: Configure Okta - [OpenID Connect] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/OpenID_Connect.htm): OpenID Connect is an identity layer on top of the OAuth 2.0 protocol. You can verify the identity of the end user based on the authentication performed by an authorization server, as well as to obtain basic profile information about the end user. You can use any provider that supports the OpenID Connect protocol. - Second paragraph: FedRAMP requirements for RelativityOne Gov instances mandate the customer's Authority URL must undergo a review by the Relativity Security team. Following a successful review, the URL will be added to the Relativity firewall allow list prior to setting up single sign-on authentication. - Headings: H1: OpenID Connect | H2: Configuring an OpenID Connect authentication provider | H2: OpenID Connect authentication provider flows | H2: Just-in-time provisioning | H3: Group claim mapping | H3: Required claim | H3: Personal claim group - [Relativity OpenID Connect] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/Relativity_OpenID_Connect.htm): Relativity can be set up as an OpenID Connect authentication provider to log users into a different Relativity instance. For example you can set up a Relativity Server environment (primary instance) to act as authentication provider for a RelativityOne cloud instance (secondary instance). - Second paragraph: Before you begin you must have the following items completed. - Headings: H1: Relativity OpenID Connect | H2: Pre-requisites | H2: Configuring Relativity OpenID Connect - [RelativityOne Connect] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/RelativityOne_Connect.htm): Use a single identity to access all your RelativityOne workspaces and instances with RelativityOne Connect. Securely connect multiple instances and let users navigate between them securely with cross-authentication using a single sign-on provider (SSO). With RelativityOne Connect you can log in to Relativity once and access workspaces across multiple instances that are connected as federated instances. - Second paragraph: Once the connection between the instances is created, the Relativity users can sign in and navigate between workspaces in the different instances. - Headings: H1: RelativityOne Connect | H2: Enabling RelativityOne Connect | H3: Finding instance names | H2: Connecting users to different instances | H2: Navigating between instances | H2: Billing information | H3: User type information | H2: Frequently asked questions - [SAML 2.0 Provider] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/SAML_2.0_provider.htm): SAML is an open-standard format for exchanging authentication and authorization data between an identity provider (IdP) and a service provider (SP). - Second paragraph: As a service provider, Relativity supports SAML IdP-initiated single sign-on (SSO). However, it does not support SP-initiated SSO. - Headings: H1: SAML 2.0 provider | H2: Considerations | H2: Configuring a SAML 2.0 authentication provider | H2: Configuring specific SAML providers - [SSO Troubleshooting console] (https://help.relativity.com/RelativityOne/Content/Relativity/Authentication/SSO_Troubleshooting_console.htm): OAuth2 clients allow you to configure external services and applications to authenticate against Relativity in a secure manner. For example, a client application can present the user with the Relativity login page to get an access token to call Relativity APIs. The application can then use the API to perform tasks for customizing eDiscovery workflows and automation. - Second paragraph: To view and manage the errors in the console: - Headings: H1: SSO Troubleshooting console | H2: Considerations | H2: Viewing the SSO Troubleshooting console ### AV Transcription - [AV transcription] (https://help.relativity.com/RelativityOne/Content/Relativity/AV_Transcription/AV_transcription.htm): The audio-visual (AV) transcription application analyzes audio and video files, then transcribes the spoken words into a text field. This streamlines the process of reviewing AV files and makes it easier to search for keywords, find correlations, and locate relevant files. - Second paragraph: See these related pages: - Headings: H1: AV transcription | H2: How AV transcription works | H3: Data retention and storage | H2: Installing AV transcription | H2: Running AV transcription | H3: Transcription setup fields | H2: How speaker partitioning works | H2: Viewing and managing transcription jobs | H3: Canceling or deleting jobs | H3: Viewing job details and exceptions | H2: Viewing transcription results | H2: Supported file types | H3: Audio channel support | H2: Job capacity and size limits | H2: Archiving and restoring workspaces - [AV transcription in the Viewer] (https://help.relativity.com/RelativityOne/Content/Relativity/AV_Transcription/Audio-visual_transcription_in_the_Viewer.htm): After you transcribe an audio-visual (AV) document, you can see the transcribed text in the Native Viewer and search for terms and view highlighted search hits in the text. To learn more about transcription, see AV transcription. The transcribed text syncs with the AV file to make it easy to track your place within the document. You can also navigate to a location within the document by clicking on the text. - Second paragraph: As you review an AV document, you can see comments that other users have left and add your own. You can also search the text of comments to conveniently locate them. To learn more, see Documents Comments. - Headings: H1: AV transcription in the Viewer | H2: Navigating transcribed documents | H3: Speaker names | H2: Searching the transcribed text | H3: Searching from the Transcript Text panel | H3: Searching from the Contextual Search panel | H2: Persistent Highlighting - [AV transcription languages] (https://help.relativity.com/RelativityOne/Content/Relativity/AV_Transcription/AV_transcription_languages.htm): The audio-visual (AV) transcription application recognizes audio from over 100 languages and regional variants. - Second paragraph: See these related pages: - Headings: H1: AV transcription languages | H2: How transcription languages work | H3: Handling multiple languages | H3: Choosing language locales | H2: Supported languages and locales - [AV transcription permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/AV_Transcription/AV_transcription_permissions.htm): This page contains information on the security permissions required for working with AV Transcription. For more information on setting permissions, see Workspace security. - Second paragraph: To use the Transcribe mass operation, you need the following permission: - Headings: H1: AV transcription permissions | H2: Using the Transcribe mass operation | H2: Viewing and managing transcription jobs | H2: Viewing and managing transcription profiles - [Transcription profiles] (https://help.relativity.com/RelativityOne/Content/Relativity/AV_Transcription/Transcription_profiles.htm): Transcription profiles store a custom combination of AV transcription settings, helping you quickly re-use the same settings across multiple jobs. If you often transcribe files with the same combination of languages, setting up a profile can save time. - Second paragraph: See these related pages: - Headings: H1: Transcription profiles | H2: Creating a transcription profile | H2: Using a transcription profile | H2: Editing or deleting a transcription profile ### Batches - [Assigning batches and checking batches in and out] (https://help.relativity.com/RelativityOne/Content/Relativity/Batches/Checking_batches_in_and_out.htm): Any batches you or another user create for your account appear in the Review Batches tab. You can control which batches reviewers see by. - Second paragraph: You can also restrict the Batches tab so only workspace managers and system admins can see it. In this model, a system admin or a user with Assign Batch permissions would need to check out batches to reviewers as needed. - Headings: H1: Assigning batches and checking batches in and out | H2: Assign a batch or check a batch out | H2: Reassign a batch or check a batch in - [Batches] (https://help.relativity.com/RelativityOne/Content/Relativity/Batches/Batches.htm): You can create batches in Relativity by splitting a static set of documents into multiple document sets based on set by a system admin. With the appropriate permissions, users can then check out these batches and assign themselves documents. - Second paragraph: Batching can bring structure to managing a large-scale document review with multiple reviewers. You can generate batches automatically or manually. Automatic document assignment reduces the chances of accidental redundancy in the review process. - Headings: H1: Batches | H2: Batch fields in Relativity | H2: Creating and editing batch sets | H3: Batch Sets for Reviewers | H3: Fields | H3: Batch Set console | H3: Auto Batching Status | H2: Deleting an individual batch | H2: Deleting a batch set | H2: Searching for documents not in existing batch sets | H2: Batching process overview | H3: No Batch Unit Field or Family Field configured | H3: Batch Unit Field configured; No Family Field configured | H3: Batch Unit Field and Family Field configured | H3: No Batch Unit Field configured; Family Field configured | H3: Exceeding the maximum batch size - [Building views for checked-out documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Batches/Building_views_for_checked-out_documents.htm): You can build views for a reviewer to access their checked-out documents. - Second paragraph: You can build views for a reviewer to see only their checked-out documents that either have not been reviewed yet or have already been reviewed. We recommend creating or designating a field for coding documents before completing these steps. - Headings: H1: Building views for checked-out documents | H2: Build a checked-out documents view ### Case Dynamics - [Case Dynamics] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Case_Dynamics.htm): Case Dynamics, formerly Fact Manager, assists in organizing and analyzing case details such as facts, issues, key organizations, key people, interview questions, and documents. This analysis helps identify strengths and weaknesses in litigation strategy and leads to better preparation for depositions, interviews, and trial. - Second paragraph: Access Case Dynamics using the Case Dynamics tab located in the workspace where you installed the application. - Headings: H1: Case Dynamics | H2: Case Dynamics topics | H2: Case Dynamics life cycle - [Case Dynamics fields] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Case_Dynamics_fields.htm): The following sections describe the object data entry fields used when adding or editing a fact, issue, key organization, key person, or interview question. - Second paragraph: You can view fact details using two different layouts. The Fact Basic Layout organizes item information using tabbed display, and the Fact Extended Layout organizes item information as a list. Both layouts contain the same fields. - Headings: H1: Case Dynamics fields | H2: Fact fields | H2: Issue fields | H2: Interview question fields | H2: Document object fields - [Creating Case Dynamics reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Creating_Case_Dynamics_reports.htm): You can create offline reports to view objects like facts, issues, key people, interview questions, and related documents. The report can be customized to display the objects you wish to view as well as any relevant fields using a custom view. You can also hide objects that do not need to be included in the report by creating a custom layout. This is a convenient feature for reviewing case information while preparing for and during interviews, depositions, and trial. - Second paragraph: The date formatting in offline reports is determined by your internet browser settings and not your operating system. The date format that is selected in your browser when creating an offline report will persist even if you email the report to someone else who has a different date format selected for their internet browser or operating system. - Headings: H1: Creating Case Dynamics reports | H2: Offline report date formatting - [Installing and upgrading Case Dynamics] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Installing_and_upgrading_Case_Dynamics.htm): The Case Dynamics application must be installed in each workspace that you want to use application. - Second paragraph: Keep the following considerations in mind when installing and upgrading Case Dynamics: - Headings: H1: Installing and upgrading Case Dynamics | H2: Case Dynamics compatibility matrix | H2: Special considerations | H2: Installing Case Dynamics | H2: Upgrading Case Dynamics | H2: Security permissions | H3: Control mass actions - [Organizing facts and issues] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Organizing_facts_and_issues.htm): You can organize facts and issues using several methods, including nesting, numeric ordering, drag and drop, and color coding. - Second paragraph: You can create custom fields, views, and layouts on any facts, issues, interview questions, or entity object. For example, imagine you have a case with three rounds of investigation. You create a custom field called Investigation Type with choices for each round - Investigation A, Investigation B, and Investigation C. Then, you create a custom view called Investigation A which returns all facts tagged with Investigation A on the Investigation Type field. - Headings: H1: Organizing facts and issues | H2: Customizing Case Dynamics | H3: Customizing object layouts | H2: Infinite nesting and numeric ordering | H2: Drag and drop | H3: Deleting facts and issues | H2: Assign a color to a new fact | H2: Inline list view organization - [Printing from Case Dynamics] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Printing_from_Case_Dynamics.htm): You can print specific facts, issues, interview questions, and outlines along with associated information, such as documents and excerpts. - Second paragraph: In order to print from Case Dynamics, you must create a Printing Profile. To create a Printing Profile: - Headings: H1: Printing from Case Dynamics | H2: Creating a Printing Profile | H2: Printing profile layout fields - [Reviewing documents with Case Dynamics] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Reviewing_documents_with_Case_Dynamics.htm): When reviewing documents in the Review Interface, you can link the active document to Case Dynamics objects, which store information related to your case. See Working with Case Dynamics objects. - Second paragraph: Object types include: - Headings: H1: Reviewing documents with Case Dynamics | H2: New review workflow with Case Dynamics | H2: Excerpts | H3: Excerpt considerations | H3: Excerpt permissions | H3: Creating a fact from an excerpt | H3: Appending an excerpt to a fact | H3: Displaying or hiding excerpt highlights | H2: Case Dynamics Document Layout | H2: Date suggestion | H2: Fact color options | H3: Editing fact color names | H3: Adding new fact colors - [Working with Case Dynamics objects] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Working_with_Case_Dynamics_objects.htm): You can use objects in Case Dynamics to store information related to your case. Object types include: - Second paragraph: The following tabs can also be used to store information related to your case: - Headings: H1: Working with Case Dynamics objects | H2: Importing Case Dynamics objects | H2: Viewing a Case Dynamics object | H3: Setting a default viewing mode | H2: Adding and editing a fact | H2: Adding and editing an issue | H2: Adding a Child | H3: Issues views | H2: Attaching supporting documents to an object | H2: Linking a document to an object | H2: Inline coding keyboard shortcuts and icons - [Working with Outlines] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Working_with_Outlines.htm): With the Outlines feature in Case Dynamics, you can easily build case narratives, create free-form outlines, and link to existing or create new Case Dynamics objects and documents. - Second paragraph: The Outlines tab includes a sample outline that gives a brief overview of how to use the feature and lets you test creating and linking objects to the outline. - Headings: H1: Working with Outlines | H2: Adding an outline | H2: Editing an outline | H3: Locked outlines | H3: Adding new objects to an outline | H3: Linking an outline to existing objects | H3: Linking a document from within an outline | H3: Viewing and editing object details | H2: View mode | H3: Linking documents to an outline | H3: Exporting an outline - [Working with Timeline Builder] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Dynamics/Working_with_the_Timeline_Builder.htm): You can use the Timeline Builder to visualize the chronology of facts. Being able to visualize the chronology of Facts adds value during the stages of a case life cycle. - Second paragraph: You can use timeline reports to: - Headings: H1: Working with the Timeline Builder | H2: Creating a Timeline Report | H2: Timeline Builder options | H3: Applying a color to a fact ### Case Metrics - [Case Metrics] (https://help.relativity.com/RelativityOne/Content/Relativity/Case_Metrics/Case_Metrics.htm): The Case Metrics application is a bundle of three reports and a dashboard. - Second paragraph: The Case Metrics application is a bundle of three reports and a dashboard: - Headings: H1: Case Metrics | H2: Special considerations for Case Metrics | H2: Installing Case Metrics | H3: Instance level installation and security configuration | H3: Workspace level installation and security configuration | H2: Reports | H3: Case Metrics profiles | H3: Reviewer Choices Report | H3: Reviewer Statistics Report | H3: Reviewer Overturn Report | H2: Reviewer Metrics dashboard | H2: Using the Scheduler | H3: Scheduled Report layout fields ### Case Workspace QRG - [Case workspace quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Case_Workspace_QRG/Case_workspace.htm): Use this guide to familiarize yourself with the case workspace. For more information on workspace navigation, see Tab navigation quick reference guide and Review interface quick reference guide. - Headings: H1: Case workspace quick reference guide ### Client domains - [Client Domains] (https://help.relativity.com/RelativityOne/Content/Relativity/Client_domains/Client_domains.htm): The client domains feature enables Relativity authorized partners to deliver more powerful managed service offerings for enterprise customers in a single instance by providing an easier way to securely isolate users, workspaces, groups, resource pools, and matters by client. - Second paragraph: Using client domains, system admins can empower a user group that is not part of the System Administrator group, client domain admins, to perform common administrative tasks within their own client domain while limiting their visibility into the Relativity environment as a whole. The client domain admins can customize the permission settings to various objects according to their preferences within their own domain, but cannot access any permissions outside of that. This resource isolation functionality grants your enterprise clients more administrative control over their own portions of the environment while preventing back-end visibility and unauthorized changes to your RelativityOne instance as a whole. - Headings: H1: Client domains | H2: Client domains software architecture | H2: Client domains cloud infrastructure | H2: Considerations before enabling client domains | H2: Enabling client domains on a client | H2: Client domain admins | H3: Client domain admin considerations | H3: Assigning a client domain admin | H2: Client domain limitations and considerations | H2: Adding or removing objects from a client domain | H2: Deleting a client domain ### Collect - [Collect] (https://help.relativity.com/RelativityOne/Content/Collect/Relativity_Collect.htm): A Relativity application for collecting your custodian - Second paragraph: Once ready, start adding custodians, data sources, and targets to Collect. Once connected, start the collect job and begin collecting data from custodians. - Headings: H1: Collect | H2: Data sources | H2: Commercial and Government support - [Collect Monitor] (https://help.relativity.com/RelativityOne/Content/Collect/Monitor.htm): Monitor pending, running, and completed collect jobs in the Monitor tab. The Monitor page only tracks collect jobs from the last 24-hour time range. - Headings: H1: Monitor - [Collect QRG] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Collect/Collect_QRG.htm): This document contains step by step guidance to setup Collect in your workspace to collect data from various cloud-based data sources. - Second paragraph: For the Collect quick reference in a .pdf file, see Relativty Collect Quick Start Guide. - Headings: H1: Collect quick reference guide | H2: Step 1: Installation | H2: Step 2: Obtaining data source configuration information | H2: Step 3: Setting up Relativity | H3: Setting up entity | H3: Setting up collection source | H3: Setting up collection matter | H2: Step 4: Collect using wizard | H3: Setting up a new Collection job | H3: Providing basic configuration information | H3: Selecting the data source | H3: Selecting the entities | H3: Applying criteria and filters | H3: Viewing the summary | H3: Viewing Collection details | H2: Step 5: Monitoring and Reporting | H3: Monitoring | H3: Reporting - [Collect reports] (https://help.relativity.com/RelativityOne/Content/Collect/Collect_reports.htm): Relativity Collect offers comprehensive reporting capabilities that you can use to view information about scouting results, collections, and targeted collections. You can set options to generate these reports based on matter and collection as well as other combinations. - Second paragraph: You can generate these reports in the collection console within a collection project. Click on the name of a report to download. Locate the Collection Summary and Collection Details report in the collection console. Locate the Results and Error report in the Data Sources table on the Collection Details page. - Headings: H1: Reports | H2: Running reports | H3: Collection Summary report | H3: Collection Details report | H3: Results report | H3: Errors report - [Custodian targets] (https://help.relativity.com/RelativityOne/Content/Collect/Custodian_targets.htm): In Collect, you manage custodians that have an associated data source. The custodian target is the combination of a custodian and data source. It is an endpoint from which Collect can connect to and collect from. For example, a custodian's Microsoft Outlook account is a custodian target. - Second paragraph: To collect from custodians, entities either have to already exist, be created, or be imported in Relativity. For more information on populating Relativity with entities, see Entity object. The custodian and their primary email address must also be associated to the data source. When the primary email address field for a custodian is present, Collect automatically generates the required targets for each data source while setting up a collection job. - Headings: H1: Custodian targets | H2: Custodians | H2: Fields | H2: Creating a custodian target | H3: Generating targets in the wizard | H2: Removing custodian targets - [Installing Collect] (https://help.relativity.com/RelativityOne/Content/Collect/Installing_Relativity_Collect.htm): You can easily install Relativity Collect or the Portal application in a workspace by using the functionality available through the Application Deployment System (ADS). This system provides you with the option to install Collect by selecting it from the list of existing applications in the Application Library tab, or by importing it from an external application file. You also use the ADS for installing the Portal application. See relevant Relativity Documentation.For more information, see Relativity applications on the Relativity Documentation site. - Second paragraph: To install Collect, install Collect from the Application Library tab and, if required, enable access for the data source. - Headings: H1: Installing Collect | H2: System requirements for Collect | H2: Installing Collect | H3: Installing Collect from the application library | H2: Permissions to run Collect | H2: Uninstalling the application - [Matters] (https://help.relativity.com/RelativityOne/Content/Collect/Matters.htm): You manage matters that can be associated with a collection. You can create each of these items on their respective tabs or you can create them when you add a new collection. - Second paragraph: You manage matters that are associated with a collection. You can create each of these items on their respective tabs, or you can create them when you add a new collection. - Headings: H1: Matters | H2: Creating a matter | H2: Matter Details layout fields | H2: Viewing or editing matter details - [Preservation to collection] (https://help.relativity.com/RelativityOne/Content/Collect/Preservation_to_collection.htm): Use the new Preservation in-place application for any new preservation holds. For more information, see Preservation in-place. - Second paragraph: When running a collection with Microsoft data sources, all available files, including preserved files, are collected. No extra steps need to be taken to collect preserved files as they are automatically included in the collection. - Headings: H1: Preservation to collection best practices | H3: Collect pre-requisites | H2: Creating a preservation hold | H2: Collecting preserved data - [Role-based access control] (https://help.relativity.com/RelativityOne/Content/Collect/Role-based_access_control.htm): Use role-based access control (RBAC) in Microsoft 365 Exchange Online to restrict your Azure Application Registration to access only specific mailboxes. This is important for workflows where your application needs mail access, and still want to limit that access to a defined set of custodians rather than all users in your organization. - Second paragraph: Azure application permissions are always-on by default. - Headings: H1: Role-based access control | H2: Azure application permissions | H2: Prerequisites | H2: Permission architecture | H2: Permissions assigned directly to the Azure App | H3: Permissions assigned with RBAC (Mailbox-Scoped) | H2: Configuration steps | H3: Connect to Exchange Online PowerShell | H3: Create a Service Principal in Exchange Online | H3: Create a Management scope for custodians | H3: Assign permissions to custodians | H3: Verify the configuration | H2: Troubleshooting | H3: Application can still access unscoped mailboxes | H3: Test-ServicePrincipalAuthorization shows no permissions | H3: PowerShell commands return an error or unexpected results | H3: macOS: zsh: command not found - [Status Summary] (https://help.relativity.com/RelativityOne/Content/Collect/Status_Summary.htm): In Collect, you manage multiple collect jobs and you need to track all of them. - Second paragraph: The job status dashboard to see the statuses of collection jobs. You can drill into each job from this dashboard. Able to look into the targets by custodian, data sources, or status to find out more about your collections. Focus on the collected components with this dashboard. - Headings: H1: Status Summary | H2: Job status | H2: Reviewing job statuses - [Target status] (https://help.relativity.com/RelativityOne/Content/Collect/Target_Status.htm): The Target Status tab is a dashboard to see the statuses of collections. You can drill into each target from this dashboard. Able to look into the targets by custodian, data sources, or status to find out more about your collections. Focus on the collected components with this dashboard. - Headings: H1: Target Status ### Collection - [Collect data in Staging Explorer] (https://help.relativity.com/RelativityOne/Content/Collect/Collection/Staging_explorer.htm): Before you begin collecting files from a custodian - Second paragraph: Use the sample screen below as a general guide for each data source type. - Headings: H1: Identifying Collection data in Staging Explorer - [Collection] (https://help.relativity.com/RelativityOne/Content/Collect/Collection/Collection.htm): Before you begin collecting files from a custodian - Second paragraph: Before you begin creating a collection, make sure to create a matter. For more information, see Matters. - Headings: H1: Collection | H2: Creating a collection | H2: Using the Collect wizard | H3: Collection Details | H3: Data source | H3: Custodians | H3: Non-custodial | H3: Collection Summary - [Collection details] (https://help.relativity.com/RelativityOne/Content/Collect/Collection/Collection_details.htm): You can view and edit collection details. You can also use the Collect console to start and stop collections and view reports. - Second paragraph: You can display the collection details by clicking the name of a collection on the Collections tab. Collection also displays these details immediately after you add a new collection. - Headings: H1: Viewing or editing Collection data | H2: Collection details | H2: Viewing collected data | H2: Collect console | H3: Preview | H3: Collection | H2: Delete collections - [Migrate Collect workspaces] (https://help.relativity.com/RelativityOne/Content/Collect/Collection/Migrate.htm): When you migrate a Collect workspace, using Archive, Restore, and Migrate (ARM) or Integration Points, Relativity moves workspace data but does not move data source credentials. - Second paragraph: To protect from compromising sensitive authentication information, Relativity does not support moving or copying Collect credentials from migration. - Headings: H1: Migrate Collect workspaces | H2: Credentials do not migrate | H3: Considerations ### Conditional Coding Rules - [Best practices for building coding rules] (https://help.relativity.com/RelativityOne/Content/Relativity/Conditional_Coding_Rules/Best_Practices_for_Coding_Rules.htm): Ensure that you don't have any conflicting conditions in your coding rule. For example, a conflict occurs if you have one condition that checks if Responsive is true, and a second condition that checks if Responsive is false. - Second paragraph: The software checks the conditions that you set to ensure that they are logical statements. However, it cannot confirm the validity of your business rules. You can avoid interruptions to your review process by validating the business logic used in the rule before it is enabled in an active workspace. The rule immediately begins executing during the review process once its Enabled. - Headings: H1: Best practices for building coding rules | H2: Check the logic for your conditions | H2: Use unique names for choices | H2: Field presence on layout | H2: Avoid changing field names | H2: Backslashes in field and choice names | H2: Wildcards in field and choice names - [Conditional Coding Rules Overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Conditional_Coding_Rules/Conditional_Coding_Rules_Overview.htm): Administrators use the Conditional Coding Rules application to set up rules that validate user input on a layout. If the data entered does not follow these rules, an error message prevents the information from being saved until corrected. - Second paragraph: Conditional Coding Rules only support validating layouts associated with the Document object or Relativity Dynamic Objects (RDOs). It does not support validation on any system objects. - Headings: H1: Conditional Coding Rules Overview - [Converting legacy Event Handler Express items] (https://help.relativity.com/RelativityOne/Content/Relativity/Conditional_Coding_Rules/Converting_legacy_Event_Handler_Express_items.htm): If any legacy Event Handler Express items are currently active in the workspace, a banner displays on the item list. - Second paragraph: Click Convert Rules to quickly migrate all existing Event Handler Express items to conditional coding rules. - Headings: H1: Converting legacy Event Handler Express items | H2: Convert all items in the workspace | H2: Convert individual items - [Creating Conditional Coding Rules] (https://help.relativity.com/RelativityOne/Content/Relativity/Conditional_Coding_Rules/Creating_Conditional_Coding_Rules.htm): Use the following steps to add information for a coding rule: - Second paragraph: The Conditional Coding Rule contains the following fields for basic information about the rule, the conditions for the rule, and the action message displayed when the rule is not fulfilled: - Headings: H1: Creating Conditional Coding Rules | H2: Fields for conditional coding rules | H2: Example Rule | H2: Supported conditions by field type | H2: Additional information about operators | H2: Using logic groups | H2: Editing coding rules | H2: Deleting coding rules - [Installing Conditional Coding Rules application] (https://help.relativity.com/RelativityOne/Content/Relativity/Conditional_Coding_Rules/Installing_Conditional_Coding_Rules_Application.htm): This application does not work with the Repository Workspace. - Second paragraph: See Permissions for more information. - Headings: H1: Installing Conditional Coding Rules application - [Permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Conditional_Coding_Rules/Permissions.htm) - Headings: H1: Permissions ### Content - [Included Topics] (https://help.relativity.com/RelativityOne/Content/IncludedTopics.htm) - Headings: H1: Included Topics - [RelativityOne e-Discovery User Documentation] (https://help.relativity.com/RelativityOne/Content/index.htm): Printable guides that cover features at a high-level - Second paragraph: Browse live trainings, webinars, and self-paced tutorials to help you get the most out of RelativityOne and the latest Relativity Server releases. - Headings: H1: Browse by topic | H2: What's new | H2: RelativityOne | H2: Data transfer | H2: Capabilities | H2: Relativity aiR | H2: Extend | H2: Supporting applications | H2: Quick reference guides | H2: Certification exam resources | H2: Additional resources | H2: Quick reference guides | H2: Workflow recipes | H2: White papers | H2: Learning | H2: Certifications | H2: Platform documentation - [Search] (https://help.relativity.com/RelativityOne/Content/Search.htm) - [Search Relativity Documentation] (https://help.relativity.com/RelativityOne/Content/CoveoSearch.htm) - Headings: H1: Search Results - [Sitemap] (https://help.relativity.com/RelativityOne/Content/Sitemap.htm) - Headings: H1: Sitemap ### Contracts - [Analysis] (https://help.relativity.com/RelativityOne/Content/Contracts/Analysis.htm): Learn about Contracts analysis sets, the analysis workflow, and Rerunning analysis. - Second paragraph: After you run an analysis set, you can review the results and rerun analysis as needed. For more information on analysis sets, see Analysis statuses and results. - Headings: H1: Analysis | H2: Model types in Contracts | H3: Prebuilt models | H3: Models requiring customization | H3: Contracts analysis profile options | H2: Analysis workflow | H2: Rerunning analysis sets | H3: Rerunning contracts classification | H3: Rerunning contracts segmentation | H3: Rerunning extraction - [Analysis statuses and results] (https://help.relativity.com/RelativityOne/Content/Contracts/Analysis_statuses_and_results.htm): There are various analysis states you - Second paragraph: To view analysis statuses and results, you must first create and run a Contracts analysis set. For instructions, see Analysis. - Headings: H1: Analysis statuses and results | H2: Management console | H2: Processing status | H3: Status | H3: Details | H2: Contracts analysis document list | H2: Supported file types | H3: How Contracts handles file types: | H3: Supported file types table | H2: Views | H3: Contracts Classification view | H3: Contracts Segmentation view | H3: Copy and edit a Contracts view | H3: Create a custom view | H3: Create a view that maintains grouping of sections to root agreements | H2: Export results - [Auto-group families based on shared field values] (https://help.relativity.com/RelativityOne/Content/Contracts/Auto-group_families_based_on_shared_field_values.htm): Learn to use the Contracts Unitization model to auto group documents into families based on shared field values. - Second paragraph: Lease documents — In a group of related lease documents, the parties and the property address are common threads. You can use Contracts unitization to auto-group those lease documents into a family after a first-pass review. - Headings: H1: Auto-group families based on shared field values | H2: Run unitization | H3: Fields auto-populated by Contracts - [Automate document assembly based on field values] (https://help.relativity.com/RelativityOne/Content/Contracts/Automate_document_assembly_based_on_field_values.htm): Generating new documents is often a manual part of the workflow following a contract review project. With Document Assembly, you can automate document creation at scale based on the structured data you - Second paragraph: For example, if your Word document has the phrase "Effective as of {{effective_date}}," you can later map this {{effective_date}} token to the Effective Date field in Relativity to fill in the actual date of the contract in place of the {{effective_date}} token in the Word document. - Headings: H1: Automate document assembly based on field values | H2: Assembly templates as building blocks | H2: Creating an assembly template | H2: Running document assembly | H3: Outputs generated by Contracts - [Auto-populate essential fields with generative AI] (https://help.relativity.com/RelativityOne/Content/Contracts/Auto-populate_essential_fields_with_generative_AI.htm): The essential fields model harnesses the power of large language models, or LLMs, to extract key data from contracts into Relativity fields. By leveraging generative AI, the essential fields model auto-populates key fields included in the Contracts application. - Second paragraph: The essential fields model uses a large language model (LLM) to extract key data from contracts into Relativity fields. When you run the essential fields model, it auto-populates fields included in the Contracts application, such as agreement type, parties, dates, and governing law. To help with transparency and defensibility, Contracts hyperlinks auto-populated fields to citations in the document and populates rationale fields where appropriate. - Headings: H1: Auto-populate essential fields with generative AI | H2: How the essential fields model works | H2: Deployment and processing geographies | H2: Language support in Contracts | H2: Job capacity and size limitations | H3: Size limits | H3: Volume limits | H2: Running the essential fields model | H3: Using a custom analysis profile | H2: Auto-populated fields - [Auto-populate field by training custom ML models] (https://help.relativity.com/RelativityOne/Content/Contracts/Auto-populate_fields_by_training_custom_ML_models.htm): Custom ML Extraction is a way to teach a machine learning model how to auto-populate fields by using previously coded examples as training data. - Second paragraph: Instead of using a regular expression, Custom ML Extraction uses examples that you create with the Contracts send-to-field feature in the viewer. You manually populate fields for many documents, and those examples serve as guidance for a new machine learning model that you build and train within the same workspace. - Headings: H1: Auto-populate fields by training custom ML models | H2: Create and train a custom model | H2: Run a custom model | H2: Frequently asked questions - [Auto-populate fields with regular expressions] (https://help.relativity.com/RelativityOne/Content/Contracts/Auto-populate_fields_with_regular_expressions.htm): Contracts uses extraction to pinpoint key data points within contracts and auto-populate fields of your choosing. Extraction works by taking a regular expression included with Contracts or custom regex and populating your desired fields based on the results of that regex. - Second paragraph: Contracts can auto-populate the following field types. How the field is populated depends on the field type group: - Headings: H1: Auto-populate fields with regular expressions | H2: Auto-populate Group 1 field types | H3: Run a regular expression model | H2: Auto-populate Group 2 field types | H3: Map results to choices - [Classify contract types] (https://help.relativity.com/RelativityOne/Content/Contracts/Classify_contract_types.htm): The contract classification model looks at the content of a document and predicts a contract type based on document content. - Second paragraph: The contract classification model looks at the content of a document and predicts a contract type. Think of a contract type as a label, or category, for the contract as a whole such as an Employment Agreement or Lease. Contracts is trained on 43 different contract types which are choices on the Contract Type field—a single choice field that is part of the Contracts application. When you run contract classification, Contracts auto-populates the Contract Type field with one of these choices. - Headings: H1: Classify contract types | H2: Running contract classification | H3: Using a custom analysis profile | H3: Auto-populated fields - [Classify section types] (https://help.relativity.com/RelativityOne/Content/Contracts/Classify_section_types.htm): The Section Classification model looks at the content of a section found via Segmentation and identifies its section type. - Second paragraph: After segmenting your contracts into sections, you can classify each section by type. A section type is a label or category—such as Confidentiality or Force Majeure—that identifies what a section covers. Contracts includes 318 predefined section types, which are choices on the Section Type field. When you run section classification, Contracts auto-populates the Section Type field with one of these choices. - Headings: H1: Classify section types | H2: Before you begin | H2: Running section classification | H3: Using a custom analysis profile | H3: Auto-populated fields - [Code contracts] (https://help.relativity.com/RelativityOne/Content/Contracts/Code_contracts.htm): Coding refers to capturing and storing metadata about a contract or its clauses. You can code a contract by clicking into fields, using Send to Field, or using data point suggestions. - Second paragraph: You can create custom fields with different format options to extract a wide range of data. For example, you can extract a lease's renewal date or determine the risk level of a change-in-control provision from an employment agreement. - Headings: H1: Code contracts | H2: Coding by clicking into fields | H2: Coding contracts via Send to Field | H3: Supported field types | H3: Send to Field from the text viewer | H3: Send to field from the image viewer | H3: Sending to long text fields multiple times | H2: Coding contracts with data point suggestions | H2: Coding at the section level - [Compare] (https://help.relativity.com/RelativityOne/Content/Contracts/Compare.htm): With Contracts Compare you can identify textual differences across sections or entire documents within your data set. You can export the analysis results as Excel or Word files that retain differences as highlights in Excel or Tracked Changes in Word. - Second paragraph: For step-by-step instructions, see Compare contracts or sections. - Headings: H1: Compare | H2: Compare requirements | H3: Incompatible comparison types | H3: Whole agreement comparison and Map Sections - [Compare contracts or sections] (https://help.relativity.com/RelativityOne/Content/Contracts/Compare_contracts_or_sections.htm): There are two methods of using Contracts Compare. You can compare Section to Section by comparing a section with other similar sections across similar contracts or different versions of the same draft. - Second paragraph: Before using Compare, you must select documents to compare. - Headings: H1: Compare contracts or sections | H2: Select documents to compare | H2: Export differences | H3: Export to Word | H3: Export to Excel | H3: Export to a saved search - [Contracts] (https://help.relativity.com/RelativityOne/Content/Contracts/Contracts.htm): Contracts is Relativity’s integrated solution for contract review. Contracts helps legal teams transform existing executed agreements into structured data to support downstream analysis for a variety of use cases ranging from corporate transactions to regulatory responses. - Second paragraph: With Contracts, you can: - Headings: H1: Contracts | H2: Requirements | H2: Contract review workflow | H2: Installing the Contracts application | H2: Considerations | H2: Permissions | H2: Job cost estimates - [Contracts OCR] (https://help.relativity.com/RelativityOne/Content/Contracts/Contracts_OCR.htm): To access the Contracts Image Viewer and functions such as search and navigation, you must run Contracts OCR. Contracts OCR (Optical Character Recognition) converts images of text, such as scanned and redacted documents, into machine-readable text characters. - Second paragraph: You must run Contracts OCR before you can use the Contracts Image Viewer and its search and navigation features. - Headings: H1: Contracts OCR | H2: Prerequisites | H2: Run Contracts OCR | H3: Fields auto-populated by Contracts | H2: Rerun Contracts OCR - [Contracts viewer] (https://help.relativity.com/RelativityOne/Content/Contracts/Contracts_Viewer.htm): The Contracts Viewer is a review interface designed specifically for contract review in RelativityOne. Use it to locate key clauses, data points, and contract metadata more efficiently than with the standard document viewer. - Second paragraph: You must run Contracts OCR on your documents before the Contracts Viewer is available. You do not need to run any other type of Contracts analysis. For more information, see run Contracts OCR. - Headings: H1: Contracts Viewer | H2: Definitions | H3: Definitions pane | H3: Definitions object list | H3: Adding definitions | H2: Sections | H3: Context menu for sections | H2: Document list navigation | H2: Related documents and their sections | H2: Data points | H2: Highlights minimap | H2: Contracts toolbar | H3: Search for text in a contract | H3: Auto-run toggle | H3: View documents | H3: Image viewer | H3: Adjust text size | H2: Context menu | H3: Send text to the section heading field | H3: Create sections | H3: Remove text from sections | H3: Create definitions | H3: Create bookmarks and links | H3: Navigate to exact lines between image and text | H3: Context menu search - [Create and edit regular expressions] (https://help.relativity.com/RelativityOne/Content/Contracts/Create_and_edit_regular_expressions.htm): You can create and save regular expressions in the Contracts Viewer, adjust your regular expressions, and see matching results in real time on the document you - Second paragraph: To create a regular expression in the Contracts Viewer: - Headings: H1: Create and edit regular expressions | H2: Create regular expressions in the Contracts Viewer | H2: Edit regular expressions in the Contracts Viewer | H2: Create regular expressions in Relativity | H2: Edit regular expressions in Relativity | H2: Highlight capture groups | H3: Common contract review scenarios for capture groups | H2: Regular expression building blocks | H3: Considerations | H3: How to use building blocks | H2: Filter regular expressions by saved searches | H3: Apply filters to regular expressions | H3: Example scenario | H2: Regular expressions included with Contracts | H2: Regular expression library | H2: Preview regular expression results | H3: Run preview | H2: Preview regular expression segmentation | H3: Run segmentation preview | H2: Segment documents using regular expressions - [Custom connectors] (https://help.relativity.com/RelativityOne/Content/Contracts/Custom_connectors.htm): You can integrate into the Contracts Analysis pipeline through custom connectors. - Second paragraph: Field mapping is done after saving the Model first and then going back to edit it. - Headings: H1: Custom connectors | H2: Configuring a custom connector | H3: Token mapping | H2: Custom connector developer documentation | H3: Authentication | H3: Request | H3: Response - [Extract definitions from contracts] (https://help.relativity.com/RelativityOne/Content/Contracts/Extract_definitions_from_contracts.htm): The Contracts Definition Extraction model will automatically extract each definition in a contract and store it in a Contracts Definition object. - Second paragraph: For example, if a contract contains the following definition: - Headings: H1: Extract definitions from contracts | H2: Contracts definition extraction | H3: Fields auto-populated by Contracts | H2: Regular expression definition extraction - [Manually group contract families] (https://help.relativity.com/RelativityOne/Content/Contracts/Manually_group_contract_families.htm): You can group amendments, addendums, exhibits, schedules, and other related documents to root agreements. - Second paragraph: Contracts assigns each analyzed document a unique identifier in the Contracts Related Documents field. To group related documents manually, you apply the same identifier (or a custom value) to every document that belongs to the same contract family. - Headings: H1: Manually group contract families | H2: Group related documents to a root agreement | H3: Create a custom order | H2: Group related documents to root agreements using Import/Export - [Run reports on regular expressions results] (https://help.relativity.com/RelativityOne/Content/Contracts/Run_reports_on_regular_expressions_results.htm): Instead of populating a specific field in your workspace, you can generate a report where Contracts creates new fields to store information regarding all regular expression results across a data set. - Second paragraph: When you generate a regular expression report, Contracts creates dedicated fields in your workspace to store the values, counts, location data, and error information for every match found. - Headings: H1: Run reports on regular expressions results | H2: Reporting fields Contracts creates and auto-populates - [Segment contracts into sections] (https://help.relativity.com/RelativityOne/Content/Contracts/Segment_contracts_into_sections.htm): The segmentation model breaks up a document into sections by looking for various signals for the start and end of a section. - Second paragraph: At a high level, the segmentation model relies on the outline format of a contract. For example, the structure of the section headings. If the contract has some structure in the form of discernible section headings, the segmentation model will use this information. - Headings: H1: Segment contracts into sections | H2: How segmentation works | H3: Segmentation and outline formats | H2: When to use segmentation | H3: Comparing differences between sections | H3: Auto populating yes/no fields to indicate section presence | H3: Filtering sections with regular expressions | H3: Auto-linking references to sections | H3: Coding sections at the section level | H2: Running segmentation | H3: Using a custom analysis profile | H3: Fields auto-populated by Contracts | H2: Segmentation using regular expressions | H3: Understanding parsing flags | H2: Improving segmentation results | H2: Using the Populate Section Text script - [Set up data points in the viewer] (https://help.relativity.com/RelativityOne/Content/Contracts/Set_up_data_points_in_the_viewer.htm): The Data Points pane found in the Contracts Viewer helps reviewers locate and navigate to key data in contracts. - Second paragraph: Data points visible in the Contracts Viewer come from the following sources: - Headings: H1: Setting up data points in the Viewer | H2: Why use data point filters | H2: Creating a data point filter - [Set up object coding mode] (https://help.relativity.com/RelativityOne/Content/Contracts/Set_up_object_coding_mode.htm): Learn how to set up object coding mode and allow information to be populated and reviewed at the family level in addition to the document level. - Second paragraph: Contracts are often amended over time, making it difficult to identify the latest source of truth across a family of documents. By creating a custom object for each contract family, you can consolidate key data from multiple related documents onto a single object. - Headings: H1: Set up object coding mode | H2: When to use object coding mode | H2: Viewer behavior in object coding mode | H2: Set up object coding mode ### Data Breach Response - [Blocklisting] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Blocklisting.htm): A blocklist is a list of banned or excluded PI Values. Using the blocklisting tool, you can identify potential PI tagged within the application and blocklist those that were falsely tagged - Second paragraph: If you are not automatically redirected, see Blocklisting. - Headings: H1: This page no longer exists. - [Data Analysis] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Incorporate_feedback.htm): The Incorporate Feedback pipeline is a combination of machine stages that make predictions, perform calculations, curate machine output, and generate reports. - Second paragraph: If you are not automatically redirected, see Data analysis. - Headings: H1: This page no longer exists. - [Data Breach Response] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Data_Breach_Response__Legacy_.htm): Data Breach Response is an AI-powered solution used to reduce the time, cost, and risk to produce an entity notification list. - Second paragraph: If you are not automatically redirected, see Data Breach Response (Legacy). - Headings: H1: This page no longer exists. - [DBR Generative AI Limited General Availability (LGA)] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Data_Breach_Response.htm): You will be automatically redirected. - Second paragraph: If you are not automatically redirected, see aiR for Data Breach Response. - Headings: H1: This page no longer exists. - [Detector QC] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Detector_QC.htm): Detector QC is the process by which humans adjust detectors for precision and recall before the review team begins their review. - Second paragraph: If you are not automatically redirected, see Detector QC. - Headings: H1: This page no longer exists. - [Document flags] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Errors_and_flags.htm): Data Breach Response uses document flags in a number of ways to denote information about a document. - Second paragraph: If you are not automatically redirected, see Document flags. - Headings: H1: This page no longer exists. - [Document ingestion] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Document_ingestion.htm): Learn about document ingestion. - Second paragraph: If you are not automatically redirected, see Document ingestion. - Headings: H1: This page no longer exists. - [Installation and configuration] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Installation_and_configuration.htm): 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. - Second paragraph: If you are not automatically redirected, see Installation and configuration. - Headings: H1: This page no longer exists. - [Non-spreadsheet review] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Unstructured_document_review.htm): You will be automatically redirected. - Second paragraph: If you are not automatically redirected, see Unstructured document review. - Headings: H1: This page no longer exists. - [Out of the box detectors] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Out_of_the_box_detectors.htm): Data Breach Response is pre-configured with PI detectors, also referred to as Out of the Box (OOTB) detectors. This is in addition to any custom detectors or classifiers added for a project. - Second paragraph: Before running Data Analysis you should review detectors and enable or disable any which make sense for your project. - Headings: H1: Out of the box detectors | H2: Enable and disable detectors | H2: PI level detectors - [Personal information detectors] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Personal_Information_detectors.htm): From the Project Settings page, you can view all detectors and tags, add new detectors and tags, and turn detector tags on and off. - Second paragraph: If you are not automatically redirected, see Personal Information detectors. - Headings: H1: This page no longer exists. - [PI and entity search] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/PI_and_Entity_Search.htm): With PI and Entity Search you can search documents with PI and Data Breach Entities that have been identified by Data Breach Response. - Second paragraph: If you are not automatically redirected, see PI and Entity Search. - Headings: H1: This page no longer exists. - [PI detect and data breach response workspace template] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/PI_Detect_and_Data_Breach_Response_workspace_template.htm): The PI Detect and Data Breach Response template has the PI Detect and Data Breach Response application pre installed and includes groups and processing fields specific to the application. - Second paragraph: The Data Breach Response template has the Data Breach Response application pre installed and includes groups and processing fields specific to the application. - Headings: H1: Data Breach Response Workspace Template | H2: Processing | H2: Data Breach Response tab visibility | H2: Workspace permissions | H3: DBR PID Template - Lead | H3: DBR PID Template - Annotator | H2: Change Log - [Project Dashboard] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Project_dashboard_.htm): Project Dashboard is available to project leads and provides immediate access to key information. You can use Project Dashboard to derive insights across your Data Breach Response project. - Second paragraph: If you are not automatically redirected, see Project dashboard. - Headings: H1: This page no longer exists. - [Project lead] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Project_lead.htm): Learn about the project lead role. - Second paragraph: Project leads have access to the following capabilities in Data Breach Response: - Headings: H1: Project lead - [Quality control] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Quality_control.htm): The Quality Control (QC) process is an optional step that occurs prior to review by the Project Lead. The goal of this step is to ensure that there is a minimization of documents with over and under predictions. - Second paragraph: If you are not automatically redirected, see Quality control. - Headings: H1: This page no longer exists. - [Review documents] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Review_documents.htm): Learn about common tasks and interfaces used by Reviewers when working with Data Breach Response. - Second paragraph: If you are not automatically redirected, see Review documents. - Headings: H1: This page no longer exists. - [Review results] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Review_results.htm): You will be automatically redirected. - Second paragraph: If you are not automatically redirected, see documentation for reviewing documents in Data Breach Response in Review documents. - Headings: H1: This page no longer exists. - [Spreadsheet QC tool] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Spreadsheet_QC_tool.htm): Spreadsheet QC allows a Project Lead to view and edit the headers of columns detected as PI, and view which search terms are being tagged by the machine in spreadsheets. - Second paragraph: If you are not automatically redirected, see Spreadsheet QC tool. - Headings: H1: This page no longer exists. - [Spreadsheet review] (https://help.relativity.com/RelativityOne/Content/Data_Breach_Response/Structured_document_review.htm): You will be automatically redirected. - Second paragraph: If you are not automatically redirected, see Structured document review. - Headings: H1: This page no longer exists. ### Data Grid - [Data Grid Text Migration application] (https://help.relativity.com/RelativityOne/Content/Relativity/Data_Grid/Data_Grid_Text_Migration_application.htm): The Data Grid Text Migration application is a Data Grid application you can use to migrate your long text fields from SQL to Data Grid. - Second paragraph: Enabling Data Grid allows you to store long text document fields, such as extracted text, outside of the SQL document table. Data Grid utilizes the Relativity file share to store long text document fields, which is the same location where native and image file data is stored. - Headings: H1: Data Grid Text Migration application | H2: Benefits of enabling Data Grid | H2: Special considerations | H3: Before running a text migration job | H3: During a text migration job | H3: Supported and unsupported functionality | H2: Installing the Data Grid Text Migration application | H2: Running text migration - [Text migration checklist] (https://help.relativity.com/RelativityOne/Content/Relativity/Data_Grid/Text_migration_checklist.htm): Before running a text migration, we recommend completing the following: - Second paragraph: Identify the workspaces you want to migrate. Be sure to review the special considerations for text migration as well as the list of supported and unsupported functionality for Data Grid. For more information, see Special considerations. - Headings: H1: Running text migration | H2: Identifying workspaces to migrate | H2: Identifying long text fields to migrate | H2: Creating a text migration job | H2: Running the Breakage Report | H2: Creating or activating a dtSearch index | H2: Resolving Breakage Report items | H3: Resolving index searches | H3: Resolving field-level searches | H3: Resolving computed fields | H2: Frequently asked questions ### Data migration - [Data migration] (https://help.relativity.com/RelativityOne/Content/Data_migration/Data_migration.htm): When it comes to going cloud with e-discovery, one of the first challenges that comes to mind is data migration. You probably have a lot of questions about data migration: What’s the process for moving your data from its current location to the cloud? How can you minimize downtime and cost? What tools can you use to migrate your data? How long will the process take? At Relativity, we’ve helped many law firms, service providers, and corporations through this process and have developed expertise that you can rely on to make the right data migration choice for your business. - Second paragraph: At Relativity, we’ve helped many law firms, service providers, and corporations through this process and have developed expertise that you can rely on to make the right data migration choice for your business. - Headings: H1: RelativityOne data migration | H2: Choosing the right data migration pathway | H3: I need to migrate my entire Relativity Server instance to RelativityOne | H2: Complicating factors that can extend your data migration timeline | H3: Staffing availability factors - [Migrating from non-Relativity platform to RelativityOne] (https://help.relativity.com/RelativityOne/Content/Data_migration/Non-Relativity_platform_data_migration.htm): This page guides you through steps and considerations when moving data from another e-Discovery platform to RelativityOne. It covers the following topics: - Second paragraph: The goal of this guide is to provide an overview of the different migration workflows and to assist with planning the migration of data to RelativityOne. - Headings: H1: Non-Relativity platform data migration | H2: RelativityOne Data Migration Program | H3: Relativity migration tools | H2: Other e-Discovery platform to RelativityOne migration | H3: Planning | H3: Pre-flight exercises | H3: Data migration & validation - [Migrating from Server to RelativityOne] (https://help.relativity.com/RelativityOne/Content/Data_migration/Server_to_RelativityOne_data_migration.htm): This page guides you through steps and considerations when moving data from Relativity Server to RelativityOne. It covers the following topics: - Second paragraph: The goal of this page is to provide you with the foundational information you’ll need to execute a successful data migration following Relativity standards. - Headings: H1: Server to RelativityOne data migration | H2: RelativityOne Data Migration Program | H2: Planning the data migration | H3: 1. Preparing Migration Team | H3: 2. Preparing Server environment | H3: 3. Planning the data migration | H3: 4. Other considerations | H2: Running a Data Migration Pilot | H2: Executing a Data Migration Plan | H2: Data migration resources - [Third-party data migration] (https://help.relativity.com/RelativityOne/Content/Data_migration/Third_party_data_migration.htm): There are many benefits to working with a RelativityOne partner who has earned the Data Migration Competency. - Second paragraph: First and foremost, these partners specialize in Relativity and can consult with you on customized solutions or, in some cases, even provide their own applications to accelerate your migration. Second, data migration requires a combination of expertise and availability. While a lot of our customers have technical proficiency and availability, for many this will be their first large RelativityOne data migration. Partners with the RelativityOne Data Migration Solution Competency bring knowledge and resources that can help accelerate your timeline and provide peace of mind. Finally, because migrations typically occur on nights and weekends, it is optimal for many organizations to rely on a partner for the necessary coverage. - Headings: H1: Third-party data migration partners | H2: RelativityOne Data Migration Competency criteria | H2: Roles and responsibilities when using a Relativity Data Migration Competency partner ### Data sources - [Anthropic (Claude) data source] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Claude.htm): This topic provides details on how to capture Anthropic's Claude Enterprise with Collect. - Second paragraph: Note the following considerations about this data source: - Headings: H1: Claude | H2: Considerations | H2: Prerequisites | H2: Collected metadata | H2: Creating the data source | H2: Settings fields | H2: Configuring the data source - [Bloomberg data source] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Bloomberg.htm): This topic provides details on how to capture Bloomberg chats and emails with Collect. - Second paragraph: Note the following consideration about this data source: - Headings: H1: Bloomberg chats and emails data source | H2: Consideration | H2: Creating the data source instance | H2: Settings fields | H2: Configuring the data source | H3: Bloomberg chat | H3: Bloomberg email - [Box] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Box.htm): This topic provides details on how to capture Box with Collect. - Second paragraph: The table lists the order to set up this data source for RelativityOne Collect. - Headings: H1: Box data source | H2: Task checklist | H2: Box application setup | H3: Creating an application with Box | H3: Authorizing an application | H2: Creating the data source instance in Collect | H2: Settings fields | H3: Data source details | H2: Configuring the data source in Collect - [Cellebrite data source] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Cellebrite.htm): This topic provides details on how you can remotely capture mobile device messages and attachments from Android or iOS devices using the Cellebrite data source within Collect. - Second paragraph: The steps below apply whether you are using Cellebrite Endpoint Inspector or Endpoint Mobile Now. Going forward in this topic, we will simply refer to them as Cellebrite. - Headings: H1: Cellebrite data source | H2: Considerations | H2: Prerequisites | H2: Task checklist | H3: Support resources | H2: Create the OAuth2 Client | H2: Set permissions in RelativityOne | H2: Connect Cellebrite to RelativityOne | H2: Generate API key for Cellebrite data source | H2: Create the data source in RelativityOne | H3: Settings fields | H2: Create entities in RelativityOne | H2: Create a Collect job in RelativityOne | H2: Mobile data collection results | H2: Troubleshooting - [ChatGPT Enterprise] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/ChatGPT.htm): This topic provides details on how to capture OpenAI's ChatGPT Enterprise with Collect. - Second paragraph: Note the following considerations about this data source: - Headings: H1: ChatGPT Enterprise data source | H2: Considerations | H2: Prerequisites | H2: Collected metadata | H2: Creating the data source | H2: Settings fields | H2: Configuring the data source - [Data sources] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Data_sources/Data_sources.htm): A preservation data source allows you to define where you want to put data on preservation hold. Set up workspace data sources before beginning preservations. - Second paragraph: Preservation data sources are stores of information from which you preserve data. These preservation sources have parameters that you can set during the creation of a preservation job. - Headings: H1: Preservation sources | H2: Creating a preservation data source | H2: Viewing preservation source details | H3: Data sources in wizard | H2: Understanding data services - [Data sources] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Data_sources.htm): A data source allows you to define where and how you pull data from a communication channel. A data source stores the configuration necessary to retrieve data from a communication channel, process that data, and ingest it into Collect. - Second paragraph: Set up workspace data sources before beginning collections. Data sources are stores of information from which you collect data. These data sources have parameters that you can set during the creation of a collection job. - Headings: H1: Data sources | H2: Creating a collect data source | H2: Data source types - [Google data sources] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Google.htm): Before you collect from a Google data source, Workspace or Gemini, you must complete the following tasks: - Second paragraph: Instance - Headings: H1: Google | H2: Google Workspace account setup | H3: Create a Google Cloud project | H3: Enable required APIs for the project | H3: Set up OAuth2 consent screen | H3: Add scopes | H3: Create credentials | H3: Set reauthentication policy | H2: Google Workspace user account setup | H3: Create admin role for Vault API | H3: Create admin role for the user accounts listing | H3: Create admin role for the groups listing | H3: Enable required privileges | H2: Restricting collections to the selected user accounts | H3: Create an organizational unit | H3: Add users to the organization unit | H3: Scope user privileges to the organizational unit | H2: Google data sources - [Google Gemini data source] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Gemini.htm): These limitations are inherent to Google’s current export behavior and not Collect-specific. - Second paragraph: Currently, in some cases, Google Vault exports may include placeholder links, or immersive chips, for these features. - Headings: H1: Google Gemini data source | H2: Advanced Gemini features | H2: Prerequisites | H2: Create the data source | H3: Settings fields | H2: Configure the data source in Collect - [Google Workspace] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Google_Workspace.htm): This topic provides details on how to capture Google Chats, Drive, Groups, and emails with Collect. Relativity collects Google Drive data using the Vault API. - Second paragraph: Consider the following items about this data source: - Headings: H1: Google Workspace data source | H2: Considerations | H3: Grouped collection | H2: Collection size | H2: Create the data source in Collect | H2: Configure the data source in Collect | H3: Google Groups | H3: Gmail | H3: Google Drive | H3: Google Chat | H2: Troubleshooting - [Google Workspace preservation source] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Data_sources/Google_Workspace.htm): This topic provides details on how to configure and capture Google Workspace Gmail, Drive, Chats, and Groups data with the Preservation in Place app. - Second paragraph: See these related topics: - Headings: H1: Google Workspace preservation source | H2: Considerations | H2: Requirements | H2: Setting up a Google data source | H3: Create a Google Cloud project | H3: Enable required APIs for the project | H3: Set up OAuth2 consent screen | H3: Create credentials | H2: Google Workspace user account setup | H3: Create admin role for Vault API | H3: Create admin role for the user accounts listing | H3: Create admin role for the groups listing | H3: Enable required privileges | H2: Create the Google Workspace data source | H3: Preservation data source fields | H2: Data source details - [iManage] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/iManage.htm): This topic provides details on how to capture data from iManage cloud instances with Collect. - Second paragraph: Your iManage account needs to have an iManage support account. To get an iManage support account, please refer to iManage's documentation. You must also connect it to Collect using the steps below. - Headings: H1: iManage data source | H2: Considerations | H2: Prerequisites | H2: Task checklist | H2: Setting up Relativity Collect in iManage | H3: Permissions | H3: Throttling | H2: Creating the data source in Collect | H2: Settings fields | H3: Data source details | H2: Configuring the data source in Collect - [Microsoft 365 Inactive mailboxes] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Microsoft_365_-_Inactive_mailboxes.htm): This topic provides details on how to capture Microsoft 365 Inactive mailboxes with Collect. - Second paragraph: Outlook mailboxes become inactive mailboxes when an account is deleted while under a preservation hold. When deleted, Microsoft does not throw the mailbox away. Microsoft keeps it in inactive state until the related preservation or retention hold is over. - Headings: H1: Microsoft 365 - Inactive mailboxes data source | H2: Considerations | H2: Collection size | H2: Task checklist | H2: Accessing Microsoft 365 tenants | H3: Registering the Collect application | H3: Obtaining a client secret | H3: Setting API permissions | H2: Adding a redirect URI | H2: Finding Azure credentials | H2: Limiting application registration access to accounts | H2: Revoking application access | H3: Revoking access via Azure Portal | H3: Revoking access via Powershell | H2: Creating the data source in Collect | H2: Settings fields | H3: Data source details | H2: Configuring the data source in Collect | H3: Data source criteria | H3: Criteria - [Microsoft 365 OneDrive] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Microsoft_365_-_OneDrive.htm): This topic provides details on how to capture Microsoft 365 OneDrive with Collect. - Second paragraph: Consider the following when using the OneDrive data source: - Headings: H1: Microsoft 365 - OneDrive data source | H2: Considerations | H2: Collection size | H2: Task checklist | H2: Accessing Microsoft 365 tenants | H3: Registering the Collect application | H3: Obtaining a client secret | H3: Setting API permissions | H2: Finding Azure credentials | H2: Revoking application access | H3: Revoking access via Azure Portal | H3: Revoking access via Powershell | H2: Creating the data source in Collect | H2: Settings fields | H3: Data source details | H2: Configuring the data source in Collect | H3: Data source criteria | H3: Collecting preserved files - [Microsoft 365 Outlook] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Microsoft_365_-_Outlook.htm): This topic provides details on how to capture Microsoft 365 Outlook mailbox, calendars, contacts, and archive mailboxes with Collect. - Second paragraph: Note the following considerations about Microsoft 365 Outlook data sources: - Headings: H1: Microsoft 365 - Outlook data source | H2: Considerations | H3: Mailbox types and required permissions | H3: Search and pre‑collection filtering | H3: Data source capabilities and limits | H3: Government cloud and environment considerations | H3: Network access and IP restrictions | H2: Collection size | H2: Task checklist | H2: Accessing Microsoft 365 tenants | H3: Registering the Collect application | H3: Obtaining a client secret | H3: Setting API permissions | H2: Finding Azure credentials | H2: Limiting application registration access to accounts | H2: Revoking application access | H3: Revoking access via Azure Portal | H3: Revoking access via Powershell | H2: Creating the data source in Collect | H2: Settings fields | H3: Data source details | H2: Configuring the data source in Collect | H3: Data source criteria | H3: Criteria | H2: Collecting preserved files | H2: Viewing collected data | H3: File names for Outlook email | H3: Files names on a preservation hold | H3: Email considerations | H2: Troubleshooting - [Microsoft 365 preservation source] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Data_sources/Microsoft_365.htm): You can preserve data in Microsoft 365, and Microsoft 365 Government, after completing the integration between RelativityOne and Microsoft 365. - Second paragraph: See these related topics: - Headings: H1: Microsoft 365 preservation source | H2: Licenses and access | H3: Microsoft 365 commercial | H3: Microsoft 365 Government | H3: Authentication and access model | H2: Considerations | H2: Setting up a Microsoft data source | H3: Automatic setup | H3: Manual setup | H2: Creating the Microsoft 365 preservation source | H3: Preservation data source fields | H3: Validate preservation hold credentials | H2: Data source details | H3: Data services - [Microsoft 365 Teams] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Microsoft_365_-_Teams.htm): This topic provides details on how to capture Microsoft 365 Teams with Collect. - Second paragraph: Note the following considerations about this data source: - Headings: H1: Microsoft 365 - Teams data source | H2: Considerations | H2: Grouped collection | H2: Collection size | H2: Task checklist | H2: Accessing Microsoft 365 tenants | H3: Licensing requirements | H3: Registering the Collect application | H3: Obtaining a client secret | H3: Setting API permissions | H2: Finding Azure credentials | H2: Revoking application access | H3: Revoking access via Azure Portal | H3: Revoking access via Powershell | H2: Creating the data source in Collect | H2: Settings fields | H3: Data source details | H2: Configuring the data source in Collect | H3: Data source criteria | H3: Modern attachments - [Microsoft preservation source automatic setup] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Data_sources/M365_Auto_setup.htm): Use an optional PowerShell script, O365PIPSetup.ps1, to automate Azure configuration steps needed to enable the Microsoft 365 Relativity preservation data source. - Second paragraph: The script handles several of the required Azure configuration tasks, including: - Headings: H1: Microsoft preservation source automatic setup | H2: PowerShell script | H2: Minimum supported access | H2: Prerequisites | H2: Run PowerShell script | H3: Validate the PowerShell script - [Microsoft preservation source manual setup] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Data_sources/M365_Manual_setup.htm): After completing the setup, you can set up the Microsoft 365 data source in Relativity. For more information, see Microsoft preservation source manual setup. - Second paragraph: See these related topics: - Headings: H1: Microsoft preservation source manual setup | H2: Minimum supported access | H2: Register the application | H2: Assign API permissions | H2: Generate certificate | H2: Assign application roles | H2: Run PowerShell script to create a Service Principal - [Microsoft SharePoint] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Microsoft_365_-_SharePoint.htm): This topic provides details on how to capture Microsoft 365 SharePoint with Collect. - Second paragraph: Note the following considerations about this data source: - Headings: H1: Microsoft 365 - SharePoint data source | H2: Considerations | H2: Collection size | H2: Task checklist | H2: Accessing Microsoft 365 tenants | H3: Registering the Collect application | H3: Obtaining a client secret | H3: Setting API permissions | H2: Finding Azure credentials | H2: Revoking application access | H3: Revoking access via Azure Portal | H3: Revoking access via Powershell | H2: Creating the data source in Collect | H3: Settings fields | H3: Data source details | H2: Configuring the data source in Collect | H3: Data source criteria | H3: Collecting preserved files | H2: Troubleshooting - [Refinitiv Eikon] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Refinitiv_Eikon.htm): This topic provides details on how to capture Refinitiv Eikon with Collect. - Second paragraph: Note the following consideration about this data source: - Headings: H1: Refinitiv Eikon data source | H2: Consideration | H2: Creating the data source | H2: Settings fields | H2: Configuring the data source - [Slack] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Slack.htm): This topic provides details on how to capture Slack data with Collect. - Second paragraph: Review the list of considerations before starting your collection: - Headings: H1: Slack data source | H2: Considerations | H3: Grouped collection | H2: Collection size | H2: Slack application setup | H2: Creating the data source in Collect | H2: Settings fields | H2: Configuring the data source in Collect | H3: Criteria | H3: Configuration considerations - [Slack preservation source] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Data_sources/Slack.htm): The Preserve in-place application connects to Slack. - Second paragraph: See these related topics: - Headings: H1: Slack preservation source | H2: Requirements | H2: Considerations | H2: Creating the Slack data source | H2: Data source details - [X1] (https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/X1.htm): This topic provides details on how to capture X1 data sources with Collect. - Second paragraph: X1 data sources require separate licensing, configuration, and training through a third party. For example, X1. For more information, see X1's licensing documentation. - Headings: H1: X1 data source | H2: Considerations | H2: Creating the data source | H2: Settings fields | H2: Configuring the data source | H3: Data source criteria ### Database Schema Updates - [Database schema updates table] (https://help.relativity.com/RelativityOne/Content/System_Guides/Database_Schema_Updates/Database_schema_updates_table.htm): (Topic Moved) - Headings: H1: Database schema updates ### dtSearch - [Alphabet list] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Alphabet_list.htm): Some of the characters in the alphabet file are not printable. Screenshots were used instead of the actual text. You cannot copy or paste the Spaces or Ignore characters since they are not printable. Instead, use the dtSearchDefaultAlphabetFile instance setting to update the dtSearch default alphabet file. - Second paragraph: Each sequence must start with a leading, or empty, space. Not having the leading space may produce errors. - Headings: H1: Alphabet list | H2: dtSearch Alphabet File | H2: Alphabet file sections | H3: Letters | H3: Hyphens | H3: Spaces | H3: Ignore | H3: End | H3: Non-ASCII characters | H3: Restricted characters | H3: Searching for a symbol or character | H3: Searching for emojis | H2: Reserved characters in the alphabet file - [dtSearch] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/dtSearch.htm): Relativity - Second paragraph: Relativity partitions a single index into smaller indexes, called sub-indexes, which multiple workers build simultaneously. This increases performance by spreading out the work over a configurable number of agents. When you perform a search, Relativity runs your query on the smaller indexes in parallel. The application then federates and returns your results. For more details, see the Ask The Expert Training content: Searching: Best Practices for dtSearch Builds. - Headings: H1: dtSearch - [dtSearch index] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/dtSearch_index.htm): You can build custom dtSearch indexes for a subset of documents or for certain document fields in a workspace. You must have the appropriate permissions to complete this task. See Workspace security. - Second paragraph: Before you begin, you need to create a saved search that includes the fields that you want to include in the index. You can then name the index based on the document search set used to create it. - Headings: H1: dtSearch index | H2: Accent-insensitive indexes | H2: Creating a dtSearch index | H3: Fields | H3: Advanced Settings | H3: Noise Words | H3: Alphabet | H2: dtSearch index page | H3: Index Status | H3: dtSearch Index Information | H3: Searchable Set - Current Indexable Fields | H3: Advanced Settings | H3: Noise Words | H3: Alphabet | H3: Temporary Index Details | H3: Current Index Details | H3: View Audit | H3: Temporary storage | H2: dtSearch console | H2: Re-index documents with incremental builds | H2: Case-insensitive indexes - [dtSearch queue admin] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/dtSearchQueueAdmin.htm): With the dtSearch queue admin page, you can monitor all dtSearch indexing jobs across an instance of Relativity that are not yet complete. This page only shows dtSearch jobs that you can access. - Second paragraph: You must have the DtSearch Queue Admin Tab Visibility permission to view. - Headings: H1: dtSearch queue admin | H2: Permissions | H2: Monitoring dtSearch indexing jobs - [Making the dtSearch noise word and alphabet list searchable] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Making_the_stop_word_and_alphabet_list_searchable.htm): Relativity ignores words that don - Second paragraph: Relativity references the default list of noise words each time you create a new index. System admins cannot edit noise words in keyword searches. The default noise word list consists of punctuation marks, single letters and numbers, and the following words: - Headings: H1: Making the dtSearch noise word list searchable | H2: Default noise word list | H2: Noise words in languages other than English - [Running a Dictionary search] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Running_a_Dictionary_search.htm): When you run a dtSearch, you can use Dictionary Search to query the index for a term and find the total occurrences and number of documents in which it occurs. - Second paragraph: A dictionary search returns only the first 2,000 items in the result set. If your search returns more than that, a message displays to indicate that only 2,000 items were returned. - Headings: H1: Running a dictionary search | H2: Running a dictionary search in the search panel | H2: Running a dictionary search in the search browser - [Running a dtSearch] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Running_a_dtSearch.htm): Use dtSearch to complete stemming, fuzzy, and proximity searches on the information included in your dtSearch index. - Second paragraph: Consider the following before running a dtSearch. - Headings: H1: Running a dtSearch | H2: Considerations and best practices | H2: Running a dtSearch in the search panel | H2: Running a dtSearch in the Search Browser | H2: Search string examples and expected results | H2: Searching for words longer than 32 characters - [Searching for symbols] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Searching_for_symbols.htm): This recipe demonstrates how to make symbols searchable in a dtSearch index and how to use regular expressions to search for certain symbols that are reserved as search operators, such as the % sign. - Second paragraph: There are two ways to make a character searchable, depending on whether the hexadecimal character code is less than 007F or greater than 0080. - Headings: H1: Searching for symbols and emojis | H2: Searching for symbols | H3: For hexadecimal characters greater than 0080 | H3: Commonly requested searchable symbols | H2: Searching for emojis | H3: Additional emojis - [Setting up CJK document workspaces in Relativity] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Setting_up_CJK_document_workspaces.htm): When working with documents that contain Asian character sets, specific settings will help expedite your setup time in Relativity. This information can help you build a clean workspace with more accurate fields to support your Asian language document sets. - Second paragraph: This document highlights items to be aware of as you work with workspaces that contain CJK character sets. - Headings: H1: Setting up CJK document workspaces in Relativity | H2: Requirements | H2: Import data with CJK characters | H2: Searching considerations | H3: dtSearch | H3: Index | H3: Word/Character search | H3: Keyword search | H2: Language considerations | H3: Mandarin considerations | H3: Chinese considerations | H2: Analytics considerations | H2: Tokenization considerations | H2: Technical workflow for tokenized character handling - [Using dtSearch syntax options] (https://help.relativity.com/RelativityOne/Content/Relativity/dtSearch/Using_dtSearch_syntax_options.htm): dtSearch includes special characters and other operators that you can use to define search criteria. The following table summarizes the syntax options available for queries run against a dtSearch index. - Second paragraph: For the list of the special characters recognized as spaces that cause word breaks, see Noise words and the alphabet file. - Headings: H1: Using dtSearch syntax options | H2: Auto-recognition | H3: Date recognition | H3: Email address recognition | H3: Credit card number recognition | H2: Boolean operators | H3: AND operator | H2: Built-in search words | H2: Connector words | H2: Exact phrase - double quotes | H3: AndAny operator | H3: OR operator | H3: NOT operator | H3: Operator precedence - no parentheses | H3: Operator precedence - with parentheses | H3: Workaround for expressions containing only AND or OR operators | H2: Exact phrase - no double quotes | H2: Fuzzy searching | H3: Using the fuzziness operator and fuzziness level option | H2: Noise words and the alphabet file | H3: Alphabet file | H3: Default noise word list | H3: Making a special character searchable | H2: Numerical patterns | H2: Phonic searching | H2: Stemming | H3: Using the stemming operator and enable stemming checkbox | H3: Using fuzzy searching and stemming together | H2: Wildcards | H2: W/N operator | H3: NOT W/N | H3: Complex expressions | H2: Words and phrases | H2: Other considerations ### Entity object - [Entity object] (https://help.relativity.com/RelativityOne/Content/Relativity/Entity_object/Entity_object.htm): The Entity object functions as the central location for people, companies, organizational groups, and their metadata. Relativity Legal Hold, Processing, and Analytics all leverage the Entity object. - Second paragraph: There are several ways to add a new entity: - Headings: H1: Entity object | H2: Creating and editing an entity | H2: Importing entities through Import/Export | H2: Deleting an entity | H2: Legal Hold entities | H3: Legal Hold layout | H3: Entity console | H3: Legal Hold entity load file | H2: Processing entities | H3: Processing layout | H3: Viewing or editing Processing entity details | H3: Processing entity load file | H2: Analytics entities | H3: Analytics layout | H3: Analytics entity load file | H3: Merge | H2: Case Dynamics entities | H3: Key entities | H3: Ensuring you do not create duplicate entities | H3: Default Case Dynamics layouts | H3: Case Dynamics entity load file | H3: Custom Case Dynamics layout requirements | H2: Collect entities | H3: Creating an entity | H3: Collect Entity Details fields | H3: Viewing or editing entity details ### Export Workflows - [Exporting data using Import/Export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/Exporting_workflows_overview.htm): You can use Import/Export to export the following: - Second paragraph: Also see General recommendations for structured data import and export jobs. - Headings: H1: Exporting data using Import/Export - [Folder load file export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/Folders_export.htm): You can use Import/Export to export folders and sub-folders out of RelativityOne. - Second paragraph: If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to Express Transfer overview for more information. With Express Transfer activated, you can run up to five concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs. - Headings: H1: Exporting a folder load file - [Production load file export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/Production_load_file_export.htm): You can use Import/Export to export a production set load file out of RelativityOne. - Second paragraph: If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to Express Transfer overview for more information. With Express Transfer activated, you can run up to five concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs. - Headings: H1: Exporting a production set load file | H2: Export Settings - [Production with Access DB load file export (MDB)] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/Production_with_Access_DB_load_file_export__MDB_.htm): The import and export workflows with Access DB (MDB) are designed for and are currently available for the Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your Account Representative. - Second paragraph: You can use Import/Export to export a production set with MDB load file out of RelativityOne. - Headings: H1: Exporting a production set with Access DB load file (MDB) - [RDO load file export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/RDO_file_export.htm): You can use Import/Export to export Relativity's dynamic objects (RDO) load file out of RelativityOne. - Second paragraph: If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to Express Transfer overview for more information. With Express Transfer activated, you can run up to five concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs. - [Saved search load file export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/Saved_Search_load_file_export.htm): You can use Import/Export to export a saved search load file out of RelativityOne. - Second paragraph: If you want to use Import/Export with Express Transfer, which is the recommended method for data transfer, refer to Express Transfer overview for more information. With Express Transfer activated, you can run up to five concurrent export jobs on a single client machine. For more information, see Concurrent and consecutive jobs. - Headings: H1: Exporting a saved search load file - [Saved Search or Folder with Access DB load file export (MDB)] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Export_Workflows/Saved_Search_or_Folder_with_Access_DB_load_file_export__MDB_.htm): The import and export workflows with Access DB (MDB) are designed for and are currently available for the Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your Account Representative. - Second paragraph: You can use Import/Export to export a saved search or a folder with MDB load file out of RelativityOne. - Headings: H1: Exporting a saved search or a folder with Access DB load file (MDB) ### Express Transfer - [Activating and deactivating Express Transfer] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Activate_and_Deactivate_Express_Transfer.htm): You have the ability to activate and deactivate Express Transfer for use with Import/Export. However, the recommended method for transferring data is with Express Transfer activated. - Second paragraph: To use Express Transfer, install the following in this order: - Headings: H1: Activating and deactivating Express Transfer | H2: Prerequisites | H2: Considerations when to use and not use Express Transfer with Import/Export | H2: Activating Express Transfer | H2: Deactivating Express Transfer | H2: Data transfer performance considerations - [Connectivity check] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Connectivity_Check.htm): Connectivity check ensures that the Express Transfer desktop application authenticates and successfully accesses the Internet, the necessary ports, and the Import/Export application to transfer data. This check executes automatically when you activate Express Transfer from the Import/Export application within RelativityOne. You can also manually perform a connectivity check anytime, even when there are active transfers. - Second paragraph: The following checks occur during the connectivity check process: - Headings: H1: Express Transfer Connectivity check | H2: Network Throughput Check - [Express Transfer job tracking and history] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Express_Transfer_Job_Tracking_and_History.htm): You can track the progress and history of jobs that were started with Express Transfer without logging into RelativityOne. - Second paragraph: To do so, open Express Transfer by double-clicking the shortcut on your desktop. - Headings: H1: Express Transfer Job tracking and history | H2: Prerequisites | H3: In Progress Tab | H3: History tab | H3: Filtering Express Transfer jobs | H3: Viewing and copying details of Express Transfer jobs - [Express Transfer overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Express_Transfer_Overview.htm): Express Transfer is an integral part of Import/Export workflows when activated for use with Import/Export. Using Import/Export with Express Transfer active is the recommended method of transferring data in Relativity. It can be used to transfer any data size, but it's designed especially for transferring large structured and unstructured data files greater than 20 GB. - Second paragraph: Using Import/Export with Express Transfer active helps reduce the time and effort it takes to transfer data in Relativity. For additional information on performance considerations when transferring data using desktop applications, see Data transfer performance considerations. - Headings: H1: Express Transfer overview | H2: Prerequisites | H2: Considerations when to use and not use Express Transfer with Import/Export - [Express Transfer preferences] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Express_Transfer_Preferences.htm): Use Express Transfer Preferences to modify the Check for Updates setting, limit bandwidth, exclude temporary Microsoft Office files from data import, configure proxy settings, and choose the Close button behavior.. - Second paragraph: You can configure whether or not you want the system to automatically check for new software versions of Express Transfer each time it opens and notify you with a message box. By default, this feature is enabled in Express Transfer Preferences. We recommend that you keep it enabled to ensure your system is running the latest software version containing the most recent software features available. If you choose to change this default setting, you will need to use the Check for Updates option in the Express Transfer system tray. See Manually checking for software updates for more information. - Headings: H1: Express Transfer Preferences | H2: Automatically checking for software updates | H2: Limit bandwidth | H2: Exclude temporary Microsoft Office files from data import | H2: Configuring proxy settings | H2: Minimize on close - [Express Transfer reporting jobs failed or completed with errors] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Express_Transfer_Reporting.htm): When using Express Transfer with Import/Export, if a job fails to finish or completes with errors, you can generate a report from Express Transfer Job Details. The report includes information such as the time stamp, file status, file name, error message, and file path. You also have a few options on how to handle the failed or errored jobs, such as retrying or skipping failed files. For more information about job tracking and history, see Express Transfer Job tracking and history. - Second paragraph: Available for Express Transfer version 2.21.1 and above. See Locating the Express Transfer version number if needed. - Headings: H1: Express Transfer reporting jobs failed or completed with errors - [Express Transfer system tray menu] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Express_Transfer_System_Tray_Menu.htm): Once the Express Transfer application is installed, its icon will be available in the system tray. Right-click on the icon to display an application menu with these options: - Headings: H1: Express Transfer system tray menu - [Installing Express Transfer] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Express_Transfer/Installing_Express_Transfer.htm): The Express Transfer application must be installed on your computer in order to use it with Import/Export workflows. The instructions below can be used for both Microsoft Windows and Apple macOS installations. You can configure preferences to automatically check for new software versions or you can check for them manually. We recommend keeping the default setting to enable the system to automatically check for new software versions to ensure you're using the latest software features available. - Second paragraph: For additional information on performance considerations when transferring data using desktop applications, see Data transfer performance considerations. - Headings: H1: Installing and updating Express Transfer desktop application | H2: Requirements | H3: System requirements | H3: Port access | H2: Prerequisites | H2: Installing Express Transfer | H2: Silent installation of Express Transfer | H2: Locating the Express Transfer version number | H2: Automatically checking for software updates | H2: Manually checking for software updates ### Fields - [Applying propagation to documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Fields/Applying_propagation_to_documents.htm): The propagation function can help enhance your document review workflow to save time spent coding documents. For example, you can tag a document as Responsive and have the value propagate to that document’s family members. - Second paragraph: To enable propagation, toggle Propagation on. - Headings: H1: Applying propagation to documents | H2: Propagating to documents in multiple groups - [Fields] (https://help.relativity.com/RelativityOne/Content/Relativity/Fields/Fields.htm): Fields store object information, document metadata, and coding choices within Relativity. You can use fields to display metadata on views and layouts. You can also use fields to create associations between different objects in Relativity. - Second paragraph: The following permissions are designated for use of fields: - Headings: H1: Fields | H2: Fields permissions | H2: System fields | H2: Creating and editing fields | H2: Fields | H3: Field information | H3: Field settings | H3: Advanced settings | H3: List and Dashboard Settings | H3: Choices | H2: Field types | H3: Fixed-length text | H3: Long text | H3: Date | H3: Whole number | H3: Decimal | H3: Currency | H3: Yes/No | H3: Single choice | H3: Multiple choice | H3: User | H3: File | H3: Single object | H3: Multiple object | H3: Fields and performance | H3: Linking Fields to Field Categories ### FINRA - [Hard Publish Delete] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/FINRA/Hard_Delete.htm): This topic provides details on performing a hard delete of processed files as part of the Post-publish Delete (file-level deletion from Review) workflow. Hard deletion provides full deletion of files within Processing when the corresponding document has been deleted out of the Documents tab. When you perform a hard delete, you remove all traces of the file from Relativity, which means the processing database no longer contains a reference to the deleted file or any of the associated metadata. - Second paragraph: Hard delete is currently available to select customers, and for these customers, hard delete is the only option when deleting from the Documents tab. For all other customers, we currently only support soft delete from Processing when you delete a file from the Documents tab. This means the file is only unpublished and not fully removed from the system. For details on soft delete, see Post-publish delete. - Headings: H1: Hard Delete | H2: Setting up for hard delete | H2: Deleting files from the review workspace | H2: Deleting files from the repository workspace | H2: Auditing delete actions | H3: Relativity Audit | H2: Invariant Log File Export | H3: Navigating to the delete log using the Staging Explorer | H3: Reviewing the CSV log | H2: Special considerations | H3: Structured Analytics | H3: Backups | H3: Cold Storage | H3: Containers (Processing) | H3: Data Grid | H3: Document Transformation | H3: dtSearch | H3: Other Jobs in the Workspace | H3: Error Deletions (Processing) | H3: Inventory (Processing) | H3: ROSE - [Metadata retention] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/FINRA/Metadata_Retention.htm): The Download & Replace functionality allows for the download of errored files to a user's local workstation and provides the ability to replace a discovered file with a different version (often repaired or decrypted). This feature can be found in the Mass action drop-down in the Files tab. - Second paragraph: For more information on Download / Replace, see Processing error resolution. - Headings: H1: Metadata Retention | H2: File Download and Replace | H2: Metadata retention | H2: Metadata retention behavior | H2: Multiple Replacement Operations | H2: Special Considerations ### FOIA - [FOIA Admin] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Admin.htm): The FOIA Admin portal provides tools for configuring agencies used in workflow steps, defining case number formats, setting working days, and managing email templates. - Second paragraph: You can customize the information your agency presents and collects at each step of the FOIA process. The Public Portal is specific to the agency accessing it. - Headings: H1: FOIA Admin (Advanced Access) | H2: Table of Contents | H2: Public Portal Settings | H3: Portal Status | H3: Public Agency Profile | H3: Submission Form | H2: Case Tracking Number | H2: Appeal Tracking Number | H2: Working Days | H2: Email Templates | H3: Adding a custom template | H2: Agency & Component - [FOIA Disclosure Center] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_DisclosureCenter.htm): The FOIA Disclosure Center provides information on previously released documents. - Headings: H1: FOIA Disclosure Center (Advanced Access) | H2: Table of Contents - [FOIA Reports] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Reports.htm): The FOIA Reports portal provides a list of reports that you can download as an Excel file. - Second paragraph: Click the Export icon next to the report you want to download. - Headings: H1: FOIA Reports (Advanced Access) | H2: Table of Contents - [Intake] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Intake.htm): During the Intake phase, the agency reviews the request and decides if it passes FOIA submission policies (perfection). - Second paragraph: Click the Intake step in the workflow panel to open its details. - Headings: H1: Intake (Advanced Access) | H2: Table of Contents | H2: Intake details for the coordinator | H2: Intake sub-steps | H3: Evaluation | H3: Save your entries | H3: Confirm Perfection - [Public Portal] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Portal.htm): The FOIA Portal provides public users with a secure access point to research released documents, submit records requests, and track the status of previous submissions. - Second paragraph: The Public Portal user interface. - Headings: H1: Public Portal (Advanced Access) | H2: Table of Contents - [RelativityOne FOIA] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA.htm): Advance Access (AA) is an opportunity to evaluate and work with Relativity features prior to the General Availability (GA) release. Relativity customers typically participate in AA programs on a feature-by-feature basis. The functionality described in this topic may not be available in all Relativity environments. This topic may not represent the functionality, appearance, or behavior of the GA release version of this feature. - Second paragraph: RelativityOne FOIA is currently in advanced access and is planned for general release in mid-2026. - Headings: H1: RelativityOne FOIA (Advanced Access) | H2: Table of Contents | H2: Public and agency portals | H3: Public Portal | H3: RelativityOne FOIA | H2: FOIA Workflow | H2: Permissions - [Request] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Request.htm): Submitting a FOIA records request. - Second paragraph: To submit a FOIA request, click the Create Request button in the navigation bar. - Headings: H1: Request (Advanced Access) | H2: Table of Contents | H2: Submitting a request | H2: Next steps - [Response] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Response.htm): The Response phase of a RelativityOne FOIA workflow consists of releasing a final decision on the FOIA request, and producing appropriate records. - Second paragraph: Click the Response step in the workflow panel to open its details. - Headings: H1: Response (Advanced Access) | H2: Table of Contents | H2: Response details for the coordinator | H2: Response sub-steps | H3: Interim Release | H3: Send Referral | H3: Provide Final Response | H3: Release to Reading Room - [Review] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Review.htm): The Review phase of a RelativityOne FOIA workflow involves assessing records for responsiveness, sensitivity, and compliance with applicable exemptions. - Second paragraph: Click the Review step in the workflow panel to open its details. - Headings: H1: Review (Advanced Access) | H2: Table of Contents | H2: Review details for the coordinator | H2: Review sub-steps | H3: Workspace(s) | H3: Request Equity Review | H3: Request Consultation - [Search] (https://help.relativity.com/RelativityOne/Content/Relativity/FOIA/FOIA_Search.htm): FOIA search consists of data collection, verifying the data, and linking or creating workspaces. - Second paragraph: Click the Search step in the workflow panel to open its details. - Headings: H1: Search (Advanced Access) | H2: Table of Contents | H2: Search details for the coordinator | H2: Search sub-step | H3: Task ### Getting Started - [Accessibility] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Accessibility.htm): Relativity is committed to accessibility in our platform and this page describes some of the accessibility options which are currently available. We will continue to expand our accessibility offerings in the future. - Second paragraph: If you are using your keyboard to navigate within Relativity, you can use this feature to skip the tabs in the Sidebar and jump to the options that are relevant to your current tab. This helps reduce keystrokes and make navigation faster. - Headings: H1: Accessibility | H2: Skip to Main Content | H2: Descriptive browser tabs - [Accessing the RelativityOne backend] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Accessing_the_RelativityOne_backend.htm): Welcome to RelativityOne. Before you can set up your Relativity instance for case workflow, you will want to configure your organization - Second paragraph: The following ports must be opened on user machines and/or firewalls for the GlobalProtect VPN to use when accessing file data in RelativityOne. - Headings: H1: Accessing the RelativityOne backend | H2: RelativityOne VPN ports | H2: Connecting to your VPN network | H2: Connecting to Utility Server | H2: Connecting to Direct SQL - [Customer-managed keys (CMK)] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Customer_managed_keys.htm): Customer-managed keys (CMK) - Second paragraph: Customer Managed Keys (CMK) provide you with control over the keys used to encrypt data at rest in RelativityOne. By allowing you to own and manage your own keys through third-party key management solutions, CMK enables you to maintain control over the encryption of persistent data within RelativityOne. - Headings: H1: Customer-managed keys (CMK) | H2: Adding a new CMK administrator | H2: Getting started with CMK | H2: Managing guest service principal keys | H3: Retrieving access tokens | H3: Get guest service principal id | H3: Creating guest service principal secret | H3: Retrieving the key list | H3: Revoking a key | H2: Rotating the key | H3: Rotating the key (manual): | H3: Rotating the key (programmatic): | H2: Pulling the key | H3: Pulling the key (manual) | H3: Pulling the key (programmatic) | H2: Restoring the key | H3: Restoring the key (manual) | H3: Restoring the key (programmatic) | H2: Security Logs API - [Deployment and processing geographies] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Deployment_and_Processing_Geos.htm): If you use Relativity's generative AI tools, your customer data may be processed outside the region where your RelativityOne instance is hosted. - Second paragraph: The tables that follow match the deployment locations of each application’s RelativityOne instance with the regions where their customer data is managed. - Headings: H1: Deployment and processing geographies | H2: For Azure OpenAI services | H3: Contracts | H3: aiR for Case Strategy | H3: aiR for Data Breach Response | H3: aiR for Privilege | H3: aiR for Review | H3: Transcripts | H2: For Azure AI Translator | H2: For Azure AI Speech, including Azure Speech-to-Text - [Downloading and installing a workspace template] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Importing_a_workspace_template.htm): This topic describes how to install a downloaded workspace template into your Relativity environment. - Second paragraph: Your RelativityOne instance may contain workspaces labeled "[DO NOT ACCESS]." You are not billed for these workspaces. However, do not access or delete them. In addition, we recommend updating any views to exclude them. - Headings: H1: Importing a workspace template - [Getting started in RelativityOne] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Getting_started_in_RelativityOne.htm): Welcome to RelativityOne. Before you start reviewing documents, Relativity requires you to perform a few key tasks to set up. If you - Second paragraph: See these related pages: - Headings: H1: Getting started in RelativityOne | H2: RelativityOne introductory training | H2: Technical readiness | H2: Setting up RelativityOne | H2: Transferring data to RelativityOne | H2: Navigating RelativityOne | H2: RelativityOne downtime windows | H2: RelativityOne repository workspace | H2: Solutions | H2: Other resources - [Navigation] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Navigation.htm): Relativity is a complex application with many screens and functions. This section describes the main core reviewer interface you use to review documents as well as some of the standard procedures you - Second paragraph: Relativity offers several ways to log in and it's possible to have two or more methods available to you. Your system admin will provide you with all the information you need to log on. Contact your system admin if you have additional questions. - Headings: H1: Navigation | H2: Logging in | H2: Tab navigation | H3: Sidebar | H2: All tabs menu | H2: Tab strip | H3: Parent and child tab display | H2: User options | H3: Changing the default Home tab | H3: My settings | H3: Dashboards | H2: Creating a dashboard | H2: Adding widgets to a dashboard | H2: Saving changes to a dashboard | H2: Deleting a dashboard | H2: Renaming a dashboard | H3: Using the search panel | H2: Resetting your password | H3: Resetting your password inside Relativity | H3: Resetting your password outside Relativity | H2: Favorites | H2: Quick nav - [Relativity conventions] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Relativity_conventions.htm): When you create or edit any object in Relativity, the following toolbars and fields are standard. - Second paragraph: When you create a new object in Relativity, the saving toolbar appears at the top of the screen. - Headings: H1: RelativityOne conventions | H2: Saving toolbar | H2: Editing toolbar | H2: Keywords and notes - [RelativityOne blank template] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne_Blank_Template.htm): For existing customers, new versions of our templates are available for download on the Community site. To receive a copy of an associated workflow document, go to the Community or contact Customer Support or your Customer Success Manager. For new tenants, templates are automatically deployed as part of new tenant provisioning process. If you customize your copy of a template, we do not overwrite that customized copy. We recommend deleting old versions of your templates when you are no longer using them. - Second paragraph: The RelativityOne Blank Template has the minimum amount of applications installed and does not contain any additional tabs, views, fields, layouts, choices, or objects. We recommend using this template when your workflows use custom Relativity applications or when you want to build workflows completely from scratch. - Headings: H1: RelativityOne Blank Template | H2: Change log - [RelativityOne downtime windows] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne_downtime_windows.htm): All time frames and dates are subject to change at Relativity - Second paragraph: We will include the most notable capabilities coming each month into one release email that is sent to our RelativityOne administrators, so you can prepare for the changes ahead of time. - Headings: H1: RelativityOne releases and downtime windows | H2: Planned release cadence | H2: RelativityOne data center regions | H2: Regular maintenance downtime windows | H2: Extended downtime windows | H3: Americas (US, Canada, Brazil) | H3: EMEA (India, United Arab Emirates) | H3: APAC (Hong Kong, Korea, Singapore) | H3: South Africa | H3: Europe (UK, West Europe, Germany, Switzerland) | H3: Australasia (Australia) | H3: Government (FedRAMP) | H2: Sandbox environment extended downtime windows | H2: Requesting to skip a downtime window | H3: Deadline for submitting requests to Relativity | H3: Considerations for skipping a regular maintenance downtime window | H3: Considerations for postponing an extended downtime window - [RelativityOne Release Process] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne_Release_Process.htm): Describes the different release mechanisms used in RelativityOne - Second paragraph: Our release process is designed around a balanced approach to ensuring both a reliable and stable platform as well as a rapid innovation pipeline. These processes follow SaaS industry best practices, and we have adopted technologies and release frameworks that ensure you can benefit from our latest innovation and improvements in a safe and timely manner. - Headings: H1: RelativityOne release process | H2: Key concepts | H2: General release categories | H2: Frequently asked questions | H3: General questions | H3: Phased rollouts - [RelativityOne technical overview] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne_technical_overview.htm): Welcome to RelativityOne. Before you can set up your Relativity instance for case workflow, you will want to configure your organization - Second paragraph: If you are an IT or network administrator that is charged with preparing your organization for RelativityOne, review the following system-level technical overview. - Headings: H1: RelativityOne technical overview | H2: RelativityOne government (FedRAMP) | H2: RelativityOne workstation configuration | H2: Instance Settings in RelativityOne | H2: RelativityOne network access | H3: Port considerations | H3: Firewall privacy considerations | H3: Content Delivery Network (CDN) considerations | H2: Accessing the RelativityOne backend | H2: RelativityOne system downtime windows | H2: RelativityOne resource scaling | H3: Automated RelativityOne resource scaling | H3: Informing support of a large incoming RelativityOne project | H2: Security | H3: Security white paper | H3: RelativityOne Security Center | H2: Hash value instance settings for billing metrics | H3: Client domains | H3: Customer lockbox | H2: Instance settings: | H3: Customer-managed keys (CMK) | H3: User authentication | H3: RelativityOne system access privileges | H2: Setting up a hybrid environment | H2: Personalization | H2: Regional date settings | H2: Deployment and processing geographies | H2: Custom application development in RelativityOne | H3: RelativityOne platform API | H2: Sandbox | H2: System logging in RelativityOne | H2: RelativityOne SMTP services (e-mail) - [RelativityOne Workspace Templates] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne_Workspace_Templates.htm): RelativityOne workspace templates put an entire workflow on rails using a prescriptive approach to tab setup, searches, and more. - Second paragraph: The following workspace templates are available for all RelativityOne customers. To receive the latest copy of any of these workspace templates, contact Support. - Headings: H1: RelativityOne Workspace Templates - [Sandbox environment] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne_Sandbox.htm): RelativityOne Sandbox refers to reusable RelativityOne environments that allow you to test SQL scripts, event handlers, API based applications, custom pages, and custom agents for both the current and Early Access (EA) release of Relativity. - Second paragraph: Sandbox environments typically do not include additional or add-on products. If you require a specific product in a sandbox environment, contact your Customer Success Manager to confirm availability. Please note that the aiR product suite cannot be installed in a sandbox environment. - Headings: H1: RelativityOne Sandbox - [Transitioning from Relativity Server to RelativityOne] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Server_to_RelativityOne.htm): Resources for transitioning from Relativity Server to RelativityOne - Second paragraph: Depending on your role, transitioning from Server to RelativityOne can be different. Use the following topics to learn more about the transition and the unique features only available in RelativityOne based on role: - Headings: H1: Transitioning from Relativity Server to RelativityOne | H2: Relativity Learning - [Transitioning from Relativity Server to RelativityOne for administrators] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Server_to_RelativityOne_for_Administrators.htm): Resources for Administrators who are transitioning from Relativity Server to RelativityOne - Second paragraph: Start here to learn how RelativityOne differs from Relativity Server from an administrator's perspective: - Headings: H1: Transitioning from Relativity Server to RelativityOne: Administrators | H2: Get started with RelativityOne | H2: Maintenance and upgrades | H2: Security | H2: Cost management | H2: Data transfer and data management | H2: Environment administration, instance settings, and tab visibility | H2: Applications, custom applications, and scripts | H2: What is still the same? - [Transitioning from Relativity Server to RelativityOne for users] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Server_to_RelativityOne_for_Users.htm): Resources for Reviewers and other end users who are transitioning from Relativity Server to RelativityOne - Second paragraph: Use the following resources to quickly get familiar with RelativityOne: - Headings: H1: Transitioning from Relativity Server to RelativityOne: Users | H2: General resources | H2: Expanded functionality | H2: Data ingestion | H2: Processing | H2: Review | H2: Production ### Hold and Collect Template - [RelativityOne Hold and Collect workspace template] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Hold_and_Collect_Template/RelativityOne_Hold_and_Collect_Workspace_template.htm): For existing customers, new versions of our templates are available for download on the Community site. To receive a copy of an associated workflow document, go to the Community or contact Customer Support or your Customer Success Manager. For new tenants, templates are automatically deployed as part of new tenant provisioning process. If you customize your copy of a template, we do not overwrite that customized copy. We recommend deleting old versions of your templates when you are no longer using them. - Second paragraph: The RelativityOne Hold and Collect Template has the Collect application and RelativityOne Legal Hold application both installed. Tabs have been pre-configured to expose the most common workflows. The prolonged use of the RelativityOne Legal Hold application in this template requires a separate license from Relativity. Send us an email to learn more. - Headings: H1: RelativityOne Hold and Collect workspace template | H2: Change log ### Imaging - [Application Field Codes] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Application_Field_Codes.htm): Application Field Codes is how Relativity refers to fields that Microsoft documents use to store document data. For example, [Date] is a field code in Microsoft that shows the date of document creation. Excel and PowerPoint refer to these fields as header and footer, Word refers to them as field codes, and Visio refers to them as fields. But for simplicity, Relativity refers to them as field codes, regardless of which Microsoft application document you’re viewing. - Second paragraph: When imaging Microsoft application documents in Relativity, field codes embedded within a document can contain incorrect or irrelevant information. The imaged field code functions as it should, but instead of using the original Date, for example, the field code captures the date the document was imaged within Relativity instead of the date the document was actually created. By creating Application Field Codes in Relativity, however, you can determine how various field codes appear on imaged documents. - Headings: H1: Application Field Codes | H2: Application Field Codes in Relativity | H2: Application Field Code formats | H2: Creating or editing an Application Field Code | H2: Fields | H2: Linking an Application Field Code to a native imaging profile - [Image upload] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Image_upload.htm): Use Relativity - Second paragraph: You can manage review and productions more efficiently by reducing the number of steps involved and avoiding some of the errors that were previously common when importing an image. - Headings: H1: Image upload | H2: Required security permissions | H2: Uploading an image | H2: Audits for image upload - [Imaging Documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging.htm): You can use imaging to convert a group of documents to images using imaging profiles and sets. You can fine-tune how your images generate by creating reusable profiles that use specific image settings. - Second paragraph: With imaging sets, you can image a group of documents by selecting a saved search and a specific imaging profile. Imaging sets also provide error-handling functionality you can use to view error messages and rerun imaging on specific documents or jobs. - Headings: H1: Imaging | H2: Security permissions for imaging | H2: Troubleshooting imaging | H2: Image on the fly | H2: Mass image - [Imaging errors] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_errors.htm): Errors are common when you run an imaging set, and you may encounter several of them when you go to check the progress of your set. - Second paragraph: To view document level imaging errors, go to the Imaging Document Error tab. The Imaging Document Error tab contains all imaging error history, including errors that are resolved. The error name provides succinct descriptions for easy understanding and resolution, these include: - Headings: H1: Imaging errors | H2: Viewing imaging errors | H3: Imaging Sets tab | H3: Documents tab | H3: Review Interface | H2: Imaging error scenarios | H2: Error email notification | H2: Retrying imaging errors | H2: Password Bank in imaging workflow - [Imaging history] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_history.htm): You can view the audit history when a job is run for an imaging set, mass image, or image-on-the-fly job by going to the History tab and filtering for Imaging in the name column. - Second paragraph: If you have the Data Grid for Audit application installed, the History tab is hidden. - Headings: H1: Imaging history - [Imaging jobs in the Worker Manager queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_jobs_in_the_Worker_Manager_queue.htm): The Imaging Queue displays all current imaging jobs running in your environment. You can view the queue if you have system admin rights to see the tab. - Second paragraph: The Imaging Queue view displays the following fields: - Headings: H1: Imaging jobs in the Processing and Imaging Queue - [Imaging native types] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_native_types.htm): On the Native Types tab, you see a list of file types that Relativity supports. Refer to this list when selecting file types that you want to restrict from imaging. The Relativity Desktop Client also supports the same list of file types. - Second paragraph: To locate specific file types, use the Show Filters option or create a new view to customize the content that appears on the tab. Default restricted file types propagate to new imaging profiles. You can edit the default value for the option that restricts the imaging of a file type and also edit the option that prevents native download for specific file types by clicking the Edit link. - Headings: H1: Imaging native types | H2: Editing a native type | H2: Generating a complete list of native types and their respective imaging engines - [Imaging profiles] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_profiles.htm): An imaging profile controls the settings used to image a group of documents. You can convert documents to black and white TIFF files or colored JPEG files. After you create a profile, you can use it in multiple imaging sets, update the profile settings, and set permissions on it. Imaging profiles, as well as any updates to the default profile, are included in workspace templates. - Second paragraph: For more information about editing permissions on imaging profiles, see Editing toolbar. - Headings: H1: Imaging profiles | H2: Creating and editing an imaging profile | H2: Fields | H2: Native file imaging profile validation | H3: Numerical Field Values | H3: Format Specific Requirements | H3: Field Dependencies | H2: Viewing imaging profile details | H3: Restricted native types | H3: Application field codes - [Imaging sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_sets.htm): An imaging set consists of an imaging profile and a saved search containing the documents you want to image. You run the imaging job from the imaging set console. In addition, on the Imaging Set Details page, you can view document-level error messages and rerun an imaging job if it failed. - Second paragraph: You need to provide reviewers in England with a group of 500 TIFFs so that they can redact and apply markups to them in the Viewer The Viewer is the area of the core reviewer interface in which document review takes place. It displays loaded forms of documents from the workspace and provides options for controlling the mode in which those documents display. Reviewers can apply markups, redactions, and persistent highlights to documents in the viewer. without having to first image them individually. You've already created an imaging profile specifically tailored to their needs. - Headings: H2: Using imaging sets - [Imaging Warnings] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Imaging_Warnings.htm): The Imaging Warnings object identifies possible cut-off content on imaged MSG or EML files and stores that information. - Second paragraph: Though MSG, P7M, P7S, ICS, VCF, EML, EMLX, and TNEF email file types are supported for imaging only EML and MSG file types are supported for imaging warnings. - Headings: H1: Imaging Warnings | H2: Special considerations | H2: Imaging Warnings tab | H3: Imaging Warning layout | H3: Warning Type pivot table | H2: All imaging warnings | H2: Core Reviewer layouts | H2: Re-imaging emails with tables - [Monitoring imaging status] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Monitoring_imaging_status.htm): In the imaging status section, you can monitor the progress of the imaging job by referring to the Status field after clicking the Refresh Page link on the console. - Second paragraph: The Imaging Status section provides the following fields: - Headings: H1: Monitoring imaging status - [Native Imaging - Dithering Algorithm Options] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Native_imaging_-_dithering_algorithm_options.htm): Relativity native imaging offers multiple dithering algorithms that you can apply towards imaging your documents. - Second paragraph: This topic provides details on the various dithering algorithms available within Relativity native imaging, as well as use cases for each algorithm, including the size and clarity of images you create. - Headings: H1: Native imaging - dithering algorithm options | H2: Dithering algorithm details | H3: Dithering results for text-rich documents | H3: Dithering results for image-rich documents - [QC Review] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/QC_Review.htm): QC Review is a feature that allows you to prevent users from viewing or editing images in an Imaging Set until a QC reviewer has a chance to review the images. The QC reviewer has access to the images, but the images are hidden from other groups until you release them. A permission setting in the Admin Operations section of the Workspace Details tab determines whether or not members of a particular group are able to view images held for QC Review. If a user without sufficient permissions views a document in an Imaging Set that is held for QC Review, the Image radio button is unavailable in the Viewer until you release the Imaging Set. - Second paragraph: Sometimes it's necessary to have one team of professionals perform a preliminary review of the images in a particular data set before releasing the images to a larger group of reviewers. With QC Review you can restrict access to a collection of images from one group, while another group performs quality checks. When the QC review process is complete, you can release the images to other groups to view. - Headings: H1: QC Review | H2: Hiding images for QC | H2: Releasing images | H3: QC Review fields | H3: Image QC Review Status - [Running an imaging set] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Running_an_imaging_set.htm): To run an imaging set, click Image Documents on the imaging set console. This kicks off the conversion of documents to images. - Second paragraph: Keep in mind the following special considerations: - Headings: H1: Running an imaging set | H2: Special considerations | H2: Unsupported file types | H2: Imaging Set console | H2: Imaging profile caching | H2: Password Bank - [Supported file types for imaging] (https://help.relativity.com/RelativityOne/Content/Relativity/Imaging/Supported_file_types_for_imaging.htm): Relativity Imaging supports many different file types. Learn about supported and unsupported file types for Native and Basic imaging. - Second paragraph: Container files | Database, spreadsheets | Document, text, word processors | Email, messaging, chat | Graphics, images | Other - Headings: H1: Supported file types for imaging ### Import Export - [Access DB (MDB) load file specifications] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Access_DB__MDB__Load_file_specifications.htm): Using load files, Relativity can load the following types of files: Metadata, extracted text, and native files, image and extracted text files, and processed data. - Second paragraph: In certain markets, the Import/Export supports data transfer of structured data defined in Access DB load files. The structure of the Access DB contains the following four tables. - Headings: H1: Access DB (MDB) load file specifications | H2: Export table | H2: Parties table | H3: Correspondence_Type_Persons_and_Organizations field logic | H2: Pages table | H2: Export_Extras table | H3: Example of values in Export_Extras table | H2: Export recommendations and considerations - [General recommendations] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/GeneralRecommendationsStructImportAndExportJobs.htm): The following are recommendations for importing and exporting load files. - Headings: H1: General recommendations for structured data import and export jobs | H2: Load file import recommendations | H2: Load file export recommendations - [IE load file specifications] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Export_Load_file_specifications.htm): Using load files, Relativity can load the following types of files: Metadata, extracted text, and native files, image and extracted text files, and processed data. - Second paragraph: Below are the load file specifications for Import/Export. - Headings: H1: Import/Export load file specifications | H2: Supported file types | H2: Metadata, extracted text, and native files | H3: Encoding | H3: Header row | H3: Fields | H3: Accepted date formats | H3: Delimiters | H3: Default delimiters | H3: ZIP archive with extracted text and natives | H2: Image and extracted text files | H3: Supported image file formats | H3: Load file format | H3: ZIP archive with images | H3: Importing extracted text during an image load | H2: Processed data | H2: Transcript file types supported | H2: Multiple references to the same native file - [Import Export overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Export_Overview.htm): Import/Export is the recommended method for bringing data into and sending data out of RelativityOne. With this tool, you can import raw data files, document load files, image load files, production files, RDO files. You can also export folders and subfolders, production sets, saved searches, and RDO files. - Second paragraph: Import/Export works with or without Express Transfer, however, activating Express Transfer is recommended. For more information, see Express Transfer overview and review the Considerations section when to use and not use Express Transfer. - Headings: H1: Import/Export overview | H2: Getting started with Import/Export | H2: Import and export workflows | H2: Import/Export transfer modes | H2: Considerations when to use and not use Express Transfer with Import/Export | H2: Supported file types | H2: Data upload size limitation | H2: Concurrent and consecutive jobs - [Import Export Queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Export_Queue.htm): Import/Export Queue lists the current Import/Export jobs in progress and their status throughout the RelativityOne instance. You can find the Import/Export Queue under the Queue Management tab. - Second paragraph: The Import/Export Queue provides job information for the following fields: - Headings: H1: Import/Export queue - [Installing Import/Export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Installing_Import_Export.htm): The Import/Export application will not be installed automatically in all your workspaces so you must do so manually in each one from the Relativity Application Library. - Second paragraph: Refer to the sections below for the necessary requirements for Import/Export. - Headings: H1: Installing Import/Export | H2: Requirements | H3: Workspace requirements | H3: Port Access | H2: Installing Import/Export - [Job tracking and history] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Job_Tracking_and_History.htm): The Import/Export Job page enables you to monitor the progress of jobs currently running, review previous jobs that were executed, and view other pertinent job details at the workspace level. - Second paragraph: To monitor jobs at the instance level, see Import/Export queue. - Headings: H1: Import/Export Job tracking and history | H2: Reviewing the Import/Export Job page | H2: Support for Mass Operations - [Permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Permissions.htm): Import/Export validates the user's permissions and checks if all required applications are installed in their workspace. If the user does not have permission to run a given workflow or if any application needed for that workflow is not installed, Import/Export grays out the workflow button and displays a warning message below it explaining why it's inactive. This validation process works separately for each workflow. For example, if a user does not have permission to run a Processing job, they may still be able to import load file data but will not be able to process it. - Second paragraph: All permissions are set in Workspace security. - Headings: H1: Permissions | H2: Additional required permissions for document import | H3: Mapped field permissions | H3: Required system field permissions for Document object import - [Scheduling Import/Export jobs with Automated Workflows] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Export_Jobs_Scheduled_with_Automated_Workflows.htm): You can use Automated Workflows to run Import/Export jobs on a schedule when your job’s data source or export location is set to Staging. - Second paragraph: On this page, you will learn how to: - Headings: H1: Scheduling Import/Export jobs with Automated Workflows | H2: Before you begin | H2: Limitations | H2: Scheduling a job | H2: Viewing scheduler-related jobs in Import/Export ### Import Workflows - [Access DB load file import (MDB)] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Access_DB_load_file_import__MDB_.htm): The import and export workflows with Access DB (MDB) are designed for and are currently available for the Asia-Pacific region. For information on the possibility of enabling this flow in your instance, please contact your Account Representative. - Second paragraph: You can use Import/Export to import document load files, .mdb .and mdbacc, into RelativityOne that contain document metadata, native files, or extracted text. You're also able to use saved job profiles to expedite the configuration process. - Headings: H1: Importing an Access DB load file (MDB) | H2: Load File Field Mappings options - [Document load file import] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Document_load_file_import.htm): You can use Import/Export to import document load files, .dat, .csv, and .txt, into RelativityOne that contain document metadata, native files, or extracted text. You're also able to use saved job profiles to expedite the configuration process. - Second paragraph: If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer, refer to Express Transfer overview for more information. - Headings: H1: Importing a document load file | H2: Load File Field Mappings options | H2: Pre-check Load File optional step - [Image load file import] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Image_load_file_import.htm): You can use Import/Export to import image and PDF load files that are Opticon-formatted (.opt) page-level files. For more information on Opticon load file, see Load file format. - Second paragraph: Before you begin, consider the following: - Headings: H1: Importing an image load file | H2: Considerations | H2: References | H2: Before you begin | H2: Importing image load file workflow | H3: Select data to Import options | H3: Choose Load File and Location options | H3: Import Settings options | H3: Pre-check Load File optional step - [Importing data using Import/Export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Import_Workflow_Overview.htm): You can use Import/Export to import unprocessed raw native files, document load files, image load files, production load files, and Relativity Dynamic Objects. Refer to Import/Export load file specifications and Data upload size limitation for more information regarding load files. Also see General recommendations for structured data import and export jobs. - Second paragraph: After documents are imported using Import/Export, you can automate creating a dtSearch index or run a search terms report with those documents using Automated Workflows. To learn more, visit Automated Workflows. - Headings: H1: Importing data using Import/Export | H2: Structured data import from Staging | H2: Pre-check Load File | H3: Document and RDO load file import | H3: Image and Production load file import | H3: Working with Pre-check Load File results - [Importing transcript MDB data for Processing via Import/Export] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Transcript_MDB_data_import.htm): Import/Export uploads raw (unprocessed) data to the ProcessingSource folder and triggers the Processing application. The ProcessingSource folder is included in your Staging threshold. To avoid additional storage costs, you may want to delete the uploaded raw (unprocessed) data from this folder once it is no longer needed. - Second paragraph: You can use Import/Export to import transcript MDB data with the linked audio/video files into RelativityOne. This will automatically trigger a Processing job to extract metadata from the selected transcript MDB file, create documents and link them with audio/video content included in the dataset, in one operation. Once the transcript data is successfully imported into your workspace, you can use the Relativity Transcripts application to review the content. - Headings: H1: Importing transcript MDB data for Processing via Import/Export | H2: Before you begin | H2: Importing transcript MDB data - [Production load file import] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Production_load_file_import.htm): You can use Import/Export to import external productions, including single and multiple PDF files, into RelativityOne with Import/Export. This is useful after a production goes out the door in the event a case team needs access to documents as they were in the production and needs them available for searching. - Second paragraph: If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer, refer to Express Transfer overview for more information. - Headings: H1: Importing a production load file - [RDO data import] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/RDO_data_import.htm): You can import Relativity's dynamic objects (RDO) for use in Relativity applications. The workflow for RDO data import follows the same general guidelines as those for document load file imports. - Second paragraph: If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer, refer to Express Transfer overview for more information. - Headings: H1: Importing an RDO load file | H2: Load File Field Mappings options - [Unprocessed data import for Processing] (https://help.relativity.com/RelativityOne/Content/Relativity/Import_Export/Import_Workflows/Unprocessed_data_import_for_Processing.htm): You can use Import/Export to import native, unprocessed/unstructured files, including Slack data, into RelativityOne that require processing and it will automatically trigger a Processing job in one operation. - Second paragraph: If you want to use Import/Export with Express Transfer active, which is the recommended workflow for data transfer, refer to Express Transfer overview for more information. - Headings: H1: Importing raw unprocessed data for Processing via Import/Export | H2: Create Processing Job | H2: Importing Slack short message data for Processing via Import/Export ### Integration Points - [Exporting data through Integration Points] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Exporting_data_through_Integration_Points.htm): Integration Points provides you with the ability to export data directly from your workspace through the same functionality that the Relativity Desktop Client (RDC) provides for exporting the document object. This includes exporting saved searches, case folders, and productions directly from your workspace, and scheduling future or recurrent export jobs. - Second paragraph: Integration Points provides you with the ability to export data directly from your workspace. This includes exporting saved searches, case folders, and productions directly from your workspace, and scheduling future or recurrent export jobs. - Headings: H1: Exporting data through Integration Points | H2: Exporting a folder and subfolders to a load file | H2: Stopping (disabling) an Integration Point from promoting data | H2: Automatically stopping a scheduled job that repeatedly fails - [Importing data through Integration Points] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Importing_data_through_Integration_Points.htm): Integration Points provides you with the ability to import data directly into your workspace through the same functionality that the Relativity Desktop Client (RDC) provides for importing the document object. - Second paragraph: Integration Points provides you with the ability to import a .csv file, LDAP, or load file directly into your workspace, and schedule future or recurrent import jobs. - Headings: H1: Importing data through Integration Points | H2: Considerations | H2: Creating an import Integration Point | H3: Import sources | H2: Importing a .csv file | H3: Setup | H3: Connect to source | H3: Map fields | H2: Importing LDAP | H3: Setup | H3: Connect to source | H3: Map fields | H2: Importing a document load file | H3: Setup | H3: Connect to source | H3: Map fields | H2: Importing an image load file | H3: Setup | H3: Source information | H2: Importing a production load file | H3: Setup | H3: Source information | H2: Importing from Microsoft Entra ID | H3: Setup | H3: Connect to source | H3: Map fields | H3: Reporting on Microsoft Entra ID imports | H2: Manually running the import job | H2: Downloading the error file | H2: Disabling a scheduled Integration Point job | H2: Scheduler date format considerations | H2: Automatically stopping a scheduled job that repeatedly fails - [Installing Integration Points] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Installing_Integration_Points.htm): To successfully use Relativity Integration Points, you need to install the Integration Points application to one or more workspace. - Second paragraph: To successfully use Integration Points, you need to install the Integration Points application to at least one workspace. - Headings: H1: Installing Integration Points | H2: Installing Integration Points - [Integration Points profiles] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Integration_Points_profiles.htm): You have the option of creating and saving profiles, which you can use to run future import or export jobs through Integration Points. You can make your profiles specific to each data source provider so that you can then reuse those settings and avoid having to remap fields multiple times. - Second paragraph: You have the option of creating and saving Integration Points profiles, which can be used to run future common import or export jobs through Integration Points without having to recreate them each time. The profiles can be specific to each data source so that you can reuse the settings and avoid having to remap fields multiple times. - Headings: H1: Integration Points profiles | H2: Creating Integration Point profiles | H2: Copying Integration Point profiles | H3: Configuring an Integration Point Profile for copying | H3: For Setup | H3: For Connect to Source - [Microsoft Entra ID provider] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Azure_AD_provider.htm): Relativity can import Entity (Employee/Custodian) data from Microsoft Azure Active Directory through Relativity Integration Points (RIP). - Second paragraph: To create your application ID and secret, you must have Application Administrator privileges to log into your Azure Portal and register an app. - Headings: H1: Microsoft Entra ID provider | H2: Registering an Azure application and credentials | H2: Finding Azure credentials | H2: Removing application access - [Monitoring job history and errors] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Monitoring_job_history_and_errors.htm): After you create an integration point and initiate the import process, you can monitor the job status on the Job History tab. This tab lists an entry for each integration point job, and also provides you with the ability to view additional details for a specific job. - Second paragraph: After you create an integration point and initiate the import process, you can monitor the job status on the Job History tab and resolve errors on the Job History Errors tab. - Headings: H1: Monitoring job history and errors | H2: Job History | H3: Viewing job history details | H2: Job History Errors | H3: Item-level errors versus job-level errors | H2: Troubleshooting job history errors - [Relativity Integration Points] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Relativity_Integration_Points.htm): Relativity Integration Points offers a solution to configure integrations from third party systems to Relativity objects. - Second paragraph: Integration Points offers a solution to configure integrations from third party systems to Relativity objects and between Relativity workspaces. For more information, see Transferring (promoting) data between workspaces. - Headings: H1: Integration Points | H2: Integration Points scenarios - [Security permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Permissions.htm): The following tables provide detailed breakdowns of the security permissions required to use Integration Points. - Second paragraph: To submit a job for a non-Relativity source provider, such as FTP, LDAP, or load file, and display console errors for that job, you need the following permissions: - Headings: H1: Security permissions | H2: Submit a job for a non-Relativity source provider | H2: Submit a job with Relativity as the source provider and display console errors for that job | H2: Create an integration point for a non-Relativity source provider | H2: Create an integration point with Relativity as the source provider | H2: View an integration point with any source provider | H2: Create and edit an integration point with any source provider | H2: Create an integration point with a Relativity source provider | H2: Create an integration point with any source provider from an integration point profile | H2: View any integration point profile | H2: Create and edit an integration points profile with any source provider | H2: Create and edit an integration points profile with a Relativity source provider - [Transferring (promoting) data between workspaces] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Promoting_data_between_workspaces_through_Integration_Points.htm): Once you - Second paragraph: You can use Integration Points to transfer, or promote, data from one Relativity workspace to another Relativity workspace. This is as a one-way sync process from a source workspace to a destination workspace. This is not a back and forth syncing process between them. - Headings: H1: Transferring (promoting) data between workspaces | H2: Considerations | H2: Exporting to a Relativity workspace | H3: Considerations | H3: Setup | H3: Connect to Source | H3: Map Fields | H2: Mapping saved searches | H2: Working with transferred documents | H3: Reusing coding decisions | H2: Calculating integration point job statistics on-demand - [Viewing destination workspaces] (https://help.relativity.com/RelativityOne/Content/Relativity/Integration_Points/Viewing_destination_workspaces.htm): You can go to the Destination Workspace tab to view all of the workspaces that are designated as destinations for documents that you push through integration points. - Second paragraph: You can go to the Destination Workspace tab to view all of the workspaces that are designated as destinations for documents that you push through integration points. - Headings: H1: Viewing destination workspaces ### Investigations Template - [RelativityOne Investigations Workspace template] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Investigations_Template/RelativityOne_Investigations_workspace_template.htm): Investigations in RelativityOne involve targeted discovery into a set of documents to identify whether or not a specific behavior occurred. Built for RelativityOne, the RelativityOne Investigations Template simplifies the process of investigations by streamlining both the setup and the investigation workflows. - Second paragraph: The Investigations Workspace Template is meant to facilitate the searching and review of documents for an investigation — all in one workspace. For an Early Case Assessment workflow (culling documents prior to review in a separate case), use the separate RelativityOne Early Case Assessment Workspace template. - Headings: H1: RelativityOne Investigations Workspace template | H2: Documents | H2: Processing | H2: Search Setup | H2: Workspace Setup | H2: Admin | H2: Change Log ### Keyboard shortcuts - [Creating keyboard shortcuts] (https://help.relativity.com/RelativityOne/Content/Relativity/Keyboard_shortcuts/Creating_keyboard_shortcuts.htm): Any user with permissions to create or edit a field or choice can create keyboard shortcuts. You can only configure shortcuts for document fields and their associated choices. - Second paragraph: The action that a shortcut triggers depends on the layout display type selected for the fields and choices. See Document field type shortcuts and Document choice shortcuts. - Headings: H1: Creating keyboard shortcuts - [Keyboard Shortcuts] (https://help.relativity.com/RelativityOne/Content/Relativity/Keyboard_shortcuts/Keyboard_shortcuts.htm): With keyboard shortcuts you can edit and navigate in the Core Reviewer Interface. Using keyboard shortcuts, you can change viewer modes, populate choices, save edits, cancel edits, and move between and within documents. Keyboard shortcuts are enabled by default. - Second paragraph: Users with permissions to edit fields and choices can create additional shortcuts using the Keyboard Shortcuts property on the choice. - Headings: H1: Keyboard shortcuts | H2: Keyboard shortcuts legend | H2: Special considerations for keyboard shortcuts | H2: Document field type shortcuts | H2: Document choice shortcuts ### Layouts - [Adding and editing an object list] (https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Adding_and_editing_an_object_list.htm): You can add a list of child objects to layouts for the parent object type, and you can add associative object lists to objects related by a single or multiple object field. Use the Layout Options console to add these lists to layouts when child or associative objects exist for the current object type. - Second paragraph: Child and associative objects frequently refer to user-created objects in Relativity. These Dynamic Objects are securable, non-document objects that you can add to a workspace. You can link Dynamic Objects to documents and to other object types to create powerful custom applications within your workspace. - Headings: H1: Adding and editing an object list | H2: Adding and editing an object list | H3: Child and associative object lists | H3: Object list properties - [Adding fields and text] (https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Adding_fields_and_text.htm): Use the fields in the Layout Options console to create your layout. Search for available fields in the search box. Relativity automatically places wild cards at the beginning and end of the entered characters. The list of available fields is dependent on the layout Object Type and any fields created with the same Object Type. - Second paragraph: The Layout Options contain the following fields: - Headings: H1: Adding fields and text | H2: Layout options | H2: Adding fields to a category | H2: Removing fields from a category | H2: Making a field one or two column | H2: Making a field read-only | H2: Other fields considerations | H2: Field properties - [Copy from Previous] (https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Copy_from_Previous.htm): You can design a layout to include the Copy from Previous toolbar. This enhances review by providing the ability to copy coding values from one document to another within a review session. - Second paragraph: After you've coded and saved a document as part of the review process, an icon displays in the layout next to any fields that are eligible for Copy from Previous. A value for each eligible field has to be selected and then saved before you can use Copy from Previous. If there is a field where no value was selected, then it is not eligible for Copy from Previous and the icon does not display to denote this. - Headings: H1: Copy from Previous | H2: Adding the Copy from Previous toolbar | H2: Using Copy from Previous - [Creating a new category] (https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Creating_a_new_category.htm): Categories act as headers that visually divide the layout into different sections. You can create a category for each sub-task in a review. - Second paragraph: For each layout, Relativity automatically creates a default category. The category contains a default name field that Relativity assigned to it based on the layout's object type. For example, the default category contains the document identifier when the object type of the layout is document and a Name field when the object type is OCR Set or Analytics Profile. - Headings: H1: Creating a new category | H2: Adding and editing categories | H2: Category properties - [Layouts] (https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Layouts.htm): Layouts are web-based coding forms that give you the ability to view and edit document fields. You can use layouts to develop workflows specific to the needs of your case. You can develop layouts that contain only the fields required to complete specific review tasks, making the review process clean and intuitive. You can also use object-level permissions to turn layouts on and off as necessary. - Second paragraph: The following permissions are needed to use layouts: - Headings: H1: Layouts | H2: Layouts permissions | H2: Creating and editing layouts | H2: Layout Information fields | H3: Changing layouts | H2: Using the layout builder | H3: Layout Options console | H3: Creating and editing a layout group | H3: Saving the layout | H2: Adding a choice to a layout | H2: Pop-ups on the layout - [Using the rich text editor] (https://help.relativity.com/RelativityOne/Content/Relativity/Layouts/Using_the_rich_text_editor.htm): The rich text editor provides support for hyperlinks, images, and tables, and is optimized for copying/pasting from Microsoft Word. - Second paragraph: It also features the following: - Headings: H1: Using the rich text editor | H2: Rich text editor features | H3: Copying and pasting ### Legal Hold - [Microsoft Azure AD technical setup] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Legal_Hold/Microsoft_Azure_AD_technical_setup.htm): This guide will take you through the technical requirements to send legal hold notices, preserve in place, and connect to your Entra ID to sync employee information. To do this, you need to create one application to link these functions. Use this guide when setting up the required syncs that Relativity needs to integrate with their system. - Second paragraph: Organizations that prefer to pull employee information from another source can import import employee information with a .csv file. - Headings: H1: Microsoft Entra ID technical setup | H2: Microsoft settings for Legal Hold | H3: Relativity application registration requirements | H3: Registering an Azure application and credentials | H3: SMTP server information | H2: Microsoft Settings for preservation hold | H3: Microsoft 365 admin account | H3: Collecting required preservation information ### Library scripts - [Australian Document ID] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Australian_Document_ID.htm): The Australian Document ID Relativity script gives you the flexibility to renumber your Relativity documents and Host/Family fields into a standard Prefix, Box, Folder and Document format. For example, ABC.001.001.0001. - Second paragraph: The script will maintain an audit of all changes. - Headings: H1: Australian Document ID | H2: Special considerations | H2: Downloading the script from the Community | H2: Installing to the Relativity Script Library | H2: Installing Australian Document ID application to a workspace | H2: Running the solution - [Billing statistics - case rollup] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Billing_statistics_-_case_rollup.htm): The Billing Statistics - Case Rollup script is a billing script that reports on peak billable data for all cases in a Relativity environment; this can be used in environments where the auto-emailed statistics feature is not possible. - Headings: H1: Billing statistics - case rollup - [Billing Statistics - RelativityOne - Case Rollup] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Billing_statistics_-RelOne_-case_rollup.htm): The Billing Statistics - Case Rollup script is a billing script that reports on peak billable data for all cases in a Relativity environment; this can be used in environments where the auto-emailed statistics feature is not possible. - Headings: H1: Billing statistics - RelativityOne - case rollup - [Billing statistics - users] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Billing_statistics_-_users.htm): This script is a billing script that reports on all users who had their Relativity access enabled during a specific month. This script can be run at any time from Home. - Headings: H1: Billing statistics - users - [Case permission audit report] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Case_permission_audit_report.htm): For a given Relativity instance, the Case Permission Audit Report script generates a report that lists all users, workspaces, and groups, as well as each group - Second paragraph: Consider the following when working with the Case Permission Audit Report script. - Headings: H1: Case permission audit report | H2: Special considerations | H2: Inputs | H2: Outputs | H2: Running the script - [Check Converted Documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Check_Converted_Documents.htm): This script returns previously converted documents and their document types. - Second paragraph: Before running the script you must have documents previously converted or produced. - Headings: H1: Check Converted Documents | H2: Inputs | H2: Results - [Choice field stratified sampling] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Choice_field_stratified_sampling.htm): This script selects a specified number of sample documents across categories chosen by the user, ensuring that each category is represented equally. - Second paragraph: Examples of how to use this script include: - Headings: H1: Choice field stratified sampling | H2: Special considerations | H2: Inputs | H2: Results - [Copy To Legacy Document Fields] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Copy_to_Legacy_Document_Fields.htm): This script updates Bates fields you create on the Document table with the Bates numbering information stored in the Production Information RDO of a production you select. - Second paragraph: This script is available as a feature in Post Production. Using Post Production has several benefits over using script. It is run automatically, improves performance, provides information about progress and gives an indication on the Production Set console that something has been run. See Production sets for more information. - Headings: H1: Copy To Legacy Document Fields | H2: Special considerations | H2: Inputs | H2: Results - [Create cluster upgrade jobs] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Create_Cluster_Upgrade_Jobs.htm): This Relativity script creates job entries in the EDDS.eddsdbo.ClusterUpgradeJobs database table. The job entries are used to upgrade Analytics clusters for performance improvements introduced in CAAT 3.17.2 and above. - Second paragraph: You can run this script to create cluster upgrade jobs for a specific workspace or all workspaces in your environment. The script identifies all the clusters in a selected workspace or all workspaces that have a Version column value equal to 0 in the ContentAnalystCluster table and do not have an entry in the EDDS.eddsdbo.ClusterUpgradeJobs table. The script creates the ClusterUpgradeJobs table if it doesn't already exist. The table contains the following columns and data: - Headings: H1: Create Cluster Upgrade Jobs | H2: Special considerations | H2: Inputs | H2: Results - [Create sample set] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Create_sample_set.htm): This script is used to randomly sample documents from a saved search to create a sample set. This is a case functionality script to be run at the case level. This script should not be run at the system level. - Headings: H1: Create sample set - [Forgotten password reset audit] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Forgotten_password_reset_audit.htm): This Relativity script provides audit records for user password reset requests generated using the Forgot your password? link on the login screen. - Headings: H1: Forgotten password reset audit - [Globally administer keyboard shortcuts] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Globally_administer_keyboard_shortcuts.htm): The Relativity script for globally administering keyboard shortcuts forces the assignment of a keyboard shortcut for a specific system function across all workspaces. The script overwrites existing keyboard shortcuts currently assigned to other system functions, fields, or choices. After the script runs, the updated keyboard shortcut is available for use in the Core Reviewer Interface. - Second paragraph: System Functionality - Headings: H1: Globally administer keyboard shortcuts | H2: Category | H2: Special considerations | H2: Inputs | H2: Results - [Lockbox Bypass report] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Lockbox_Bypass_Report.htm): The Lockbox Bypass Report script provides audit history of changes to the Lockbox instance setting, by whom, and when. - Second paragraph: To run the script: - Headings: H1: Lockbox Bypass report | H2: Running the script | H2: Outputs - [Lockbox report] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Lockbox_Report.htm): The Lockbox Report script will list out all workspaces where anyone at Relativity ODA LLC has current access to along with the name of the group that the Relativity ODC LLC user is linked to. - Second paragraph: Consider the following when working with the Lockbox Report script. - Headings: H1: Lockbox report | H2: Special considerations | H2: Running the script | H2: Outputs - [Monitor cluster upgrade jobs] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Monitor_Cluster_Upgrade_Jobs.htm): This Relativity script checks and reports the status of all Analytics cluster upgrade jobs recorded in the EDDS.eddsdbo.ClusterUpgradeJobs database table. - Second paragraph: Consider the following when running this script: - Headings: H1: Monitor Cluster Upgrade Jobs | H2: Special considerations | H2: Inputs | H2: Results - [Populate parent ID to child] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Populate_parent_ID_to_child.htm): Populate parent ID to child is a workspace-level script that propagates the Document ID of the parent document to any children of that document. - Second paragraph: When running email threading (under the Structured analytics set tab), attachments aren't threaded with their parent emails if the Parent Document ID field is blank for the attachment, or if it's mapped to a field that doesn't use a supported format. If your document set includes attachments with unpopulated Parent Document ID fields, run the Populate parent ID to child script before running email threading. For information on supported formats, see See Analytics profiles. - Headings: H1: Populate parent ID to child | H2: Special considerations | H3: Recommended prep work | H2: Inputs | H2: Running the script - [Processing Statistics] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Processing_Statistics.htm): This Relativity system-level script provides you with the option of displaying. - Second paragraph: This is a Relativity script that runs at the environment level. You must run this script while in Home mode, as it won't work from the workspace. - Headings: H1: Processing Statistics | H2: Category | H2: Special considerations | H2: Input and preparation | H2: Script results | H3: Returned output - detailed display type | H2: File size changes in script report | H2: Returned output - summary display type - [Propagate sent date to family documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Propagate_sent_date_to_family_documents.htm): This Relativity script sets all email families documents to the same sent date as their parent documents in a case. This allows for chronological sorting within all documents. - Second paragraph: This is a case functionality script to be run at a case level. - Headings: H1: Propagate sent date to family documents | H2: Special considerations | H2: Inputs | H2: Results - [Relativity Script Library] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Relativity_Script_Library.htm): The following is a list of standard scripts available in Relativity. This list may vary per version of Relativity. - Second paragraph: These scripts are available in the Relativity Script Library. To access the script library: - Headings: H1: Relativity Script Library - [Report sample-based statistics] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Report_sample-based_statistics.htm): This script generates reports for the deprecated sample-based learning feature. If you have legacy sample-based learning projects in your workspace, you can select one and generate several types of reports based on its contents. - Second paragraph: Because the sample-based learning feature is now deprecated, you cannot modify the data within the projects or create new ones. These reports show each legacy project as-is, regardless of whether the project was completed. - Headings: H1: Report sample-based statistics | H2: Report types | H2: Inputs | H2: Results - [Reviewer statistics] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Reviewer_statistics.htm): The Relativity Reviewer Statistics scripts report on the efficiency of reviewers over the specified date range. - Second paragraph: The Relativity Reviewer Statistics scripts report on the efficiency of reviewers over the specified date range. The returned statistics provide a count on how many documents were reviewed over a certain period of time. Time zone of the reviewers must be specified in order for the report to accurately account for reviewers in different time zones. - Headings: H1: Reviewer statistics | H2: Inputs | H2: Results - [Saved search gap and overlap check] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Saved_search_gap_and_overlap_check.htm): This workspace script finds documents with gaps in Bates numbers or overlapping Bates numbers. - Second paragraph: Consider the following when working with this script: - Headings: H1: Saved search gap and overlap check | H2: Special considerations | H2: Inputs | H2: Outputs | H2: Running the script - [Set duplicate flag field] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Set_duplicate_flag_field.htm): This Relativity script identifies and sets a Yes/No field on all case documents to indicate them as original or duplicate. - Second paragraph: This is a case functionality script to be run at a case level. - Headings: H1: Set duplicate flag field | H2: Special considerations | H2: Inputs | H2: Results - [Set extracted text size field] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Set_extracted_text_size_field.htm): This Relativity script stores a document - Headings: H1: Set extracted text size field - [Set native file size field v4] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Set_native_file_size_field_v4.htm): This Relativity script stores the native file size (in Kilobytes), for each case document in a decimal field; used where the field’s value is empty. - Second paragraph: Consider the following when running this script: - Headings: H1: Set native file size field v4 | H2: Special considerations | H2: Inputs | H2: Results - [Set production beg/end attach fields] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Set_production_beg-end_attach_fields.htm): This script populates the production beginning and end attachment range fields for each document included in a production. This is a case functionality script to be run at a case level. - Second paragraph: The risks outlined below must be considered when running this script: - Headings: H1: Set production beg/end attach fields | H2: Special considerations | H2: Inputs | H2: Results - [Set Relativity folder path field] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Set_Relativity_folder_path_field.htm): This Relativity case script stores the current Relativity folder path of each document in a long text field. This allows you to see the full path structure of a folder for example, Custodian / J Smith / Inbox. - Second paragraph: This script populates the new long text field with the current case folder structure. - Headings: H1: Set Relativity folder path field | H2: Special considerations | H2: Inputs | H2: Results - [Total Automated Workflows in Instance] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Total_Automated_Workflows_in_Instance.htm): This script reports on the number of workflows in your instance as well as displaying the current status of workflows too. Additionally, you can see the starting and ending date for the most recent run of each workflow in the script results. - Second paragraph: The Total Automated Workflows in Instance script is installed automatically when you install the Automated Workflows application. To learn more about this application, visit Automated Workflows. - Headings: H1: Total Automated Workflows in Instance | H2: Inputs | H2: Results - [Upgrade legacy applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Library_scripts/Upgrade_legacy_applications.htm): This Relativity script performs an upgrade of version 6.8 Relativity applications and earlier. It can also be used to upgrade a 6.9 or 6.10 Relativity application if it was exported with the ADS Utility. - Second paragraph: Choose an application from the Application field. Only applications from Relativity 6.8 or earlier and 6.9 or 6.10 applications that were exported with the ADS utility are available in this drop-down menu. - Headings: H1: Upgrade legacy applications | H2: Inputs | H2: Results ### Management Console - [Cost Explorer] (https://help.relativity.com/RelativityOne/Content/Management_Console/Cost_Explorer.htm): The RelativityOne Cost Explorer gives you access to billing and usage data for your RelativityOne instances. - Second paragraph: This functionality assists users to: - Headings: H1: Cost Explorer | H2: Using Cost Explorer | H3: Contextual billing help banners | H3: Quick search | H3: Time frame selector | H2: Data usage tab | H3: Workspaces table | H3: Excel export | H2: Users tab | H3: Users table | H2: Extend products tab | H2: Cost explorer vs Usage reports - [Management Console] (https://help.relativity.com/RelativityOne/Content/Management_Console/Management_Console.htm): Management Console offers a variety of reports to provide general oversight and statistics across the instance, particularly focusing on cost and usage. The reports available include: - Second paragraph: To access reports within Management Console, hover over the More button, then hover over Mgmt. Console to view the list of reports. Click the desired report name. - Headings: H1: Management Console - [Usage Reports] (https://help.relativity.com/RelativityOne/Content/Management_Console/Usage_Reports.htm): 003 - Second paragraph: For a complete list of fields available in the Usage Reports, see Usage Report fields, below. - Headings: H1: Usage Reports | H2: Permissions | H2: Creating Usage Reports | H2: Data freshness and expected delays | H2: Exporting Usage Reports | H2: Usage Report Fields ### Mass operations - [Cancel Production Job] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Cancel_Production_Job.htm): To cancel multiple production jobs from the Production Queue tab, use the Cancel Production Job mass operation. - Second paragraph: You must configure certain instance level permissions to use Cancel Production Job. - Headings: H1: Cancel production job | H2: Security configuration | H2: Using Cancel Production Job - [Invite users] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Invite_users.htm): You can use the Invite operation to send out invitation to newly-created users to log in to Relativity and set their passwords. The mass operation is available from the mass operations bar. This feature is useful when setting up a large number of reviewers in a new case. - Second paragraph: You cannot use mass operations on Data Grid-enabled fields. - Headings: H1: Invite users - [Mass convert] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_convert.htm): Use Mass convert to pre-convert a large set of documents into HTML5 format before review. By using mass convert you can eliminate document load time in the viewer. - Second paragraph: You can access Mass Convert from the mass operations bar on the document list. Choose whether to convert checked items or all items in the current result set. Then, select Convert from the drop-down menu and complete the fields on the Convert Documents layout. - Headings: H1: Mass convert | H2: Conversion options | H2: Limitations - [Mass copy] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_copy.htm): Use Mass copy to copy items within Relativity. By using mass copy you can easily copy and rename items to improve workflows. - Second paragraph: You cannot use mass operations on Data Grid-enabled fields. - Headings: H1: Mass copy - [Mass delete] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_delete.htm): You can use the Mass delete operation to remove a group of documents or objects from Relativity in a single operation. When you delete documents, you can also remove their images and natives from the file servers. Mass delete is available from the mass operations bar. - Second paragraph: Remove documents and objects efficiently with Mass delete. This feature lets you delete a group of documents or objects from Relativity in one go. You can even choose to remove their associated images and native files from the file servers for a more comprehensive cleanup. - Headings: H1: Mass delete | H2: Mass delete permissions | H3: Deleting documents that were published through Processing has two key effects: | H3: Special considerations | H2: Performing a mass delete on other objects | H2: Enabling or disabling snapshot auditing on delete - [Mass edit] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_edit.htm): You can use the mass edit operation to modify fields and coding values for multiple documents or objects at the same time. You can use any layout that you have rights to. Mass edit is available from the mass operations bar. - Second paragraph: You cannot use mass operations on Data Grid-enabled fields. - Headings: H1: Mass edit | H2: Working with multi-choice fields on the mass edit form - [Mass export to file] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_export_to_file.htm): Use the Export to file (previously known as Export to Excel) operation to export the contents of the current list to a file. Any items and fields in the current view or report are exported. Unicode characters are permitted. Mass export to file is available from the mass operations bar. - Second paragraph: All fields in the current view and its content are exported, including unicode characters. Mass export to file is available from the mass operations bar. - Headings: H1: Mass export to file | H2: Considerations | H2: Fields - [Mass image] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_image.htm): Mass imaging creates TIFF or JPEG images for a document set based on the settings in the imaging profile you select. Relativity also provides a default imaging profile that you can use out-of-the-box. You can customize profiles to create color JPEG images, adjust image size, and leverage other formatting options. Mass image is available from the mass operations bar. - Second paragraph: The mass image operation uses the same technology as the Relativity native file viewer. - Headings: H1: Mass image - [Mass move] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_move.htm): You can use the mass move operation to move selected documents from their current folder to another existing folder. If you mass move any documents, any custom security applied to those documents is lost. The document inherits the rights of the new parent folder. Mass move is available from the mass operations bar. - Second paragraph: If documents are moved in error, you have two options to reverse the action: - Headings: H1: Mass move - [Mass operation jobs] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_operation_jobs.htm): You can use the mass move operation to move selected documents from their current folder to another existing folder. If you mass move any documents, any custom security applied to those documents is lost. The document inherits the rights of the new parent folder. Mass move is available from the mass operations bar. - Second paragraph: An Edit mass operation job appears on this page. However, a mass Save as PDF job doesn't appear here because it's already included in the PDF Queue. For more details, see the Mass Operation Type list below. - Headings: H1: Mass Operation Jobs status - [Mass operations] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_operations.htm): Using mass operations, you can perform actions on a set of documents at once instead of performing the same action for each individual document. Some mass operations are available to reviewers, while some are limited to system admins. Access to each mass operation can be granted individually. - Second paragraph: For details on how to monitor the status of a mass operation that you've started, see Mass operation jobs. - Headings: H1: Mass operations | H2: List of standard mass operations | H2: Mass operations permissions - [Mass PDF] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_PDF.htm): With the Mass PDF operation you can save natives, images, and produced document as PDFs and print them once you save them. The Mass PDF application is available from the mass operations bar on the document list. - Second paragraph: The PDF application has the following associated permissions: - Headings: H1: Mass PDF | H2: Considerations | H2: PDF permissions | H2: PDF profile | H3: PDF Profile Types | H2: Creating PDF | H2: Branding PDF | H2: Creating PDFs via mass operation | H3: Using the Password Bank to Create PDFs from Password-Protected Natives | H3: Mass PDF progress bar - [Mass replace] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_replace.htm): You can use the mass replace operation to replace existing long or fixed-length field text with new content. Mass replace is available from the mass operations bar. - Second paragraph: You cannot use mass operations on Data Grid-enabled fields. - Headings: H1: Mass replace - [Mass Save as List] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Mass_Save_as_List.htm): To save a group of documents as a list, follow this procedure. The same steps apply to other objects with Lists enabled. Always begin by clicking the tab of the object for which you want to save a new list. Mass Save as List is available from the mass operations bar and the related items pane in the viewer. Mass Save as List is available from the mass operations bar and the related items pane in the viewer. - Second paragraph: You cannot use mass operations on Data Grid-enabled fields. - Headings: H1: Mass Save as List - [Move to folder path] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Move_to_folder_path.htm): Move to folder path is a mass operation used for moving documents to a new folder that you specify in a text field on the document object. This solution is one component of the Document Utilities application. Visit the Relativity Customer Portal to download the Document Utilities application. - Second paragraph: You can use the move to folder path mass operation to move documents to a new folder that you specify in a text field on the document object. Relativity automatically creates the new folder when you run this mass operation. You can also specify a default folder that Relativity uses when the destination folder path isn't set on a document. You must install the Document Utilities application to add the Move to folder path mass operation to your workspace. - Headings: H1: Move to folder path | H2: Prerequisites for the move to folder path mass operation | H3: Installing the Document Utilities application | H3: Setting required security permissions | H2: Running the move to folder path mass operation | H3: Fields for move to folder path mass operation - [PDF Queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/PDF_Queue.htm): PDF Queue is a sub-tab of Queue Management. From this screen, you can monitor all PDF jobs across an instance of Relativity that are not yet complete. - Second paragraph: To cancel a PDF job: - Headings: H1: PDF Queue | H2: PDF Queue columns | H2: Cancel a PDF job - [PDF Sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/PDF_Sets.htm): With the Mass PDF operation you can save natives, images, and produced document as PDFs and print them once you save them. The Mass PDF application is available from the mass operations bar on the document list. - Second paragraph: Before executing a PDF Set, you must create a Saved Search. This is the data source the PDF set will be run on. You will also need a PDF Profile. - Headings: H1: PDF Sets | H2: Prerequisites | H2: Executing PDF Sets | H3: PDF Lists page | H2: Current limitations - [Retry Production Job] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Retry_Production_Job.htm): To retry multiple production jobs from the Production Queue tab, use the Retry Production Job mass operation. - Second paragraph: See these related pages: - Headings: H1: Retry Production Job | H2: Security configuration | H2: Retrying production jobs - [Set long text size] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Set_long_text_field_size.htm): You can use the set long text size operation to calculate long text for each selected document and save the value in a decimal field. This feature can be used with both SQL and Data Grid long text fields. - Second paragraph: To enable the mass operation in your Relativity instance, you must import the Long Text Size application from the application library. To do this, you must have the appropriate admin rights. - Headings: H1: Set long text field size | H2: Before you begin | H3: Set long text field size considerations | H2: Using the mass operation - [Tally/sum/average] (https://help.relativity.com/RelativityOne/Content/Relativity/Mass_operations/Tally_sum_average.htm): You can use the tally/sum/average operation to tally, sum, or average the values of fixed-length text, choice, user, and number fields associated with documents or objects. This operation is commonly used to determine the number of pages in a print job or production. For documents, it - Second paragraph: This operation is commonly used to determine the number of pages in a print job or production. For documents, it's recorded under the document history. Tally/sum/average is available from the mass operations bar. - Headings: H1: Tally/sum/average | H2: Considerations ### MCP - [RelativityOne MCP] (https://help.relativity.com/RelativityOne/Content/Relativity/MCP/RelativityOne_MCP.htm): The RelativityOne MCP server is designed to give AI assistants access to RelativityOne capabilities through Model Context Protocol, an open standard for connecting AI tools to external data and services through MCP clients. As a system administrator, you can use it to perform day-to-day tasks such as managing matters, configuring workspaces, granting access, and reviewing system usage. - Second paragraph: Before you enable the MCP connection, confirm that you have the following: - Headings: H1: RelativityOne MCP | H2: Considerations | H2: Setup | H3: Prerequisites | H3: Setting up Claude Web or Claude Desktop | H2: Available tools | H3: Cross-tool prompts | H3: How prompts translate to tool calls | H2: Data Processing Agreement | H2: Privacy and Cookie Policy - [RelativityOne MCP Gateway] (https://help.relativity.com/RelativityOne/Content/Relativity/MCP/RelativityOne_MCP_Gateway.htm) ### Migrate - [Migrate] (https://help.relativity.com/RelativityOne/Content/Data_migration/Migrate/Migrate.htm): Migrate is used to migrate large numbers of workspaces from Relativity Server to RelativityOne. Your data migration will be seamless and intuitive, allowing workspaces to be migrated in just a few clicks. - Second paragraph: Related topics: - Headings: H1: Migrate | H2: Permissions | H2: Migrate considerations | H3: Migrating Client Domains | H3: Migrating from RelativityOne to RelativityOne - [Migrate files first workflow] (https://help.relativity.com/RelativityOne/Content/Data_migration/Migrate/Migrate_files_first_workflow.htm): You can use the Files first migration workflow for large and active workspaces. This workflow will give you the flexibility to schedule workspace downtime for an active case. At a high level, the first step in the Files first workflow requires copying over the workspace repository files from the server instance over to RelativityOne. This reduces the size of the archive, transfer, and restoration. As a result, this reduces the overall workspace downtime. Once the files are transferred, the Migration job can be started, which will make the workspace inactive until restoration is complete. - Second paragraph: For instructions on Migrate setup and configuration, go to Migrate setup page. - Headings: H1: Using Migrate (Files first workflow) | H2: Preparing server instance for migration | H3: Step 1 - Pre-migration file validation | H3: Step 2 - Installing and launching RelativityOne Staging Explorer on the server instance | H3: Step 3 - Copying workspace files to the RelativityOne environment | H2: Preparing RelativityOne instance for migration | H3: Step 1 - Configuring ARM Archive Location | H3: Step 2 - Configuring Migration | H3: Step 3 - Tracking migrations | H3: Step 4 - Post-migration file validation | H2: Other available actions | H3: Changing the migration name | H3: Canceling migration setup | H3: Canceling workspace migration | H3: Managing email notifications | H2: Verifying instance settings when restoring to client domains | H2: Troubleshooting errored workspace migrations | H3: Retrying failed workspace migrations | H3: Abandoning failed workspace migrations | H2: Workspace migrations during RelativityOne maintenance window - [Migrate setup] (https://help.relativity.com/RelativityOne/Content/Data_migration/Migrate/Migrate_setup.htm): This task should be performed under the guidance of your RelativityOne specialist. Please submit a request via the Customer Support form for assistance. - Second paragraph: Before you install Migrate, it's recommended that you copy all required ID values to a text file so that you can easily copy and paste them during installation. These include: - Headings: H1: Migrate setup and configuration | H2: Pre-installation considerations | H2: Migrate network setup | H2: Installing and configuring Migrate (RelativityOne) | H2: Installing and configuring Migrate (Relativity Server) | H3: Relativity Server 2024 and above | H3: Relativity Server versions below 2024 - [Migrate workflow] (https://help.relativity.com/RelativityOne/Content/Data_migration/Migrate/Migrate_workflow.htm): Before creating a new migration, you must first register your Relativity Server instance to define a migration source. This will allow you to view all the workspaces from the given Relativity Server instance in Migrate. - Second paragraph: You cannot delete an instance which has been already used as migration source for any migration (regardless of the status of the migration). - Headings: H1: Using Migrate (workflow) | H2: Managing the migration source | H3: Registering your Relativity Server instance with RelativityOne for the first time | H3: Adding an additional migration source | H3: Editing a migration source | H3: Deleting registration of a migration source | H2: Primary migration workflow | H3: Step 1 - Creating a new migration | H3: Step 2 – Selecting and assigning workspaces for migration | H3: Step 3 – Previewing your migration | H3: Step 4 – Migration | H3: Step 5 - Tracking migrations | H2: Other available actions | H3: Changing the migration name | H3: Canceling migration setup | H3: Canceling workspace migration | H3: Managing email notifications | H2: Troubleshooting errored workspace migrations | H3: Retrying failed workspace migrations | H3: Abandoning failed workspace migrations | H2: Workspace migrations during RelativityOne maintenance window ### Mobile - [Coding documents] (https://help.relativity.com/RelativityOne/Content/Mobile/Coding_documents.htm): Code documents on the go with RelativityOne - Second paragraph: Before coding a document, make sure you are in the correct layout and group. For more information, see Selecting a coding layout . Once the layout is set, follow the steps below: - Headings: H1: Coding documents | H2: Coding a document | H3: Coding fields | H3: Propagation | H3: Document skip | H3: Event Handlers | H2: Selecting a coding layout | H3: Multiple layout groups | H2: Automatic-layout navigation | H2: Copying from previous - [Documents] (https://help.relativity.com/RelativityOne/Content/Mobile/Documents.htm): Focus on viewing and coding documents in RelativityOne - Second paragraph: You can perform the following actions to find a document in your document list: - Headings: H1: Documents | H2: Document list | H3: Filtering | H3: Searching | H2: Document viewer | H3: Changing viewers - [Folders] (https://help.relativity.com/RelativityOne/Content/Mobile/Folders.htm): RelativityOne - Second paragraph: RelativityOne's mobile app includes searching functionality within the Folders browser to decrease the number of taps to find the correct folder. To search, follow the steps below: - Headings: H1: Folders | H2: Using the Folders browser | H3: Searching in Folders - [Mobile] (https://help.relativity.com/RelativityOne/Content/Mobile/Mobile.htm): View and code documents on the go from your iPad or an iPhone with RelativityOne - Second paragraph: The features in RelativityOne's mobile app allow you to: - Headings: H1: RelativityOne's mobile experience | H2: Unified experience with RelativityOne | H2: Device and system requirements | H2: Understanding the ADS app and OAuth2 client - [Mobile Admin] (https://help.relativity.com/RelativityOne/Content/Mobile/Mobile_Admin.htm): Set up users, groups, and workspaces from anywhere with the RelativityOne app for iOS. - Second paragraph: All lists are searchable. Pull down on the device and a search bar appears. - Headings: H1: Admin | H2: Users | H2: Groups | H2: Workspaces - [Navigation] (https://help.relativity.com/RelativityOne/Content/Mobile/Navigation.htm): Navigating RelativityOne - Second paragraph: RelativityOne's mobile app offers several login methods. The following methods are supported – Username and password, RSA, Active Directory authentication, Integrated Windows, and OpenID Connect. The SAML method of logging in isn't supported. For more information on these methods, see Logging in to Relativity. - Headings: H1: Navigation | H2: Opening the app | H3: Creating a passcode | H3: Logging in | H3: Instance URL | H3: Exceeding passcode limits | H2: Opening a workspace | H3: Switching workspaces | H2: General navigation and icons | H3: Apple keyboard shortcuts | H2: Pull to refresh - [Offline] (https://help.relativity.com/RelativityOne/Content/Mobile/Offline.htm): Work offline with the RelativityOne mobile app for iOS. - Second paragraph: Downloads are automatically wiped if the user has not authenticated in 30 days. The user will see the download cell update to "Download Expired – Swipe to Delete" notifying them the download has been deleted from the app. - Headings: H1: Offline | H2: Security | H2: Permissions | H2: Downloading a saved search or folder | H2: Viewing downloaded documents - [Saved searches] (https://help.relativity.com/RelativityOne/Content/Mobile/Saved_searches.htm): RelativityOne - Second paragraph: In RelativityOne's mobile app, you can view already created saved searches and saved search folders. To run an already created saved search, follow the steps below: - Headings: H1: Saved searches | H2: Running a saved search | H2: Searching for saved searches | H2: Sharing a saved search - [Security] (https://help.relativity.com/RelativityOne/Content/Mobile/Security.htm): With Relativity - Second paragraph: Relativity's mobile app incorporates the following additional security measures to protect your information from theft: - Headings: H1: Security | H2: Security information | H3: iOS data protection | H3: Improving security | H3: Restoring from iCloud and iTunes - [Support & Settings] (https://help.relativity.com/RelativityOne/Content/Mobile/Support___Settings.htm): Switch your workspace, get mobile support and update your RelativityOne mobile app settings in the More tab. - Second paragraph: To switch workspaces while already in one, click More. In the More menu, tap the Switch Workspace to view a workspace list. Locate the workspace by searching or scrolling through the list. Tap on the desired workspace to open. - Headings: H1: Mobile support and settings | H2: Switching workspaces | H2: Support | H2: Settings | H3: Updating your passcode | H2: Logout ### OCR - [OCR] (https://help.relativity.com/RelativityOne/Content/Relativity/OCR/OCR.htm): Optical Character Recognition (OCR) translates images of text, such as scanned and redacted documents, into actual text characters. - Second paragraph: With OCR you can view and search on text that's normally locked inside images. It uses pattern recognition to identify individual text characters on a page, such as letters, numbers, punctuation marks, spaces, and ends of lines. - Headings: H1: OCR | H2: Document characteristics that affect OCR quality | H2: Creating and editing an OCR profile | H3: OCR profile fields | H2: Creating and editing an OCR set | H3: OCR set fields | H2: Running an OCR set | H2: Viewing OCR text - [OCR on redacted production documents] (https://help.relativity.com/RelativityOne/Content/Relativity/OCR/OCR_on_redacted_production_documents.htm): Preparing redacted documents for production in an efficient manner is a common challenge in eDiscovery. This topic provides details on completing OCR on redacted documents and exporting the text. - Second paragraph: To run OCR on your production, perform the following steps. You should do so after you run the production but before you perform the final export. - Headings: H1: OCR on redacted production documents | H2: Running the OCR job | H2: Exporting a production - [OCR queue] (https://help.relativity.com/RelativityOne/Content/Relativity/OCR/OCR_queue.htm): Your permission settings determine whether or not you have access to the OCR Queue tab from Home. The OCR Queue tab allows you to view all submitted OCR jobs in the environment to check their status, priority, and the workspace to which they belong. You can only access the OCR Queue tab from Home. - Second paragraph: OCR queue columns - Headings: H1: OCR queue ### PDF Downloads - [PDF downloads] (https://help.relativity.com/RelativityOne/Content/Site_Resources/PDF_Downloads/R1_PDF_Downloads.htm): This page contains PDF versions of the documentation on this site. The PDFs posted here are updated daily, so we recommend bookmarking the PDFs instead of saving them locally or printing. - Second paragraph: Ultimately, we recommend using the website to get the most up-to-date information. If you have trouble accessing any of these guides, contact us using the form at the bottom of this page. - Headings: H1: RelativityOne PDF downloads | H2: Feature guides | H2: Importing and exporting | H2: Miscellaneous | H2: Zip files ### Persistent highlight sets - [Creating efficient searches for persistent highlighting] (https://help.relativity.com/RelativityOne/Content/Relativity/Persistent_highlight_sets/Creating_efficient_searches_for_persistent_highlighting.htm): Creating efficient searches improves the performance of persistent highlighting, whether you - Second paragraph: Avoid the following when writing searches for persistent highlighting: - Headings: H1: Creating efficient searches for persistent highlighting | H2: Using terms search | H2: Using highlight fields - [Creating persistent highlight sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Persistent_highlight_sets/Creating_persistent_highlight_sets.htm): To create a new persistent highlight set, follow these steps. - Second paragraph: If you plan to use the Source: Highlight Fields, you may need to create a search terms report. For more information, see Using the highlight fields source. - Headings: H1: Creating persistent highlight sets | H2: Fields - [Entering highlight terms] (https://help.relativity.com/RelativityOne/Content/Relativity/Persistent_highlight_sets/Entering_highlight_terms.htm): If you choose Terms as the source of your highlighting, you have to enter the terms in the Terms field text box to save the new highlight set. You also have the option of applying color-coding to these terms in the Viewer. - Second paragraph: When you enter a term in the Highlight Terms box, you can also specify the color for both the text and the background. Use the following format to color-code your persistently highlighted text: - Headings: H1: Entering highlight terms | H2: Color-coding persistent highlights | H2: Guidelines for adding terms or phrases - [Persistent highlight sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Persistent_highlight_sets/Persistent_highlight_sets.htm): Persistent highlight sets allow you to configure and apply term highlighting to assist with document review in the viewer. In the Persistent Highlight Pane of the viewer, you can see all sets saved in a workspace and apply or hide term highlights in the document you - Second paragraph: If a document you are reviewing contains any of the terms specified in a set, the list of terms and the number of times they appear in the document appear under the set. If a document contains no terms from the set, you can not expand or collapse the set in the tree. If the document contains some terms in the set, only the terms that exist in the document appear below the set name. - Headings: H1: Persistent highlight sets | H2: Getting started with persistent highlight sets | H3: Showing and hiding persistent highlight sets in the Viewer | H3: Navigating persistent highlight hits in the Viewer | H3: Recent searches in the Persistent Highlight Sets pane | H3: Navigating highlighted terms in the Viewer | H3: Persistent highlight set behavior across Viewers | H3: Persistent highlight behavior | H2: Using multiple persistent highlight sets | H2: Performance considerations | H3: Individual document size | H3: Number of terms | H3: Types of operators used | H3: Local machine - [Using the highlight fields source] (https://help.relativity.com/RelativityOne/Content/Relativity/Persistent_highlight_sets/Using_the_highlight_fields_source.htm): Using the Highlight Fields source in a persistent highlight set allows you to choose a field referencing a list of terms to highlight. - Second paragraph: Select the Highlight Fields option, and then click the Select button to open the Select items - Highlight Fields modal. This system view displays the Name and Object Type for applicable multiple object fields, including those created by Search Terms Reports. - Headings: H1: Using the highlight fields source | H2: Best practices ### Pivot - [Pivot] (https://help.relativity.com/RelativityOne/Content/Relativity/Pivot/Pivot.htm): Using Pivot, you can quickly analyze your workspace data to identify trends or patterns. You can use Pivot to summarize data in tables or charts, simplifying the analysis process. You can also create ad hoc Pivot reports using the options available on the Pivot menu. - Second paragraph: To generate a Pivot report, you specify a field for grouping data totals and further characterize this data by selecting a secondary field. The Pivot grid displays your results in a table format that you can customize for more convenient viewing. See Running Pivot reports. - Headings: H1: Pivot - [Pivot profiles] (https://help.relativity.com/RelativityOne/Content/Relativity/Pivot/Pivot_profiles.htm): Using Pivot profiles, you can create, save, and edit custom Pivot settings to use at any time. Once saved, these profiles are accessible via a drop-down menu in the upper left corner of the item list. - Second paragraph: Pivot profiles include configured settings for the Group By, Pivot On, and Date fields, as well as the chart formats. When you select a profile, the fields in the Pivot menu automatically populate with predefined values. You can modify these values to run additional pivot reports. Use the Save button to save any updates to the preexisting profile or use the Save As button to create a new pivot profile. - Headings: H1: Pivot profiles | H2: Creating or editing a pivot profile - [Running Pivot reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Pivot/Running_Pivot_reports_in_the_new_UI_framework.htm): The Pivot menu displays options to run reports on pivot-enabled fields in views and saved searches. - Second paragraph: The Pivot color map has been expanded to include 14 colors. When a chart is created, the color map checks to see if there are already colors assigned to a value in the chart. If there are assigned colors, the chart will maintain those colors. If not, a new color will be assigned for that value to help maintain color consistency. To learn more, see Color Map. - Headings: H1: Running Pivot reports | H2: Pivot color map | H2: Adding a Pivot widget | H2: Pivot options | H3: Properties | H3: Display type | H3: Export | H3: Options | H2: Working with Pivot chart results | H3: Using bar charts | H3: Using pie charts | H3: Using stacked bar charts | H3: Using line charts | H3: Filtering the Document list from a Pivot chart | H3: Exporting a Pivot or cluster visualization widget | H2: Working with Pivot table results | H3: Filtering the Document list from a Pivot table | H3: Filtering on numeric fields in a Pivot table | H3: Filtering on the Group By (X) field in a Pivot table ### Pivot Quick Reference - [Dashboard and pivot quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Pivot_Quick_Reference/Dashboard_and_pivot.htm): Use this guide to navigate, create, and edit your dashboard and pivot tables. - Second paragraph: Export Dashboard button - Headings: H1: Dashboard and pivot quick reference guide ### Preservation - [Manage preservations] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Manage_preservations.htm): Manage your preservations in the console. The Preservation console is available on the Preservation Details page. - Second paragraph: To navigate to the Preservation details page, click Manage Preservation in the Legal Hold Project console or navigate to the Preservation tab and click into a preservation. - Headings: H1: Manage preservations | H2: Manage Preservations console | H2: Multiple preservation holds and release behavior | H2: Release a hold - [Preservation data] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Preservation_data.htm): After creating a preservation, more information becomes available to review and act upon. For example, you can find information on each preservation job in the Preservation Hold Job tab. - Second paragraph: In the Preservation Hold Jobs tab, you can see a list of all jobs that have taken place in the workspace. - Headings: H1: Preservation data | H2: Preservation hold jobs | H2: Preservation error | H2: Entity status | H2: Non-custodial data - [Preservation hold] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Preservation_in_place.htm): A Preservation Hold preserves files and emails in an custodian - Second paragraph: With Preservation in-place, Relativity integrates with supported third‑party applications, such as Google Workspace, Microsoft 365, and Slack, to place preservation holds where the data lives. These third‑party applications perform the actual preservation holds. - Headings: H1: Preservation in-place | H2: Preservation workflow | H3: Creating a preservation in Relativity | H3: Processing the preservation request | H3: Preserving data in third‑party systems | H3: Preservation status and tracking | H2: Preservation sources - [Preservations] (https://help.relativity.com/RelativityOne/Content/Relativity/Preservation/Preservations.htm): After integrating RelativityOne with data source, creating data sources, and the rest of the setup, you need create the preservation hold. In RelativityOne, you can create a hold for multiple data sources, custodians, non-custodian data, and preserve the data. - Second paragraph: To create a preservation project, you must create a legal hold project. For more information on a legal project, see Managing a legal hold project. After creating a legal project, you must click Preserve Data in the Project console. For more information, see Project console. - Headings: H1: Preservations | H2: Prerequisites | H2: Considerations | H2: Preservation roles | H3: Create a role | H3: Assign the role | H2: Creating a preservation | H3: Using the preservation wizard | H3: Custodian experience during preservation ### Processing - [Administration] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_Administration.htm): This topic provides an overview of processing administration, including security permissions, monitoring active jobs, post-publish delete job performance, processing history. - Second paragraph: Consider the following items related to security and client domains (formerly multi-tenancy): - Headings: H1: Processing administration | H2: Security considerations for processing administration | H2: Monitoring active jobs | H3: Post-publish delete job performance | H3: Active jobs mass operations | H2: Processing history - [Deduplication considerations] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Deduplication_considerations.htm): This page describes the workflows for global deduplication, custodial deduplication, or no deduplication. - Second paragraph: Note the following special considerations regarding deduplication: - Headings: H1: Deduplication considerations | H2: Global deduplication | H2: Custodial deduplication | H2: No deduplication | H2: Global deduplication with attachments | H2: Global deduplication with document-level errors | H2: Technical notes for deduplication | H3: Fields used for comparing files in deduplication | H3: Calculating MD5/SHA1/SHA256 hashes | H3: Calculating deduplication hashes for emails | H3: Calculating the Relativity deduplication hash - [Discovering files] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Discovering_files.htm): Discovery is the phase of processing in which the processing engine retrieves deeper levels of metadata not accessible during Inventory and prepares files for publishing to a workspace. - Second paragraph: The following graphic depicts how discovery fits into the basic workflow used to reduce the file size of a data set through processing. This workflow assumes that you are applying some method of deNIST and deduplication. - Headings: H1: Discovering files | H2: Running file discovery | H3: Discovery process | H3: Container extraction | H2: Special considerations - OCR and text extraction | H2: Monitoring discovery status | H3: Discover job details | H2: Canceling discovery - [Error workflow] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_error_workflow.htm): Errors can occur during your processing job, and Relativity provides a number of objects to make it easy to identify and address them, including the Document and Job Errors tabs and the Current Category field, among others. Once you identify an error, you can then use the Error Actions console available on the error details layout to retry or ignore that error, depending on your current needs. - Headings: H1: Error workflow - [Exception and error overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_error_overview.htm): This topic provides an overview of processing errors and exceptions, including a description of the types of exceptions you may encounter, exception levels, and where to find exception and error details. - Second paragraph: For information on resolving processing exceptions, see Processing exception resolution. - Headings: H1: Exception and error overview | H2: Types of processing exceptions | H2: Processing exception tabs | H3: Files tab | H3: Job Errors tab | H2: Viewing exceptions from a processing set | H2: Retrying exceptions after making changes to the processing profile | H2: Required security permissions - [Exception and error resolution] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_error_resolution.htm): This topic lists the types of exceptions and erros in processing, exception levels, exception phases, and how to resolve them. - Second paragraph: For information on where to find processing exception and error information in RelativityOne, see Processing exception overview. - Headings: H1: Exception and error resolution | H2: Types of processing exceptions | H2: File exceptions | H3: File exception actions | H2: Resolving file exceptions | H3: Retrying an exception from the processing set | H3: Retry file exceptions mass action | H3: Replacing corrupted files | H3: Resolving a password-protected file exception | H3: Publish documents with field length exceptions | H3: Troubleshooting corrupted .msg files in a .pst container | H2: Job errors | H3: Job error workflow | H3: Resolving job errors - [Files tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Files_tab.htm): The Files tab in Relativity Processing allows you to view and analyze a list of all discovered documents and their metadata before deduplication and publishing. - Second paragraph: The Files tab (using MDS storage) differs slightly from the current interface. Details on these changes are described in the All Files view (MDS) section. - Headings: H1: Files tab | H2: Views on the Files tab | H3: All Files view | H3: All Files view (MDS) | H3: Deleted Documents view | H3: Current Files with Exceptions | H3: Current files with exceptions view | H3: All Files with Exceptions | H3: All files with exceptions view | H2: Details modal | H2: Retrying delete exceptions | H2: Republishing files from the Files tab | H3: Republishing files where job errors are present | H3: Common use cases for using the Republish mass action | H2: Retrying exceptions | H2: Saved filters | H2: Saved filters (MDS) | H3: Right-click options | H2: Single Download / Replace | H2: Mass download and replacement of errored files | H3: Mass download of errored files | H3: Mass replacement of errored files - [Frequently asked questions] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_FAQs.htm): Common questions about Relativity processing. - Second paragraph: The processing engine captures all the dates of calendar items. If there is not a field for it in Relativity, this data will end up in the "OtherProps" field. - Headings: H1: Frequently asked questions | H2: Date and time | H2: DeNIST | H2: Discover | H2: Errors | H2: Media processing | H2: Other | H2: Password-protected files - [Inventory Overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Inventory.htm): Use Inventory to narrow down your files before discovering them by eliminating irrelevant raw data from the discovery process through a variety of preliminary filters. With inventory you can exclude certain file types, file locations, file sizes, NIST files, date ranges, and sender domains. - Second paragraph: This page provides an overview of the inventory process. For information on running an inventory job, applying filters, and managing inventory exceptions, see Inventory processing. - Headings: H1: Inventory overview | H2: Inventory process | H2: Monitoring inventory status | H3: Inventory job details | H2: Inventory filters | H2: Discovering files from Inventory - [Inventory processing] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/InventoryProcessing.htm): This page provides details on inventory processing, applying filters, and managing inventory errors. - Second paragraph: To inventory the files found in a processing set's data source(s), click Inventory Files on the processing set console. This option is only available if you have added at least one data source to the processing set. - Headings: H1: Inventory processing | H2: Running inventory | H3: Canceling inventory | H2: Filtering files | H3: Applying a Date range filter | H3: Applying a File Size filter | H3: Applying a deNIST filter | H3: Applying a Location filter | H3: Applying a File Type filter | H3: Applying a Sender Domain filter | H2: Removing filters | H2: Inventory errors | H3: Inventory error scenarios | H2: Re-inventory - [Mapping processing fields] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Mapping_processing_fields.htm): This topic provides a list of system-mapped fields, optional fields, source path, message id, comment, and deduplication considerations. - Second paragraph: System fields versus optional fields - Headings: H1: Mapping processing fields | H2: Mapping fields | H3: Relativity system field considerations | H3: Field mapping validations | H2: System-mapped fields | H2: Optional fields | H2: Email Store Name field | H2: Virtual path | H2: Processing folder path | H2: Email folder path | H2: Source path | H2: Message ID considerations | H2: Comments considerations | H2: De-duped custodian and path considerations - [Password bank] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Password_bank.htm): The Password Bank is a password repository used to decrypt certain password-protected files during inventory, discovery, and basic and native imaging. This topic describes workflows that use the password bank, validations and exceptions, and viewing audits. - Second paragraph: The following scenario depicts the basic procedure by which you would address exceptions due to password-protected files in a processing set. In this scenario, you would: - Headings: H1: Password bank | H2: Password bank in processing workflow | H2: Password Bank in imaging workflow | H2: Creating or deleting a Password Bank entry | H3: Fields | H3: Example password | H2: Validations and exceptions | H2: Viewing audits - [Post-publish delete] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Post-publish_delete.htm): This topic provides an overview of post-publish delete in processing, including running post-publish delete, and retrying delete errors. - Second paragraph: Use the Delete mass action on the Documents view to delete multiple files (after they have been discovered and published). To view a list of previously deleted files, navigate to the Files tab and open the Deleted Documents view. - Headings: H1: Post-publish delete | H2: Overview | H2: Post-publish delete and duplicate documents | H2: Running post-publish delete | H2: Interacting with deleted documents | H2: Retrying delete errors - [Processing] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_in_Relativity.htm): This topic gives an overview of Relativity processing including a basic workflow. - Second paragraph: Some of the primary goals of processing are to: - Headings: H1: Processing | H2: Basic processing workflow - [Processing duplication workflow] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_duplication_workflow.htm): The Processing Duplication Workflow is a way to identify and mark duplicate documents after discovery. This way you can review only one copy of each document, while leaving all copies of the document in place across the workspace. - Second paragraph: The scripts described on this page help identify duplicate files and their source locations. Use the scripts if you have deduplication set to No Deduplication or are working with files uploaded outside of Relativity. You should not use these scripts if you are running deduplication within Relativity processing. - Headings: H1: Processing duplication workflow | H2: Downloading and installing the solution to your instance | H3: Supported versions | H3: Components | H3: Considerations | H2: Deploying and configuring the solution | H2: Adding the solution to a workspace | H2: Before you run the scripts | H3: Fields | H3: Saved searches | H3: Other considerations | H2: Running the scripts | H3: All Custodians script | H3: All Source Locations script | H3: Update Duplicate Status script - [Processing history] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_history.htm): This topic describes the resources for viewing historical data on processing jobs. - Second paragraph: The Processing history tab displays a list of the latest activity for each data source within a processing set. This information provides an overview of the processing set configuration and then job activity, including file counts and sizes for preprocessed, discovered, and published files. - Headings: H1: Processing history | H2: Processing history tab | H3: Exporting the processing history list | H2: Audit tab | H3: Object type | H2: Dynamic numbering considerations - [Processing profiles] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_profiles.htm): A processing profile is an object that stores the numbering, deNIST, extraction, and deduplication settings that the processing engine refers to when publishing the documents in each data source that you attach to your processing set. - Second paragraph: Relativity provides a Default profile upon installation of processing. - Headings: H1: Processing profiles | H2: Creating or editing a processing profile | H3: Fields | H3: Inventory / Discover settings | H3: Extraction settings | H3: Short message conversion settings | H3: Deduplication settings | H3: Publish settings | H3: Other considerations - [Processing sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_sets.htm): A processing set is an object to which you attach a processing profile and at least one data source and then use as the basis for a processing job. - Second paragraph: Consider the following about processing sets: - Headings: H1: Processing sets | H2: Processing sets default view | H2: Creating a processing set | H2: Processing set fields | H2: Adding a data source | H2: Data source fields | H3: Data | H3: Custodian Options | H3: Advanced Options | H3: Order considerations | H3: Edit considerations for data sources | H3: Processing data source view | H3: Job Errors view | H2: Processing Data Sources tab | H2: Deleting a processing set | H3: Permissions | H2: Avoiding data loss across sets | H2: Copying natives during processing - [Processing throughput] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Throughput_factors.htm): This topic explains several factors that may affect processing throughput, or performance for processing discover and publish jobs. - Second paragraph: The following content discusses common factors that may affect discover job throughput. - Headings: H1: Factors that affect processing throughput | H2: Calculating processing discover throughput | H2: Discover job performance | H3: Factors related to the processing discover job | H3: Processing profile settings that may impact discover job performance | H2: Publishing job performance | H3: Factors related to the processing publish job | H3: Processing profile settings that may impact publish job performance - [Processing to Data Grid] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_to_Data_Grid.htm): This topic describes how to enable and process to data grid. - Second paragraph: After you install Data Grid, the only requirement for setting up your workspace to process to Data Grid is enabling both the workspace and the extracted text field in your environment. - Headings: H1: Processing to Data Grid | H2: Enabling processing to Data Grid - [Publishing files] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Publishing_files.htm): Publishing files to a workspace is the step that loads processed data into the environment so reviewers can access the files. At any point after file discovery is complete, you can publish the discovered files to a workspace. - Second paragraph: For details on deleting files after publishing, see Post-publish delete. - Headings: H1: Publishing files | H2: Running file publish | H3: Publish process | H2: Monitoring publish status | H3: Publish job details | H2: Canceling publishing | H2: Republishing a processing set | H2: Retrying exceptions after publish - [Quick-create set(s)] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Quick-create_set_s_.htm): With the quick-create set(s) feature, you can streamline the creation of data sources, custodians, and processing sets based on a specific file structure or PST from a single object. - Second paragraph: You can also create single or multiple processing sets based on the custodians and data sources and specify what action you want Relativity to take for each, such as starting inventory or discovery. - Headings: H1: Quick-create set(s) | H2: Required security permissions | H2: Using quick-create set(s) | H3: Validations and errors - [Reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_reports.htm): In the Reports tab, you can generate reports in Relativity to understand the progress and results of processing jobs. - Second paragraph: This topic contains several references to progressive filtration. For context, consider the following explanation: A count based on absolute filtration counts the total number of files each filter eliminates as if it were the only filter applied to the entire data set. A count based on progressive filtration counts the total number of files each filter actually eliminates by accounting for all previously applied filters. For example, a file type filter eliminates 3000 PDF files from a data set, but a previously applied date range filter also eliminated 5000 PDF files. A count based on absolute filtration would report the file type filter as eliminating 8000 PDF files because the count is based on the total number of files each filter eliminates as if it were the only filter applied to the entire data set. However, a count based on progressive filtration counts the total number of files each filter actually eliminates by accounting for all previously applied filters. In the previous example, a progressive filtration count only reports 3000 PDF files eliminated by the file type filter, because the other 5000 PDF documents were progressively eliminated by the date range filter. - Headings: H1: Reports | H2: Generating a processing report | H2: Data Migration | H2: Master Document Replacement Summary | H2: Discovery Exclusion Results | H2: Discovered Files by Custodian | H2: Discovered Files by File Type | H2: Document Exception | H2: File Size Summary | H2: Inventory Details | H2: Inventory Details by Custodian | H2: Inventory Exclusion Results | H2: Inventory Exclusion Results by Custodian | H2: Inventory Summary | H2: Job Exception | H2: Text Extraction - [Short message conversion for Cellebrite] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-Cellebrite.htm): This topic describes short message conversion for Cellebrite, including generated RSMF fields, troubleshooting, and known issues and limitation. - Second paragraph: Relativity supports short message conversion for Cellebrite in RelativityOne Government. - Headings: H1: Short message conversion for Cellebrite | H2: Recommended workflow | H2: Generated RSMF fields | H3: Email data extracted from Cellebrite | H3: Output format by data type | H2: Deduplication mechanism in Relativity Processing (UFDR-specific) | H2: Troubleshooting | H2: Known issues and limitations | H2: Resources - [Short message conversion for Google Chat] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-GoogleChat.htm): This topic describes short message conversion for Slack, including generated RSMF fields, processing org-level exports, troubleshooting, and known issues and limitation. - Second paragraph: Relativity Processing supports Google Chat exports from Google Vault. A Google Vault export for Google Chat produces two files: - Headings: H1: Short message conversion for Google Chat | H2: Required file structure | H2: Processing Google Chat conversations | H2: Generated RSMF fields | H2: Troubleshooting | H2: Known issues and limitations - [Short message conversion for Microsoft Teams] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-Teams.htm): This topic describes short message conversion for Microsoft Teams, including generated RSMF fields, troubleshooting, and known issues and limitation. - Second paragraph: Relativity supports short message conversion for Microsoft Teams in RelativityOne Government. - Headings: H1: Short message conversion for Microsoft Teams | H2: Metadata used to group Teams conversations | H2: Troubleshooting | H2: Known issues and limitations | H2: Resources - [Short message conversion for Slack] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-Slack.htm): This topic describes short message conversion for Slack, including generated RSMF fields, processing org-level exports, troubleshooting, and known issues and limitation. - Second paragraph: Relativity supports short message conversion for Slack in RelativityOne Government. - Headings: H1: Short message conversion for Slack | H2: Required file structure | H3: Understanding JSON files for Slack data exports | H2: Generated RSMF fields | H2: Processing organization-level exports | H2: Troubleshooting | H2: Known issues and limitations | H2: Resources - [Supported file types] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Supported_file_types_for_processing.htm): Relativity supports file types where the metadata and text can be extracted and processed for further review and publication. If the metadata or text cannot be extracted, the file type is not supported. - Second paragraph: You can find additional supported file type details and considerations on the following pages: - Headings: H1: Supported file types for processing | H2: Supported and unsupported file types for processing - [Supported file types - Google Workspace] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-Google.htm): This topic describes processing considerations for Google Workspace, Google Vault, using Collect, and metadata fields. - Second paragraph: When you gather Google Workspace data directly using Google Vault (Vault) or indirectly using Relativity Collect (Collect), the collection export includes zipped Google Gmail (Gmail) or Google Drive (Drive) data, along with supplemental metadata files. - Headings: H1: Google Workspace | H2: Collect | H2: Google Vault | H3: Other considerations | H2: Google Workspace metadata field lists - [Supported file types - Microsoft] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-Microsoft.htm): This topic covers additional supported file type (for processing) information for Microsoft. - Second paragraph: The following table provides details on the differences between how Relativity handles .msg and .mht file types. This information may be especially useful if you plan on setting the Email Output field on the processing profile to MIME encapsulation. - Headings: H1: Microsoft | H2: Outlook message item (.msg) to MIME encapsulation (.mht) conversion | H3: Email image extraction support | H3: Microsoft Office child extraction support | H2: Excel files - [Supported file types - other software support] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/SupportedFileTypes-Other.htm): This topic covers additional supported file type (for processing) information for other software considerations. - Second paragraph: When processing a forensic image with multi-part extents, be sure to include all parts within the same directory. Not doing so will cause inventory and discovery to fail. - Headings: H1: Other software support | H2: Multi-part forensic file considerations | H2: Password-protected .rar files | H3: Lotus Notes | H2: Multi-part container considerations | H2: Calendar file, vCard file considerations - [Using EDRM MIH to identify duplicates in emails] (https://help.relativity.com/RelativityOne/Content/Relativity/Processing/Processing_duplication_workflow_EDRM.htm): This topic describes how to use EDRM MIH to identify duplicates in emails. - Second paragraph: How the hash is generated: - Headings: H1: Using EDRM MIH to identify duplicates in emails | H2: How to use EDRM MIH in Relativity | H3: Fields and saved search | H3: Viewing EDRM MIH results | H2: How to map the EDRM MIH field from a load file | H2: How to export the EDRM MIH values | H2: Limitations ### Production - [Advanced formatting for branding] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Advanced_Formatting_for_Branding.htm): Advanced Formatting is a type of branding available on the Production Set form. With Advanced Formatting, you can brand headers and footers with a combination of fields from the Advanced Formatting drop-down list, free-form text, and carriage returns. - Second paragraph: With Advanced Formatting, you can brand headers and footers with a combination of fields from the Advanced Formatting drop-down list, free-form text, and carriage returns. The Advanced Formatting option also supports a scripting language that you can use to create conditional branding based on production, document, and page fields. - Headings: H1: Advanced Formatting for Branding | H2: Production object | H3: Example of Advanced Formatting with the production object | H2: Document object | H3: Example of Advanced Formatting with the document object | H2: Page object | H3: Example of Advanced Formatting with the page object | H2: Script examples - [Branding queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Branding_queue.htm): The Branding Queue displays production jobs receiving branding of redactions, header, footer, or other modifications. A production job displays in this queue only while it has a status of branding. The production job remains in the production queue until all branding is complete. - Second paragraph: You can view the branding queue from Home. Select the Queue Management tab, and then click Branding Queue. See Branding queue fields for details. - Headings: H1: Branding queue | H2: Branding queue fields - [Placeholders] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_placeholders.htm): You can create your own unique placeholders for productions using images or custom text. Once you create the placeholders, you can attach the placeholders to the production data source. You can also produce the same document in multiple productions with different placeholders. The Production Placeholder library automatically includes a default image placeholder. If you need to attach a placeholder to a production data source, see Production Data Source. - Second paragraph: When creating a template workspace using production, Relativity automatically copies Placeholders. - Headings: H1: Placeholders | H2: Creating an image placeholder | H2: Creating a custom placeholder | H2: Creating a PDF placeholder | H2: Previewing placeholders - [Production] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_overview.htm): Production is an application that allows you to prepare relevant and non-privileged documents to turn over to opposing counsel after review. Relativity - Second paragraph: For more information about working with productions, see the following pages: - Headings: H1: Production | H2: Security permissions to run productions | H2: Upgrading production | H2: Basic production workflow | H2: Production information | H3: Production information tab - [Production data source] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_data_source.htm): The production data source attaches saved searches to your production set. With the production data source you can specify the type of production and select placeholders from your placeholder library to customize your production. By setting the placeholder on the data source you can include multiple placeholders within a single production. The placeholder is based on the saved search attached to the production data source. - Second paragraph: You must have view, add, and edit permissions for the Production Data Source object in order to successfully create a data set. We also recommend the delete permission. - Headings: H1: Production data source | H2: Adding a production data source - [Production errors] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_errors.htm): When staging and running a production job, staging, validation, and branding errors can occur. - Second paragraph: Staging errors occur when: - Headings: H1: Production errors | H2: Staging errors | H2: Validation errors | H2: Branding errors | H3: Post Production errors - [Production queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_queue.htm): The Production Queue tab displays all current production jobs running in your environment, and any jobs in error status. A job remains in this queue until the completion of branding and other processing. - Second paragraph: You can view the production queue from Home. Select the Queue Management tab, and then click Production Queue. - Headings: H1: Production queue | H2: Change job priority | H2: Retry Production Job mass operation | H3: Security Configuration | H3: Retrying production jobs | H2: Cancel Production Job mass operation | H3: Security Configuration | H3: Canceling multiple production jobs | H2: Production queue fields - [Production sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_sets.htm): When you want to produce documents in a case workspace, you can create a production set that defines the markup set for redactions, the document numbering, the appearance of the numbering, and other settings that Relativity uses when you run the production. Post production workflow details are found in this topic. - Second paragraph: You can then view the produced images in the Review Interface by selecting Production mode and the production set. - Headings: H1: Production sets | H2: Post production | H2: Creating and editing a production set | H2: Basic Settings | H2: Numbering | H2: Branding | H2: Sorting | H3: Sort order limitations | H2: Post Production | H3: Rerun Post Production | H2: Other | H2: Viewing production set details | H3: Production set details options | H3: Previewing a production | H2: Tracking multiple redaction sets - [Re-production] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Re-production.htm): You can use the Re-produce mass operation to re-produce select documents from a produced production without having to run the whole production again. For each production that is modified, Relativity creates a new production job, which is a re-production job. Re-production jobs store the modified documents and reuse the numbering format, bates numbers, and branding options from the original productions. - Second paragraph: Once a re-production job finishes running, the modified documents merge into the existing, original production set; they overwrite the documents that were previously produced. The previously produced version of the document will no longer display in the Viewer and will not be available for export. - Headings: H1: Re-production | H2: Special considerations | H2: Security configuration | H2: Re-production types | H3: Replace produced images with placeholder (I-P) | H3: Replace placeholder with images (P-I) | H3: Re-produce documents (same number of pages) (I-I) | H2: Re-production scenarios | H2: Re-produce documents | H2: Re-production job status | H2: Re-production views ### Production console - [Check for production conflicts] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_console/Check_for_production_conflicts.htm): You can perform a conflict check that compares the documents in the production against those in a saved search selected in the Production Restrictions field on the workspace details page. For example, the saved search may include conditions that identify privileged documents and their families, which you would not want to produce. - Second paragraph: You must have permissions to the documents included in a production to remove production restrictions. - Headings: H1: Check for production conflicts - [Production console] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_console/Production_console.htm): You can use the production console to preview your production documents, review branding errors if any, stage your production to populate the production information object, and run the production. The production console also contains a progress bar which seamlessly updates the production statuses. - Second paragraph: To access the production console, click the name of the desired production set. - Headings: H1: Production console | H2: Manage Production | H2: Run Production | H2: Post Production | H2: Advanced Options - [Run a production] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_console/Run_a_production.htm): To run a production, click Run Production in the production console. After you click Run Production, the status bar updates as the documents produce. - Second paragraph: In the viewer, you can view the produced images by selecting the Production mode. You can view the images exactly as they were produced. - Headings: H1: Run a production | H2: Checking production status | H3: Production Summary fields | H3: Branding Summary fields | H3: Post Production Summary fields - [Stage a production] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_console/Stage_a_production.htm): Before you can run a production, you must stage the production. Staging the production takes a snapshot of the data sources to prepare documents. After you assign your data sources, placeholders, and production set, you can stage your production. - Second paragraph: To stage a production, click Stage in the Production console. You can also stage and run a production job in a single step by clicking Stage and Run Production on the Production console. For more information, see Stage and run a production. - Headings: H1: Stage a production | H2: Stage a production | H2: Staging Summary fields | H2: Staging errors - [Stage and run a production] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_console/Stage_and_run_a_production.htm): To stage and run a production in a single step, click Stage and Run Production on the Production console. - Second paragraph: A stage and run production job goes through 4 steps: - Headings: H1: Stage and run a production | H2: Staging and running a production | H3: Staging | H3: Validation | H3: Production | H3: Branding | H3: Post Production | H2: Checking production status | H3: Staging Summary fields | H3: Production Summary fields | H3: Branding Summary fields | H3: Post Production Summary fields - [View documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Production/Production_console/View_documents.htm): You can view the total number of image and native files to produce and other specific information about each document included in the production by clicking the View Documents button in the Production console. - Second paragraph: The View Documents window displays the following fields for each production document: Document Identifier, Data Source Name, Production Option, Begin Bates, End Bates, Has Native, Has Images, and Has Redactions. This information is also viewable from the Production Information object. - Headings: H1: View documents ### Purview Sync - [Configure Purview Sync] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Configure.htm): After registering Purview Sync with Microsoft Azure AD, you need to configure and integrate Microsoft with Relativity. - Second paragraph: Before starting, you will need the following access in Microsoft 365: - Headings: H1: Configure Purview Sync | H2: Prerequisites | H2: Configuring Purview Sync | H2: Testing the application - [Data transformation] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Data_transformation.htm): Purview Sync automatically transforms Microsoft Purview exports into formats optimized for Relativity, removing the need for manual preparation or conversion. - Second paragraph: The application retrieves data directly through the Microsoft Graph API and processes it into review-ready formats such as Relativity Short Message Format (RSMF) for Teams conversations and HTML for other supported content types. - Headings: H1: Data transformation | H2: Processing | H2: Processing custodians | H2: Automatic overlay and using Microsoft fields | H2: Relativity Short Messaging File conversion - [Importing data] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Import.htm): To import data from Microsoft to RelativityOne using Purview Sync, you will need to have the application installed and configured properly. For more information, see Install Purview Sync. - Second paragraph: Complete the following before importing data: - Headings: H1: Importing data | H2: Prerequisites | H2: Considerations | H2: Importing | H3: Import fields | H3: Processing fields | H2: Imports list | H2: Import details | H2: Cancel and retry job - [Install Purview Sync] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Install.htm): Follow the prerequisites and procedure to install the Purview Sync application in Relativity. - Second paragraph: Before installing the application, note the following prerequisites: - Headings: H1: Install Purview Sync | H2: Prerequisites | H2: Installing the app - [Purview Sync] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Purview_Sync.htm): Purview Sync is used collect custodian data in Microsoft 365 directly from Microsoft Purview Premium to RelativityOne. - Second paragraph: This includes the following Microsoft 365 data: - Headings: H1: Purview Sync | H2: Prerequisites | H3: Licensing requirements | H3: Permissions | H2: Supported data formats | H2: Choosing to use Purview Sync or Collect | H3: Delegated and application permissions | H3: Inactive and archived mailboxes | H3: Teams data - [Purview Sync Application registration issues troubleshooting] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Registration_troubleshooting.htm): In this topic, you can find solutions to common issues when registering the Purview Sync application with Microsoft. - Second paragraph: Click on any of the scenarios to see the cause of the issue and the resolution. - Headings: H1: Purview Sync Application registration issues troubleshooting | H2: Common issues | H2: Considerations - [Purview Sync frequently asked questions] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/FAQ.htm): This topic covers commonly questioned items within the Purview Sync application. - Second paragraph: Following access is needed in Microsoft 365: - Headings: H1: Purview Sync frequently asked questions - [Register Purview Sync with Azure] (https://help.relativity.com/RelativityOne/Content/Relativity/Purview_Sync/Register.htm): Purview Sync uses the Microsoft Graph API. For more information on Microsoft Graph API, see Microsoft's documentation. - Second paragraph: To access the API, you must register an application in Azure Active Directory. Authentication requires referencing a dedicated Azure AD application that has the necessary permissions. This configuration must be performed on the client side by an Azure user with sufficient administrative rights. - Headings: H1: Register Purview Sync with Azure | H2: Automating Purview Sync registration in Azure Active Directory with a script | H3: Requirements | H3: Automating the registration | H2: Registering an Azure application and credentials manually | H3: Authentication | H3: Creating a client secret | H3: Setting API permissions | H3: Create the service principal | H2: Grant users eDiscovery permissions in Microsoft Purview | H3: Considerations | H3: Permissions for the admin configuring access | H3: Setting up Compliance Admin roles | H3: Permissions for Purview Sync users | H3: Grant Purview Sync users access (broader) ### RDO - [Building Media Tracker with Relativity Dynamic Objects] (https://help.relativity.com/RelativityOne/Content/Managing_Relativity_dynamic_objects/RDO/Building_Media_Tracker_with_RDOs.htm): Media Tracker is an application you can build using Relativity Dynamic Objects (RDOs). With Media Tracker, you can track media received from vendors, clients, and opposing counsel. After you build and deploy the application in a workspace, you can manually input the media and related metadata. - Second paragraph: Complete the following steps to create a Media Tracker application and then import it into Relativity workspaces. - Headings: H1: Building Media Tracker with Relativity Dynamic Objects | H2: Create a new application | H2: Link and create object types | H2: Update and create fields | H2: Update views | H2: Build layouts | H2: Export Media Tracker application - [Creating a question object] (https://help.relativity.com/RelativityOne/Content/Managing_Relativity_dynamic_objects/RDO/Creating_a_question_object.htm): Custodians can have multiple documents linked to them, but documents can have only one custodian. This is a one-to-many relationship – many documents to one custodian. - Second paragraph: A reviewer may have one or many questions about a document, and each question may be associated with one or many documents. This is a many-to-many relationship: many documents to many questions. - Headings: H1: Creating a question object | H2: Creating the Question object type | H2: Editing field and layout views | H3: Editing the Fields view | H3: Editing the Layouts view | H3: Filtering to view Question types | H2: Creating the Question object fields | H3: Creating the Question field | H3: Creating the Answer field | H3: Creating a multiple object field | H2: Writing questions and modifying the Question tab | H3: Adding new questions | H3: Adding an Answer to the Question detail page | H3: Adding the Documents list to the Question detail page | H3: Adding Answers to the Question tab | H2: Adding questions to a layout in the viewer | H2: Setting up Question-related views | H3: Creating a Document view for documents with questions | H3: Creating a Document view for documents with no questions | H2: Linking questions to a document during review - [Creating a tab to bookmark an object] (https://help.relativity.com/RelativityOne/Content/Managing_Relativity_dynamic_objects/RDO/Creating_a_tab_to_bookmark_an_object.htm): You can create new a tab that links you directly to any web page or a location within Relativity. This is useful for bypassing list views or for going to specific locations. In both cases, it potentially saves navigation steps. - Second paragraph: If the target is a Relativity page or object, you need the ArtifactID. - Headings: H1: Creating a tab to bookmark an object | H2: Finding the ArtifactID | H2: Creating the tab - [Creating and editing Relativity Objects] (https://help.relativity.com/RelativityOne/Content/Managing_Relativity_dynamic_objects/RDO/Creating_and_editing_Relativity_Objects.htm): RDOs are object types that you create and manage from within any Relativity application. They help process and organize data. For example, you can assign information to them and create new data structures. You can also attach external applications such as event handlers and rules to extend their functionality. - Second paragraph: To create an object from a workspace: - Headings: H1: Creating and editing Relativity Objects | H2: Creating an object from a workspace | H2: Creating an object from home | H2: Deleting an object from a workspace | H2: Deleting an object from home | H2: Editing an object's details | H2: Fields for an object type | H3: Object Type Information section | H3: Object Type Settings section | H3: Other section | H2: Adding an event handler | H3: Deleting an event handler | H2: Adding an object rule | H3: Default Layout | H3: Custom Single Object Add Link Visibility | H3: Default Layout on New | H3: Global Button Visibility | H3: Mass Action Visibility | H3: Choice Behavior | H3: Sub-List Button Visibility | H3: New Button Override | H3: Override edit link URL | H3: Override view link URL | H2: Adding a custom mass operation | H3: Mass operation fields | H2: Adding information to objects - [Deleting object dependencies] (https://help.relativity.com/RelativityOne/Content/Managing_Relativity_dynamic_objects/RDO/Deleting_object_dependencies.htm): Deleting object dependencies removes that object - Second paragraph: You also need to have the correct level of permissions. See your system admin for additional details. With the Delete Object Dependencies permission, you can force delete the current object, which includes deleting its children and unlinking associative objects. - Headings: H1: Deleting object dependencies | H2: Force deleting object dependencies | H2: Displaying and interpreting the dependencies report | H2: Considering the fields of force deleted objects | H3: Analytics categorization set example | H3: Search terms reports example - [Relativity Objects] (https://help.relativity.com/RelativityOne/Content/Managing_Relativity_dynamic_objects/RDO/Relativity_objects.htm): Relativity contains two kinds of objects. System objects, and Relativity Dynamic Objects (RDOs), also called dynamic objects. Both kinds, collectively called objects, are the building blocks Relativity applications. Objects connect together, whether implicitly resulting from a workflow, or explicitly by you defining the connections. Through these connections or links, you extend functionality by storing data and making efficient use of its organization. You can attach many kinds of objects to additional features or functionality, such as object rules and event handlers. This allows Relativity, third party, or in-house developers to introduce custom features specific to your needs. - Second paragraph: As an example of using objects to extend data reach, from within a workspace, you can create your own RDO for storing custodian information, including not only custodian names but also their emails, sent and received dates, and recipients. This information can then link to other documents or for greater granularity in sorting, searching, or listing those documents. - Headings: H1: Relativity Objects | H2: System objects | H2: Relativity Dynamic Objects (RDOs) | H2: Programmatically using Relativity objects and RDOs ### Redirects - [Premier Success Program (PSP)] (https://help.relativity.com/RelativityOne/Content/Resources/Redirects/PSP.htm): Information about Relativity's Premier Success Program is located at https://help.relativity.com/PSP. Click here if you are not automatically redirected. - Headings: H1: Premier Success Program (PSP) - [Premier Success Program (PSP) for Government] (https://help.relativity.com/RelativityOne/Content/Resources/Redirects/PSPGov.htm): Information about Relativity's Premier Success Program for Government is located at https://help.relativity.com/PSPGovernment. Click here if you are not automatically redirected. - Headings: H1: Premier Success Program (PSP) for Government | H2: PSPGov - [Third Party Licensing] (https://help.relativity.com/RelativityOne/Content/Resources/Redirects/TPL.htm): Information about third party licensing in Relativity is located at https://help.relativity.com/third_party_licensing. Click here if you are not automatically redirected. - Headings: H1: Third Party Licensing - [Trials] (https://help.relativity.com/RelativityOne/Content/Resources/Redirects/Trials.htm): Information about trials in Relativity is located at https://help.relativity.com/Trials. Click here if you are not automatically redirected. - Headings: H1: Trials | H2: Beta Trials Evaluation Advanced Access ### Regular expressions - [Searching with regular expressions] (https://help.relativity.com/RelativityOne/Content/Relativity/Regular_expressions/Searching_with_regular_expressions.htm): A regular expression is a form of advanced searching that looks for specific patterns, as opposed to certain terms and phrases. With RegEx you can use pattern matching to search for particular strings of characters rather than constructing multiple, literal search queries. - Second paragraph: Regular expressions uses metacharacters in conjunction with a search engine to retrieve specific patterns. Metacharacters are the building blocks of regular expressions. For example, “\d” in a regular expression is a metacharacter that represents a digit character. “d” stands for the literal character, “d.” You can use regular expressions to search for social security numbers, patent numbers, URLs, email addresses, Bates numbers, and other strings that follow a specific pattern. - Headings: H1: Searching with regular expressions (regex) | H2: Use cases for regular expressions | H2: Regular expression metacharacters | H3: Regular expression quantifiers | H3: Escaping regular expression metacharacters | H2: Additional resources - [Using regular expressions with dtSearch] (https://help.relativity.com/RelativityOne/Content/Relativity/Regular_expressions/Using_regular_expressions_with_dtSearch.htm): You can use regular expression with your dtSearch index to search for things like Bates numbers, zip codes, and phone numbers. You can use regular expression in conjunction with proximity, stemming, and fuzzy searching in dtSearch. - Second paragraph: For more information about constructing regular expressions, see the following pages: - Headings: H1: Using regular expressions with dtSearch | H2: Regular expression search strings | H2: Regular expression metacharacters | H3: View regular expression metacharacters examples | H2: Regular expression groups | H2: Escaping regular expression metacharacters | H3: Regular expression caveats in dtSearch | H2: Common dtSearch regular expression examples ### Relativity - [AI Help Chatbot] (https://help.relativity.com/RelativityOne/Content/Relativity/AI_Help.htm): Configuring and using the AI Help Chatbot - Second paragraph: Users with the appropriate level of access can open the chatbot by clicking the Ask AI button on the upper right corner of the screen. - Headings: H1: AI Help Chatbot | H2: Accessing and using the chatbot | H2: Access Control | H2: Writing effective prompts | H3: Be specific | H3: Use clear language | H3: Include context | H3: Ask one question at a time | H3: Utilize Relativity terminology | H3: Prompt examples | H2: Frequently-Asked Questions - [Automated workflows] (https://help.relativity.com/RelativityOne/Content/Relativity/Automated_Workflows.htm): Automated Workflows is a Relativity application that lets users automate tasks in workspaces that previously required manual actions to complete. With automated workflows, users specify a trigger that determines the conditions under which the automation begins as well as whether to run the automation automatically or manually. - Second paragraph: Rather than the Automated Workflows application performing the specific task(s), it will send a message to the action you specified and the appropriate application will do the task on behalf of the user. With automated workflows, you can setup automation to reduce and even eliminate the need for users to complete actions in Relativity that previously required manual work. This saves you time and enables users to focus on other important tasks within your business. Additionally, once a workflow has been created, you can copy it to workspaces as needed without having to recreate it from scratch. - Headings: H1: Automated Workflows | H2: Automated workflow permissions | H2: Automated workflow overview | H2: Installation and workspace templates | H3: Application Library installation | H3: Workspace templates | H3: Cold Storage and Recycle Bin | H3: Automated Workflow thresholds | H2: Creating a new workflow | H2: Editing an existing workflow | H2: Workflow Sync | H3: Copying a workflow to workspaces | H3: Sync a workflow to workspaces | H2: Triggers | H2: Actions | H2: Canceling a workflow | H2: Automated workflow status | H3: Workflow Notification Settings | H3: Viewing audit information | H2: Error handling and troubleshooting | H3: Failure saving an automated workflow | H3: Action resulting in Completed with Errors | H3: Action resulting in Failed - [Choices] (https://help.relativity.com/RelativityOne/Content/Relativity/Choices.htm): Choices are the predetermined values that you apply to single and multiple choice list fields. With the necessary permissions, you can create choices for workspace fields and admin fields. - Second paragraph: In a workspace, you use choices in coding fields to allow users to record decisions on a document. For example, a Responsiveness field might have choices like Responsive, Not Responsive, and Not Sure. You can add and edit workspace choices directly within Field forms and the Choices tab. Within the Field forms, any saved single or multiple choice field contains the choice editor, so you can create and manage choices directly within the field. Within, the Choices tab you may also add single or multiple choices, reorder choices, and create parent and child choices. - Headings: H1: Choices | H2: Accessing the Choice editor | H2: Permission considerations for the Choice editor | H2: Adding choices | H2: Editing choices | H2: Choice detail fields | H2: Deleting choices | H2: Performing mass operations on choices | H2: Organizing choices | H2: Fields in workspaces | H2: Admin choices | H3: Admin fields - [Clients] (https://help.relativity.com/RelativityOne/Content/Relativity/Clients.htm): Clients are companies or organizations. In Relativity, link clients with associated users, matters, groups, and workspaces. - Second paragraph: This page contains the following sections: - Headings: H1: Clients | H2: Creating or editing a client | H3: Fields | H2: Enabling client domains on a client - [Color Map] (https://help.relativity.com/RelativityOne/Content/Relativity/Color_Map.htm): Relativity system administrators can update the colors that are assigned to specific choices from the Color Map tab. You can edit the highlight colors for aiR for Review Analysis, fact colors in Case Dynamics, the colors in pivot charts, and the colors mapped to choices in email thread visualization. - Second paragraph: To learn more about these features, see the following related pages: - Headings: H1: Color Map | H2: Changing the assigned color for a choice | H2: Highlight colors in aiR for Review Analysis - [Creating commonly-used dashboards] (https://help.relativity.com/RelativityOne/Content/Relativity/Creating_commonly-used_dashboards.htm): This recipe includes information on creating 12 different dashboards and the widgets saved on each dashboard. - Second paragraph: With these dashboards, you and your case team will be better equipped to explore and prioritize your review, identify patterns and trends across custodians, and develop better review strategies with real-time insight. - Headings: H1: Commonly-used dashboards | H2: Communicators | H2: Data Load QC | H2: Database Stats | H2: Document Characteristics | H2: Review Prioritization | H2: Review Progress/QC | H2: Privilege Review/QC | H2: Search Term Review | H2: Pre-Production QC | H2: Email Threading | H2: Language Identification | H2: Special considerations - [Customer-managed direct SQL access (CMDSA)] (https://help.relativity.com/RelativityOne/Content/Relativity/Direct_SQL_access.htm): In addition to querying and manipulating data through Relativity - Second paragraph: In addition to querying and manipulating data through Relativity's suite of APIs, administrators and developers can extend the Platform's power further by directly querying the SQL database. You can run Relativity Scripts in your RelativityOne instance, and you can also run SQL scripts in SQL Server Management Studio (SSMS) directly against your Relativity databases. You can use Direct SQL for situations requiring custom reports, Relativity scripts, or commands directly in SQL Server Management Studio against your RelativityOne database. - Headings: H1: Customer-managed direct SQL access (CMDSA) | H2: Accessing direct SQL | H2: Database or server access | H2: Client use databases | H2: SQL tenant admin operational overview | H2: Limitations - [Dashboards] (https://help.relativity.com/RelativityOne/Content/Relativity/Dashboards.htm): When you - Second paragraph: For a list of dashboards that provide an effective starting point for administrators to help review teams visualize their data set, see Creating commonly-used dashboards. - Headings: H1: Dashboards | H2: Creating a dashboard | H2: Adding widgets to a dashboard | H2: Saving changes to a dashboard | H2: Deleting a dashboard | H2: Renaming a dashboard | H2: Filtering a dashboard | H2: Exporting a dashboard - [Displaying family groups by building an indented view] (https://help.relativity.com/RelativityOne/Content/Relativity/Displaying_family_groups_in_a_view.htm): During review, it may be helpful to quickly see documents as they exist in their family groups. Building an indented view to organize documents by family can support this workflow. - Headings: H1: Displaying family groups in a view | H2: Creating the family group view - [Early Case Assessment in RelativityOne] (https://help.relativity.com/RelativityOne/Content/Relativity/ECAv2_Overview.htm): Most cases require sifting through large amounts of emails, documents, instant messages, and other data to filter content and uncover facts most pertinent to your case. Whether you are conducting a litigation review, investigation, 3rd party subpoena, or a data subject access request, RelativityOne’s Early Case Assessment (ECA) template provides you with a streamlined workflow to easily cull unwanted data and find unique information and insights. - Second paragraph: The ECA template can be useful in a variety of common use cases: - Headings: H1: Early Case Assessment in RelativityOne | H2: Set up the template workspace | H2: Narrow the scope of documents for further review | H2: Identify key people and information | H2: Promote documents to a new workspace for further review | H2: Record and track promoted documents - [Early Case Assessment Workspace Template] (https://help.relativity.com/RelativityOne/Content/Relativity/ECAv2_Template.htm): Early Case Assessment (ECA) involves identifying key facts to drive case strategy and cull documents for review in a separate workspace. The ECA workspace template simplifies and streamlines the process of early case assessment by putting the process on rails and removing unneeded content and capabilities. Additionally, the ECA workspace template already has the Repository Workspace application pre-installed, providing cost savings while limiting functionality to only what is required for early case assessment. - Second paragraph: From a global perspective, ECA begins with understanding the case and issues, identifying and interviewing key people involved, preserving collected documents and files, eliminating irrelevant documents, performing a cost and risk assessment, and finally, making recommendations for further steps. Further steps may include creating new policies or procedures to prevent behaviors identified in an investigation, settling with key parties in an employee dispute, or deciding whether to pursue litigation. In the image below, the colored blocks represent the steps performed using Relativity tools, while the white blocks represent steps and decisions outside of Relativity. - Headings: H1: Early Case Assessment Workspace Template | H2: Global overview of early case assessment | H2: Early case assessment template | H2: Set up the template workspace | H2: Narrow the scope of documents for further review | H2: Identify key people and information | H2: Promote documents to a new workspace for review | H2: Record and track promoted documents | H2: Workspace permissions | H3: ECA Users | H3: Administrator | H2: Change log - [Field categories] (https://help.relativity.com/RelativityOne/Content/Relativity/Field_categories.htm): Field categories allow you to quickly and accurately apply field conditions to the document list, a saved search, or a view. Once a field category has been created, it can be linked to as many fields as desired. The field category can then be selected when adding fields or conditions in the search panel, a view, or a saved search to conveniently access and apply the linked fields. To learn more, visit the Search panel. - Second paragraph: All Fields is a system default field category that displays every non-secured field in your workspace. It cannot be edited or secured from other users and it will always display at the bottom of the Field Categories drop-list. All Fields allows you to conveniently switch between viewing all of the fields and the fields included in a particular field category. - Headings: H1: Field categories | H2: Creating a field category | H2: Viewing fields associated with a field category | H2: Link a field or fields to a field category | H2: Unlink a field or fields from a field category - [Filters] (https://help.relativity.com/RelativityOne/Content/Relativity/Filters.htm): Filtering provides a fast and easy way to search for items in a list in Relativity. You can use filters to search for values in the fields on the active view, and across all records available in the searchable set. Filters are also available for item lists on tabs and pop-up windows. - Second paragraph: The field type associated with each column determines the available filter types, such as text boxes, pop-up pickers, and drop-down lists. You do not need any specific security permissions to use filtering. - Headings: H1: Filters | H2: Showing and hiding filters in the item list | H2: Filter types | H3: Using Boolean filters | H3: Using numeric filters for numbers | H3: Using List filters | H3: Using date filters | H3: Using multi-list filters | H3: Using text box filters | H3: Text box filter search examples | H3: Using advanced text box filtering | H2: Changing item sets per page | H2: Saving filters as a search - [GlobalProtect VPN client] (https://help.relativity.com/RelativityOne/Content/Relativity/GlobalProtect_VPN.htm): Your VPN enables a secure connection between your computer and resources on your Relativity instance - Second paragraph: For Sandbox environments, you can access the following back end resources via the VPN: - Headings: H1: GlobalProtect VPN client | H2: GlobalProtect VPN requirements | H3: Port requirements | H2: Current VPN portal URL | H2: Accepting the invitation from Microsoft Entra ID | H2: Downloading and installing the GlobalProtect VPN client | H2: Logging in using your GlobalProtect VPN client | H2: Changing your VPN password | H2: Adding an additional VPN region to GlobalProtect - [Groups] (https://help.relativity.com/RelativityOne/Content/Relativity/Groups.htm): With groups you can organize users in Relativity. A user can be a member of one or more groups. You can grant groups permission to view admin tabs from Home. You can also add groups to workspaces and set permissions per group on a workspace-by-workspace basis. - Second paragraph: Relativity workspaces include the following default system groups: - Headings: H1: Groups | H2: System groups | H2: Creating and editing groups | H2: Fields | H2: Adding users to groups | H2: Adding external users through groups | H2: Adding or removing groups from a client domain - [Importing and exporting] (https://help.relativity.com/RelativityOne/Content/Relativity/Importing_and_exporting.htm): Relativity provides several options for importing and exporting data designed to facilitate your needs. - Headings: H1: Importing and exporting - [Inline editing in the document list] (https://help.relativity.com/RelativityOne/Content/Relativity/Inline_editing.htm): Eligible fields can be edited from the Documents tab without needing to open and edit fields individually. Yes/No, single choice, multiple choice, single object, multiple object, date, and fixed-text fields are eligible for inline edits. To ensure that sensitive data is preserved, system, results, and processing source fields cannot be edited. - Second paragraph: The following permission is needed to use inline editing: - Headings: H1: Inline editing in the document list | H2: Permission | H2: Enabling inline editing in a view | H2: Editing fields with inline editing - [Instance Details tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Instance_details.htm): The Instance Details tab allows you to monitor some of the most basic information about your instance of Relativity. You can view, edit, and enable the Message of the Day (MotD), monitor all users within Relativity, check your license expiration date, view alerts and queue statuses, and view or edit group admin security settings. - Second paragraph: In the Security section, you can manage group permissions and generate a group permissions report. - Headings: H1: Instance Details tab | H2: Security | H3: Manage Permissions | H3: Group Permissions Report | H2: Message of the Day - [Investigations in RelativityOne] (https://help.relativity.com/RelativityOne/Content/Relativity/Investigations_in_RelativityOne.htm): Organizations often execute investigations by searching email, documents, instant messages, network drives, user share folders, logs, and other data sources in their native format or native application. RelativityOne enhances your investigation by expanding the standard set of tools used to find and analyze data and document findings. - Second paragraph: For videos and tutorials that cover the basics of Investigations in RelativityOne, see the Investigations Introduction learning path. - Headings: H1: Investigations in RelativityOne | H2: Search for Key Documents | H3: Search by term | H3: Visualize and document searches | H3: Search by document concepts | H3: Search by document attributes | H2: Review Communications | H2: Document Findings | H2: Tips - [Keyword search] (https://help.relativity.com/RelativityOne/Content/Relativity/Keyword_search.htm): Keyword search (or SQL index search) is Relativity - Second paragraph: New workspaces created in RelativityOne have extracted text automatically stored in Data Grid. Workspaces restored into RelativityOne using the ARM application will automatically have the extracted text migrated to Data Grid. In order to search extracted text in workspaces, you must use dtSearch or Analytics searching; you cannot use keyword search. - Headings: H1: Keyword search | H2: Fields | H2: Example keyword search strings | H2: Using the NOT operator in keyword searches | H2: Understanding noise words | H3: Keyword search noise words - without double quotes | H3: Keyword search noise words - with double quotes | H3: Single digits as noise words | H3: Punctuation as noise words | H3: At sign (@) and dashes | H3: Hyphens and dashes | H3: Default noise word list | H2: Running a keyword search | H3: Running a keyword search in the search panel | H3: Running a keyword search in the Search browser - [Lists] (https://help.relativity.com/RelativityOne/Content/Relativity/Lists.htm): Lists provide a simple way to save a list of objects, such as documents, without specifying the types of conditions you do for a saved search. Since lists aren - Second paragraph: Lists are especially useful when saving a list of sampled items. When using Sampling, you can save a random sample set of documents as a list in order to access the same sample set again later. See Sampling. When saving a list of documents, you can view the list later by creating a saved search with the list set as search criteria. The Lists console includes a command to automate the creation of a saved search from a list. - Headings: H1: Lists | H2: Enabling lists on an object | H2: Viewing items in a list | H3: Incorporating a list of documents as a search criterion in a saved search | H3: Creating a view from a saved list - [Log extractor] (https://help.relativity.com/RelativityOne/Content/Relativity/Log_Extractor.htm): In RelativityOne, you can use the log extractor to access logs for a custom application. You can view logs for a date range of seven days or less, which your custom application has generated in the last 21 days. The log extractor accesses the logs and displays them as JSON output on a new tab in your browser where you can view or download them. - Second paragraph: Follow good security practices when writing and retrieving logs to minimize data exposure: - Headings: H1: Log Extractor | H2: Data Logging Security | H2: Required permissions | H2: Creating a log request for a custom application | H3: Log lifespan | H3: Log Extractor changes following back-end log aggregator update | H2: Data Loss in Logs - [Markup sets] (https://help.relativity.com/RelativityOne/Content/Relativity/Markup_sets.htm): Markup sets are securable sets of redactions available to reviewers for applying text redactions to documents in the viewer. - Second paragraph: For example, if you want to mark certain redactions as Confidential and others as Private, you can create a markup set containing the words Confidential and Private and apply them to your document set without manually entering the words for each textbox redaction. - Headings: H1: Markup sets | H2: Permissions | H2: Creating and editing a markup set | H2: Fields | H2: Copying markup sets - [Matters] (https://help.relativity.com/RelativityOne/Content/Relativity/Matters.htm): Clients in Relativity are associated with one or more matters. Matters are used to define the different cases, disputes or advising that a firm may be involved with for a client. Within Relativity, a matter must be associated with an existing client. A matter can also be associated with one or more workspaces, but it - Second paragraph: To create or edit a matter, perform the following steps: - Headings: H1: Matters | H2: Creating or editing a matter | H2: Adding or removing matters from a client domain - [Printing in Relativity] (https://help.relativity.com/RelativityOne/Content/Relativity/Printing_in_Relativity.htm): Relativity includes a few options which you can employ when you need to print natives or images of documents in Relativity. These easily accessible features support printing a large group of documents or a single document at a time. - Second paragraph: Single Save as PDF is an option within the Viewer in Relativity. With this option you can save the native of the current open document as a PDF file. Once you save the PDF of the file, you can open the PDF and print it to your designated printing location. For more information, see Save as PDF. - Headings: H1: Printing in Relativity | H2: Save as PDF | H2: Mass PDF - [Queue Management] (https://help.relativity.com/RelativityOne/Content/Relativity/Queue_Management.htm): The Queue Management tab is the parent tab of the following queue sub-tabs. - Second paragraph: This topic is about the instance-level tab called Queue Management. For information about Review Center queues, see Review Center. - Headings: H1: Queue Management | H2: Permissions | H2: Branding queue | H2: dtSearch queue admin | H2: Import/Export queue | H2: Mass Operations Jobs | H2: OCR queue | H2: PDF queue | H2: Processing and imaging queue | H2: Production queue | H1: Queue management best practices | H2: Processing scaling and queue management | H1: Client domain resource management | H2: Client domain best practices | H3: Service providers - [RelativityOne data management] (https://help.relativity.com/RelativityOne/Content/Relativity/Data_Management.htm): Data management home - Second paragraph: Note the following data volume considerations for RelativityOne and RelativityOne Government: - Headings: H1: RelativityOne data management | H2: Data volume considerations | H3: Data retention | H3: Restoring Workspace Data | H2: Data management tools comparison | H2: Data management workflows in RelativityOne | H3: Repository to Review workflow | H3: Review to Cold Storage workflow | H3: Archive to cloud storage (staging area) workflow | H3: RelativityOne cloud storage to Repository or Review workflow | H3: Review to Repository Conversion workflow | H3: RelativityOne Repository to Cold Storage | H2: Resources - [RelativityOne repository workspace] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_document_repository.htm): When installed to an existing workspace, the RelativityOne repository workspace application converts the workspace into a more streamlined version for performing early case assessment on processed data. This limited workspace is equipped with Relativity functionality you need for early case assessment while providing more cost-effective pricing for storing data that may not be actively used in a case. - Second paragraph: You cannot use a repository workspace for review or production purposes. - Headings: H1: RelativityOne repository workspace | H2: Basic repository workspace usage workflow | H2: Best practices | H2: Repository workspace billing structure | H3: Billing for duplicates | H2: Creating a new repository workspace using the ECA Template | H2: Converting a review workspace to a repository workspace | H3: Converting a Repository workspace to a Review workspace | H2: Moving a repository workspace to Cold Storage | H2: Limitations on functionality in Repository workspaces | H2: Available tabs and operations - [RelativityOne Store] (https://help.relativity.com/RelativityOne/Content/Relativity/Store.htm): Relativity has deprecated RelativityOne Store. For information on other storage options, see RelativityOne data management. - Headings: H1: RelativityOne Store - [Reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Reports.htm): Several Relativity features offer reporting options for gauging the progress and results of a job. These reports provide data that helps you, for example, make adjustments to a document review project or determine if you need to run another instance of a job. - Second paragraph: The following features provide reporting options: - Headings: H1: Reports | H2: Batches | H2: dtSearch | H2: History | H2: Pivot | H2: Processing | H2: Analytics | H2: Review Center | H2: Search terms reports | H2: Structured Analytics - [Sampling] (https://help.relativity.com/RelativityOne/Content/Relativity/Sampling.htm): Relativity - Second paragraph: You can enable any object to use Relativity's sampling. By default, sampling is enabled on the Document object. - Headings: H1: Sampling | H2: Enabling sampling on an object | H2: Generating a sample | H3: Creating a fixed size sample set | H3: Creating a percentage sample set | H3: Creating a statistical sample set - [Script groups] (https://help.relativity.com/RelativityOne/Content/Relativity/Script_groups.htm): You can use script groups in Relativity to create a dashboard view into your scripting activities. Script groups are an extension of the Relativity script page that allow you to dynamically create script dashboards based on the category specified in the Relativity script XML. These dashboards provide you with a radio button list of all scripts, and they provide a centralized location to run your similar scripts. - Second paragraph: See Scripts for more information. - Headings: H1: Script groups | H2: Setting up a script group - [Scripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Scripts.htm): You can use Relativity scripts to create and execute flexible SQL-based scripts to customize and augment Relativity functionality. Scripts are Relativity artifacts. This means they have the same features as standard Relativity objects, allowing them to be secured and audited. - Second paragraph: Only users who are members of groups with the appropriate permissions can write scripts. System admins have permissions to preview, edit, and create scripts. See Security and permissions. - Headings: H1: Scripts | H2: Script compatibility and updates | H2: Creating a new library script | H2: Selecting an existing library script | H2: Creating a new workspace script | H2: Adding a library script to the script tab | H2: Running a library script - [Search terms report hit count] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_terms_report_hit_count.htm): This recipe describes how to calculate and store the number of terms in a Search Terms Report (STR) that hit on a document. You can then sort, filter and search for documents based on the number of STR hits, allowing you to prioritize review based on STR hit count or create searches that return documents having a minimum number of STR hits. - Headings: H1: Search terms report hit count | H1: Search terms report hit count - [Search terms reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_terms_reports.htm): Search terms reports provide the ability to identify documents containing specific keywords or terms that are important to a case. You can enter multiple terms and generate a report listing the number of hits for each term in a document. You can determine the output of the report by selecting one of the following type options. - Headings: H1: Search terms reports | H2: Search terms reports - [Staging Area] (https://help.relativity.com/RelativityOne/Content/Relativity/Staging_Area.htm): For more information on Staging Area folders, refer to the Staging Area FAQ article in Community. - Second paragraph: The Staging Area is a storage area where you can upload, manipulate, and organize your data before processing and importing it into RelativityOne. This area is separate from where your workspace data and RelativtyOne system data resides. The volume size of the Staging Area is based on your current RelativityOne subscription. It is used for: - Headings: H1: Staging Area | H2: Staging Area folders | H2: Billable | H2: Best Practices - [Summary reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Summary_reports.htm): Summary reports provide aggregate tallies of field values. Field types available for reporting are limited to the following. - Headings: H1: Summary reports - [Tabs] (https://help.relativity.com/RelativityOne/Content/Relativity/Tabs.htm): A workspace contains tabs that provide you with easy access to different Relativity features, including documents, search terms reports, views, and other default functionality. Relativity is a highly customizable platform. You can apply any template with a tabs arrangement that best serves your review needs. Some workspace templates also include custom tabs for specialized functionality. - Second paragraph: You can also apply any workspace template with a tabs arrangement that best serves your review needs. Some workspace templates also include custom tabs for specialized functionality. - Headings: H1: Tabs | H2: Creating and editing tabs | H2: Fields | H3: Tab Information | H3: Tab Location | H2: Nesting children tabs - [Users] (https://help.relativity.com/RelativityOne/Content/Relativity/Users.htm): Users are individuals who have access to the Relativity environment. You create users and add them to groups, which are then associated with workspaces. Users are also directly associated to clients. This diagram illustrates how clients, groups, and workspaces relate to users. - Second paragraph: - Headings: H1: Users | H2: User status | H2: Creating and editing a user | H2: Adding a user log-in type | H2: Fields | H2: Viewing user audit records | H2: Sending messages to users | H2: Bounce list removal | H2: Forcing users to log out | H2: Adding or removing users from a client domain | H2: Auto-disable users - [Utility Server (UVM)] (https://help.relativity.com/RelativityOne/Content/Relativity/Utility_Server.htm): The Utility Server is a virtual machine that can optionally be connected to your RelativityOne instance. It contains additional support tools to help you work with data in your RelativityOne staging area before editing and loading it into your RelativityOne instance. - Headings: H1: Utility Server (UVM) | H2: Utility Server access | H2: Connecting to your Utility Server | H2: Logging off or disconnecting Utility Server sessions | H2: Data, applications and storage capacity on the Utility Server - [Views] (https://help.relativity.com/RelativityOne/Content/Relativity/Views.htm): Views are customizable lists of items in Relativity. - Second paragraph: Views are effectively special saved queries that control three things: - Headings: H1: Views | H2: Workspace system views | H2: System views from Home | H2: Creating a view | H3: Creating a view with field categories | H3: Creating a view without field categories | H2: Information tab | H2: Other tab | H2: Fields tab | H2: Conditions tab | H2: Sort tab | H2: Editing view information | H3: Using the four-step wizard | H2: Basic Information | H2: Fields | H2: Conditions | H2: Sort | H2: Linking a dashboard to a view ### Relativity Connect - [Connect: Primary contact] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Relativity_Connect/Connect_-_primary_contact.htm): To enable Connect and connect two or more Relativity instances, each party's RelativityOne primary contact must complete a RelativityOne Connect Request form. This applies unless the two instances are owned by the same customer (or their global entity). - Second paragraph: To begin using RelativityOne Connect, the primary RelativityOne contact at your organization needs to navigate to the Community site. - Headings: H1: Connect: Primary contact | H2: Enabling RelativityOne Connect | H3: Finding instance names - [Connect: RelativityOne admin] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Relativity_Connect/Connect_-_Relativity_admin.htm): To connect users to multiple instances with their one set of login credentials, navigate to the Admin-level Users tab. Find the user that needs to be connected and select the user. - Second paragraph: Once the user is selected and their user information page is available, add a new Login Method. - Headings: H1: Connect: Relativity admin | H2: Connecting users to different instances - [Connect: User] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Relativity_Connect/Connect_-_user.htm): As a user, the links to the connected instances appear in the User drop-down menu. The available instance names are available in the Other Relativity Instances drop-down option. Hover over the Other Relativity Instances and click the name of any instance. - Second paragraph: By default, the connected instances in the Other Relativity Instances drop-down option are visible to all users. If you want to limit who can see the instances in the drop-down option, apply item-level security to the connected instance in the Federated Instances tab. For more information on individual item security, see Relativity object security. - Headings: H1: Connect: User | H2: Navigating between instances ### Relativity Legal Hold - [Adding custodian portal settings] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Adding_custodian_portal_settings.htm): On the Legal Hold Settings page, you can update the fields in the Custodian Portal. Define how the Custodian Portal will look and act to the custodian interacting with it. Add the URL, title, and a custom image to the portal. - Second paragraph: To update the Custodian Portal settings on the Legal Hold Settings page, follow the steps below: - Headings: H1: Adding custodian portal settings | H2: Custodian Portal settings fields - [Adding email settings] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Adding_email_settings.htm): To complete the Legal Hold Settings, you need to add the email settings. These settings provide the information so you can issue legal holds as well as send and receive communications from your legal hold instance. - Second paragraph: See these related pages: - Headings: H1: Adding email settings | H2: Email processor types and requirements | H3: Graph API email settings requirements | H3: Gmail settings requirements | H3: SMTP email settings requirements | H2: Adding Outgoing Email settings | H3: Outgoing email fields | H3: Validating outgoing email settings | H3: Testing the outgoing email settings | H2: Adding Incoming Email settings | H3: Incoming email fields | H3: Validating incoming email settings | H3: Testing your incoming email settings | H2: Troubleshooting email settings - [Adding general settings] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Adding_general_settings.htm): Update the fields in the General section of Legal Hold Settings. - Second paragraph: To update the General settings on the Legal Hold Settings page, follow the steps below: - Headings: H1: Adding general settings | H2: General settings fields | H2: Entity OneDrive URL field (Legacy) | H3: Setting up OneDrive - [Adding legal hold settings] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Legal_Hold_Settings.htm): Configuring general settings, preservation settings, and email settings. - Second paragraph: Use Integration Points to import custodians from an LDAP-enabled data source. See Integration Points. As Integration Points is only compatible with Relativity 9.1 and higher, we encourage users who rely on this functionality to upgrade to Relativity 9.1+ prior to upgrading to Legal Hold 4.2 and above. - Headings: H1: Adding legal hold settings - [Adding preservation hold settings] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Preservation_Hold_Settings.htm): The Hold Admin tab contains all Legal Hold configuration, Global Reminder settings, and custodian roles. - Second paragraph: Preservation Hold Settings must be configured before creating a preservation hold for a custodian. The Preservation Hold Settings page is used to add, edit, or remove preservation hold data sources from legal hold projects with Microsoft 365 data sources. - Headings: H1: Adding preservation hold settings using Modern Authentication (Legacy) | H2: Background information | H2: Permissions | H2: Adding preservation hold settings | H3: Setup in Microsoft | H3: Run PowerShell Script to create a Service Principal | H3: Preservation Hold Settings configuration | H3: Validate preservation hold settings | H2: Deleting a preservation hold setting - [Attachments library] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Attachments_library.htm): The Libraries tab includes the Attachments libraries. - Second paragraph: Attachments are files that appear as links in the Custodian portal. For example, you may want to provide a supplemental document for a custodian to read before they acknowledge participation in a project. Attachments, unlike communications, aren't sent out to custodians. See Portal Content. - Headings: H1: Attachments library - [Azure AD for custodian portal SSO] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Azure_AD_For_Custodian_Portal_SSO.htm): To complete the set up of SSO authentication using the Azure AD provider, you need: - Second paragraph: For more information, see Custodian Portal Authentication Provider. - Headings: H1: Integrating Azure AD for Custodian Portal SSO | H2: Understanding Code flow and Implicit flow | H2: Registering an Azure application and credentials | H2: Creating a client secret | H2: Setting API Permissions | H2: Editing the custodian portal authentication provider | H3: Custodian portal authentication provider fields | H2: Configuring the redirect URL | H2: Enabling ID tokens for Azure application | H2: Troubleshooting Claims - [Azure AD for importing custodians] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Azure_AD_for_Importing_Custodians.htm): To import custodians into Relativity, you also need the following applications to be installed in your workspace: - Second paragraph: For more information, see Importing custodian data using Microsoft Entra ID. - Headings: H1: Integrating Azure AD for importing custodians | H2: Registering an application and credentials | H2: Creating a client secret | H2: Adding permissions | H2: Azure AD Provider setup and run - [Configuring SharePoint discovery for preservation] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Config_SharePoint_Discovery_for_Preservation.htm): Use the new Preservation in-place application for any new preservation holds. For more information, see Preservation in-place. - Second paragraph: This section explains how to configure SharePoint Discovery to use modern authentication via the CSOM API when executed from a RelativityOne Legal Hold project. This configuration will create an Enterprise application in Azure. - Headings: H1: Setting up SharePoint Discovery for preservation holds (Legacy) | H2: Configuring SharePoint Discovery | H2: Limitations of SharePoint Discovery - [Creating a communication] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Creating_communications.htm): Send hold notices, questionnaires, follow-up communications, or anything else you need to send to a custodian or group of specificed custodians regarding their involvement in the project or hold. - Second paragraph: Before creating a communication, you must add email settings. See the following: - Headings: H1: Creating a communication | H2: Requirements | H2: Create a communication | H2: Communication detail layout fields | H3: Detail tab | H3: Email tab | H3: Portal Content tab | H3: Reminder & Escalation tab | H3: Summary BCC tab | H3: Confirmation Messages | H2: Communication types | H3: General notice | H3: Alert group | H3: Email acknowledgement | H3: Release notice | H2: Using the editor window | H3: Hyperlinks | H3: Email merge fields | H3: Preview merge fields | H3: Email merge fields list - [Creating a report] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Creating_reports.htm): To run a report in Legal Hold, navigate to the Reports tab. - Second paragraph: Legal Hold reports are run with the permissions of the user running the report. - Headings: H1: Running a report - [Creating legal hold entities] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Creating_entities.htm): The Entity object functions as the central location for people, companies, organizational groups, and their metadata. Relativity Legal Hold, Processing, and Analytics all leverage the Entity object. - Second paragraph: If you would like to import entities, see the following topics: - Headings: H1: Creating legal hold entities | H2: Creating and editing an entity | H2: Legal Hold layout | H3: Basic Contact | H3: Company | H3: Location | H3: Other | H3: Custodian Interaction level | H2: Entity console - [Creating questionnaires] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Creating_questionnaires.htm): Use questionnaires to collect any information needed for the project. For example, an initial legal hold questionnaire might ask what kinds of hardware an individual uses at work, whether they work from home, how long they've been employed at the company, and any other questions. These kinds of questions assist the general counsel in managing a custodian's involvement in the project or compliance. - Second paragraph: To create a questionnaire: - Headings: H1: Creating a questionnaire | H2: Questionnaire fields | H2: Adding conditions | H2: Question types | H2: Question categories | H3: Creating a questionnaire - [Custodian communications tab] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Custodian_communications_tab.htm): Relativity Legal Hold customers want to work with custodian information in a more dynamic way when analyzing their legal holds. The Custodian Role and The Custodian Status tabs in Relativity store important information that ties custodians to projects and communications. The challenge with working in these two areas of Relativity Legal Hold is that the data presented can be voluminous and it can appear to be duplicated. For example, custodians are listed for every project they are on in the Custodian Role tab and for every communication they receive in the Custodian Status tab. - Second paragraph: The purpose of Relativity Legal Hold Custodian Information is to provide a method to manage and review the information on these tabs. The views provide customized ways to view the granular field data and the dashboards are used to group custodians, projects, communications, and other common fields that cannot be grouped using conditions or filters. The application can be unlocked and the dashboards and views can be further customized for your workflows. - Headings: H1: Custodian communications tab | H2: Views | H2: Dashboards - [Custodian portal] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Custodian_portal.htm): The Custodian portal is only accessible to custodians via a secure link in a communication sent from Legal Hold. In the portal, custodians can acknowledge their participation in a hold, answer questionnaires, view all of the active projects they - Second paragraph: After upgrading a workspace to Legal Hold 3.2+ from a previous version, run the Upgrade Old Legal Hold Portal Links script once in the Administration > Scripts sub-tab to upgrade the Portal links with the 3.2+ application. If you don't run this script, all former portal links sent prior to upgrade will not work. This script only applies to previous version upgrades to Legal Hold 3.2+. - Headings: H1: Custodian portal | H2: Custodian portal browser compatibility | H2: Accessing the Custodian Portal | H2: Customizing the Custodian Portal | H2: SSO for Custodian Portal | H2: Custodian console - [Custodian portal (admin)] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Portal.htm): As an admin, you must understand the requirements to display the Custodian Portal. This is especially important when importing legal hold data. For more information, see Importing hold data to RelativityOne. - Second paragraph: You must also understand what the custodian sees in the Custodian Portal. There are different states, or sections, in the portal. Each state must meet certain conditions for it to be visible to custodians. For more information, see Portal states. - Headings: H1: Custodian portal (admin) | H2: Portal states | H3: Active holds | H3: Tasks requiring attention | H3: Completed tasks - [Custodian Portal Authentication Provider] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Custodian_portal_authentication_provider.htm): The Custodian Portal Authentication Provider is a connection betweel Relativity Legal Hold and and an organization - Second paragraph: Legal Hold Portal SSO authentication only supports OpenID Connect protocol with Implicit Flow or Code Flow. SAML is not supported. For help connecting an authentication provider, contact Support. - Headings: H1: Custodian Portal Authentication Provider | H2: Considerations | H2: Enabling Custodian Portal SSO | H3: Authentication Provider fields | H3: Advanced fields | H3: Okta SSO setup | H2: Securing the custodian portal link - [Custodian projects tab] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Custodian_projects_tab.htm): In the Custodian Projects tab, you can work with custodian information in a more dynamic way when analyzing legal holds. - Second paragraph: The Custodian Projects tab in Relativity stores important information that ties custodians to projects. Working in this area of Legal Hold can create a challenge because data can be voluminous. It can appear to be duplicated. For example, custodians are listed for every project they are on in the Custodian Projects tab. - Headings: H1: Custodian Projects tab | H2: Views and dashboards | H3: Views | H3: Dashboards | H2: Mass operation - [Custodian status dashboard] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Custodian_status_dashboard.htm): Create custom custodian dashboards to view the status the custodians, the number of acknowledgements, and the overall health of your projects. - Second paragraph: Navigate to the Custodian status dashboard to manage custodian-based dashboards. Create and save dashboards for different views of Legal Hold projects. For more information, see Dashboards. Custodian status dashboards can help you easily identify: - Headings: H1: Custodian status dashboard - [Deleting a custodian] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Deleting_a_custodian.htm): You can delete individual entities, or multiple entities at once from Legal Hold, and any project to which they may be assigned. An entity cannot be deleted if they have communications redirected to them. For more information, see Custodian Interaction level - Second paragraph: To delete an entity: - Headings: H1: Deleting a custodian | H2: Deleting a custodian on a preservation hold - [Gmail API] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Gmail_API.htm): Connecting your Google Workspace to Legal Hold takes some setup in both Google and Relativity. Begin with the credential setup in Google. - Second paragraph: Consider the following when using the Google Mail API for hold communications: - Headings: H1: Gmail API | H2: Considerations | H2: Requirements | H3: Create a Google Cloud project | H3: Enable required APIs for the project | H3: Set up OAuth2 consent screen | H3: Create credentials | H2: Add email settings | H3: Outgoing email fields - [Graph API] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Graph_API.htm): Application permissions allow Relativity to send Legal Hold email communications as an application, without requiring any Microsoft user to sign in. - Second paragraph: This option is available for Commercial environments only and is intended for organizations that want an application‑based, non‑interactive configuration. Emails are sent from a configured mailbox, and no credential prompt is required during setup. A configured mailbox is the Microsoft 365 email address you entered in the Email From field. This mailbox sends the emails and receives replies. - Headings: H1: Microsoft Graph API - Application permissions | H2: Graph API | H2: Considerations | H2: Licenses | H2: Requirements | H3: Registering an Azure application and credentials | H3: Adding permissions | H3: Creating a client secret | H2: Adding email settings | H3: Outgoing email fields - [Graph API - Delegated permissions] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Graph_API_Delegated.htm): Delegated permissions allow Relativity to send Legal Hold email communications on behalf of a signed‑in Microsoft user. - Second paragraph: This option is used in Commercial and Government environments, including GCC High, where user‑based authentication is required. A licensed Microsoft user must authenticate during setup, and Relativity sends emails using that user’s mailbox. - Headings: H1: Microsoft Graph API - Delegated permissions | H2: Graph API | H2: Considerations | H2: Licenses | H2: Requirements | H3: Registering an Azure application and credentials | H3: Adding permissions | H3: Configuring the redirect URL | H3: Creating a client secret | H2: Authenticating with Microsoft | H3: Fields | H2: Adding email settings | H3: Outgoing email fields | H3: Incoming email fields - [Graph API for communications] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Graph_API_for_communications.htm): Relativity Legal Hold uses Microsoft Graph API to send email communications from your Microsoft tenant. Microsoft Graph API supports two permission models: - Second paragraph: Each permission type uses a different authentication model and has different tenant, licensing, and setup considerations. Understanding these differences helps you select the option that aligns with your organization’s environment and compliance requirements. - Headings: H1: Graph API for communications | H2: Permission types | H3: Application permissions | H3: Delegated permissions | H2: Comparisons | H3: Authentication and behavior | H3: Licensing and mailbox requirements | H2: Choose the correct permission type | H2: Outbound connectivity - [Import Purview cases] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Import_Purview_cases.htm): This document will describe how you can import Purview cases and hold policies that were created outside of Relativity into the Legal Hold and Preservation in-place application. - Second paragraph: Before you import Purview Cases from Purview to Legal Hold, you must complete the following tasks: - Headings: H1: Import Purview cases | H2: Prerequisites | H2: Identify Case ID and Hold ID from Purview | H2: Importing Objects into Relativity | H2: Considerations - [Importing custodians from Entra ID] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Azure_AD.htm): Integrating Azure with Legal Hold holds three purposes. Click the links for more information on each one. - Second paragraph: To walk through the entire technical setup process, see the Microsoft Entra ID technical setup quick reference guide. - Headings: H1: Integrating Azure with Legal Hold - [Importing entities - ImportExport] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Importing_entities_-_ImportExport.htm): You can add multiple legal hold custodians, or entities, by uploading a .csv or .dat file with Import/Export. - Second paragraph: To import custodians with Import/Export, create a load file that contains at least the following: - Headings: H1: Importing custodians with Import/Export | H2: Legal Hold custodian load file | H2: Importing legal hold custodians | H3: Choose the Load File Type | H3: Choose Load File and Location | H3: Load File Settings | H3: Load File Field Mappings | H3: Import Settings | H3: Import Summary - [Importing entities - integration points] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Importing_entities_-_Integration_points.htm): Importing data from Microsoft Entra ID and a .csv file is important to the legal hold process. - Second paragraph: For more information, see Integration Points. - Headings: H1: Importing entities with Integration Points | H2: Considerations | H2: Importing from Microsoft Entra ID | H3: Setup | H3: Connect to source | H3: Map fields | H3: Reporting on Microsoft Entra ID imports | H2: Importing a .csv file | H3: Setup | H3: Connect to source | H3: Map fields | H3: Importing custodians with managers | H2: Importing from LDAP | H3: Setup | H3: Connect to source | H3: Map fields - [Importing legal hold data to Relativity] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Importing_data_to_Relativity.htm): After installing Legal Hold, you can use the Relativity Desktop Client (RDC) to migrate hold information from a legacy system into Legal Hold. See Relativity Desktop Client. See the Relativity Desktop Client guide. - Second paragraph: For more information the load files you can import, see the following topics: - Headings: H1: Importing hold data to RelativityOne | H2: Considerations | H2: Prerequisites | H3: Load file types | H2: Importing the legacy data | H3: Load file order | H3: Import/Export | H2: Migrating with ARM | H2: Importing custodian data using Microsoft Entra ID - [Installing Relativity Legal Hold] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Installing_Legal_Hold.htm): To successfully use Relativity Legal Hold, you need to access, configure, and secure the workspaces. - Second paragraph: For more information on prerequisites, technical requirements, and other considerations, see the links below. - Headings: H1: Installing Legal Hold | H2: Installing Legal Hold | H3: RelativityOne Hold and Collect template | H3: Install Legal Hold from the Application Library | H2: Configuring Legal Hold | H2: Post-installation verification test - [Item selectors] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Item_selectors.htm): Legal Hold admins can modify the custodian pickers throughout Relativity Legal Hold from Item Selectors tab. Modifications to the pickers include re-ordering the fields, setting the size of the columns, adding and removing fields, and adding custom fields to include additional information. - Second paragraph: Relativity Legal Hold includes a fixed list of custodian pickers. Custodian pickers are the menus where you can select different custodians and put them in a select or unselected column. The pickers include Acknowledge on Behalf of Selected Custodians, Assign Custodians to Projects, Change Custodian Role, Escalate Select Custodians, Release Custodians from Project, Remind Select Custodians, Remove Custodians from Project, Send Communication. These pickers all map to a legal task or communications around custodians in legal hold. - Headings: H1: Item selectors - [Legal Hold project management] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Managing_projects.htm): Managing a legal hold project icnludes creating, reviewing, updating, and closing projects. - Second paragraph: Create a legal hold project in the Projects tab using the Project Wizard. Using the project wizard, you can create a new legal hold or project from scratch or from a template in six steps. - Headings: H1: Managing a legal hold project | H2: Creating a project | H3: Using the project wizard | H3: Project Details layout fields | H3: Assigning custodians to a project | H2: Securing a project | H2: Closing a project | H3: Closing a project with a preservation hold | H2: Deleting a project - [Mailbox] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Mailbox.htm): The Mailbox tab contains all information related to received communications in Legal Hold. - Second paragraph: The Mailbox also shows incoming messages so that you can track out of office notifications, bounce backs, custodian responses, and more. Use the column filters to sort information and click on an item to view its details. - Headings: H1: Mailbox | H2: Accessing the mailbox | H2: Using the mailbox | H2: Message statuses | H2: Requeue errored messages | H2: Responding to emails from Legal Hold | H2: Troubleshooting - [Optional load files] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Optional_load_files.htm): After importing the required load files, you do have the option to load other hold data. For example, task data and questionnaire data. For more information on importing legal hold data, see Importing the legacy data. - Second paragraph: Migrating data to Legal Hold should be performed by someone who is experienced with migrating structured data. If you do not possess this skill set, please reach out to a service provider or experienced colleague at your organization. For more information, see Optional load files. - Headings: H1: Optional load files | H2: Questionnaire load file | H3: Required fields | H3: Optional fields | H2: Questionnaire question load file | H3: Required fields | H3: Optional fields | H2: Questionnaire response answer load file | H3: Required fields | H3: Optional fields | H2: Questionnaire responses load file | H2: Task load files | H3: Required fields | H3: Optional fields - [Preservation hold] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Preservation_hold.htm): A Preservation Hold preserves files and emails in an custodian - Second paragraph: With the preserve-in-place feature, you can preserve Microsoft 365 data including Exchange mailboxes, OneDrive files, and Skype for business conversations. A preservation hold ensures that original copies, prior to any edits or deletions, of emails and files are preserved in a Microsoft 365 Preservation Library. The Preservation Library ensures that there is no loss of data through accidental or willful deletion or editing of items under a preservation hold. - Headings: H1: Preservation hold (Legacy) | H2: Permissions | H2: Prerequisites | H2: Licenses | H2: Considerations | H2: Adding a preservation hold to a project | H2: Adding a preservation case | H2: Deleting a preservation case | H2: Preservation hold status - [Projects] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Projects.htm): The Projects tab contains all information related to all Legal Hold projects. In this tab, you can create, review, update, and close projects. - Second paragraph: Watch the Legal Hold training video for more information. - Headings: H1: Projects | H2: Projects landing page | H3: Project dashboards | H3: Legal Hold layouts | H3: Project views | H2: Project Details | H3: Project console | H2: Project lock down - [Question library] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Question_library.htm): The Questions library contains all questions with the Save Question to Library option checked in any questionnaire. Add questions to this library when you're creating your questionnaire or directly from the Questions tab. See Creating a questionnaire. - Second paragraph: To create a question: - Headings: H1: Question library | H2: Creating a question from the Questions tab - [Question responses] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Question_responses.htm): All questionnaire responses appear in the Legal Hold tab > Question Responses sub-tab. Use the column filters to sort information and click on an item to view its details. - Second paragraph: In RelativityOne, you cannot edit questionnaire responses. Relativity keeps the original state of custodian responses. - Headings: H1: Question responses | H2: Using Relativity pivot to analyze question responses | H2: Updating responses - [Relativity Legal Hold] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Relativity_Legal_Hold.htm): Relativity Legal Hold - Second paragraph: Instead of sending ad hoc emails and manually tracking responses in spreadsheets to manage a legal hold, you can centralize this process by using one application. - Headings: H1: Legal Hold | H2: Starting with the Hold And Collect template | H2: Preparing to use Legal Hold | H2: Legal Hold technical requirements | H2: Legal Hold considerations | H2: Legal Hold documentation based on personas | H2: Training | H2: Installing Legal Hold - [Reminders] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Reminders.htm): There are multiple reminders within Legal Hold. Learn the basics of each in this topic and follow the links to other topics for specific instruction on each reminder. - Second paragraph: Before sending reminders, consider the following: - Headings: H1: Legal hold reminders | H2: Considerations | H2: Reminder types | H3: Project reminders | H3: Global reminders | H2: Enabling reminders | H3: Scheduling a global reminder | H3: Scheduling a project reminder | H3: Schedule Email Job and Email layout fields | H2: Sending a reminder | H3: Scheduling an automatic reminder | H2: Sending an escalation | H3: Scheduling an automatic escalation | H2: Reminder consoles | H3: Global Reminder console | H3: Project Reminder console | H2: Disabling reminders | H2: Disabling escalations - [Reporting] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Reports.htm): Run Legal Hold reports to analyze and manage your projects from the Legal Hold tab > Reports tab. - Second paragraph: You must consider and know the following before creating reports: - Headings: H1: Reports | H2: Considerations | H2: Report types | H3: Active Preservation Holds Report | H3: All Preservation Holds Report | H3: Communication Summary Report | H3: Custodian Active Projects Report | H3: Custodian Change Report | H3: Custodian Open Items Report | H3: Custodians Report | H3: Employment Status Change Report | H3: Global Summary Report | H3: Non-Responsive Custodians Report | H3: Questionnaire Response report - [Required load files] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Required_load_files.htm): Importing legacy data into Legal Hold requires separate imports through Import/Export for each object type. For example, import the custodians load file into the Entity object. - Second paragraph: Migrating data to Legal Hold should be performed by someone who is experienced with migrating structured data. If you do not possess this skill set, please reach out to a service provider or experienced colleague at your organization. For more information, see Required load files. - Headings: H1: Required load files | H2: Import order | H2: Entity load file | H3: Required fields | H3: Optional fields | H2: Projects load file | H3: Required fields | H3: Optional fields | H2: Communications load file | H3: Load file considerations | H3: Required fields | H3: Optional fields | H2: Attachments load file | H2: Custodian Role load file | H3: Required fields | H3: Optional fields | H2: Custodian Status load file | H3: Required fields | H3: Optional fields | H2: Message load file - [Responding to emails] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Responding_to_emails.htm): When a custodian responds to a hold communication, the response's message status is marked Received. You can respond to the received communications directly in Relativity Legal Hold from the email's details. - Second paragraph: After sent a response, the message status is marked Responded. - Headings: H1: Responding to emails - [Roles] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Roles.htm): All Legal Hold roles configuration and assignments. - Second paragraph: Use roles when sending communications to specific groups. For example, you may need to send a specific communication to only the Human Resources group at your company. Use roles to filter your custodian list when you use the Select option to send a communication from the Project console. See Project console. - Headings: H1: Assigning roles to custodians | H2: Creating a role | H2: Assigning a role - [Scheduling a report] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Scheduled_reports.htm): Use the Scheduled Reports feature to run reports on a set, recurring basis. You would typically use this feature to schedule a report to send out for the duration of a project or hold. Even though you can schedule a one-time report, this feature is optimized for longer term use. - Second paragraph: Scheduled Legal Hold reports are run under the permissions of the user scheduling the report. - Headings: H1: Scheduling a report | H2: Creating a scheduled report | H2: Create Scheduled Report layout fields | H2: Disabling or deleting a scheduled report - [Securing a workspace] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Managing_workspace_security.htm): To use Relativity Legal Hold, you need to configure the workspace security. - Second paragraph: See these related topics: - Headings: H1: Managing Legal Hold workspace security | H2: Accessing and configuring Legal Hold | H3: Legal Hold template | H2: Managing workspace security - [Sending a communication] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Sending_a_communication.htm): Send a communication, escalation, and reminder. - Second paragraph: Once you've sent a communication or questionnaire, you cannot retract it. If necessary, a system admin can create and send a new communication or questionnaire. For more information, see Creating a communication. - Headings: H1: Sending a communication | H2: Communication details | H3: Communication console | H2: Scheduling a communication | H2: Sending a reminder | H3: Scheduling an automatic reminder | H2: Sending an escalation | H3: Scheduling an automatic escalation | H2: Approving a communication | H3: Reviewing communications | H2: Acknowledging on behalf of a custodian - [Sending a questionnaire] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Sending_questionnaires.htm): Use questionnaires to receive more information from custodians. Create customizable questionnaires to gather custodian information. Add questions to the questionnaire and conditions to the questions conditional questions, send automatic alerts, and review responses. - Second paragraph: To send a questionnaire, you must first attach the questionnaire to a communication, then send the communication. - Headings: H1: Sending questionnaires | H2: Sending a questionnaire | H2: Resending a questionnaire | H2: Tracking question responses - [Tasks] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Tasks.htm): Within Legal Hold, there is a new Tasks tab. Create different types of tasks for specific projects to manage custodians, IT requests, HR requests, and other user tasks associated with your legal hold projects. - Second paragraph: To add a task for a member of the legal hold project, navigate to the Tasks tab. - Headings: H1: Task tracking | H2: Adding a task - [Workspace security] (https://help.relativity.com/RelativityOne/Content/Relativity_Legal_Hold/Workspace_security.htm): To successfully use the latest version of Relativity Legal Hold, you need to manage permissions. - Second paragraph: The Legal Hold custom permissions are independent from the System Admin group and aren't automatically assigned to the group. For Relativity System Administrators or Workspace Admin Group members to have access to the functions controlled by the Legal Hold Application, you must add these users to another security group or add a new group with access to the Legal Hold Application. When Legal Hold is installed to a workspace Relativity creates a Legal Hold Security Admins group where you can add users. - Headings: H1: Securing a legal hold project | H2: Securing a project | H2: Instance security | H2: Configuring Legal Hold ### Relativity Redact - [Automated image markup project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Automated_image_markup_project.htm): Creating an image markup project allows you to apply markups to a group of imaged documents automatically saving you time. You can create a project by entering words, terms, phrases, or regular expressions that you would like Redact to apply markups to. Alternatively, you can enter the rules in a .csv file and upload it to Relativity to create the rules for the image markup project. Once the project is created and run, markups will be applied automatically based on the rules you create. - Second paragraph: Consider creating a saved search with the documents you wish to apply markups to and a markup set that contains the markups you wish to apply to your imaged documents before starting the image markup project creation process. - Headings: H1: Automated image markup project | H2: Before you begin | H2: Creating an image markup project manually | H2: Creating an image markup project using .csv or .xlsm rules | H3: .csv or .xlsm rules | H2: Fields | H3: Create image markup project section | H3: Rules section | H2: Running the project | H2: Reviewing markups - [Automated image template markup project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Automated_image_template_project.htm): An image template project can be used to propagate all of the markups applied to a single, imaged document to each of the documents in a saved search. This is an effective way to apply markups in the same location for a group of documents. For example, if there is sensitive information in a series of tax forms that you want to obscure, you can run an image template project to apply the markups to each document. - Second paragraph: To use this project, you will need to choose an imaged document and create a saved search. - Headings: H1: Automated image template markup project | H2: Before you begin | H2: Creating an image template markup project | H2: Fields | H2: Running the project | H2: Reviewing markups - [Automated PDF markup project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Automated_PDF_markup_project.htm): Creating a PDF markup project allows you to apply markups to the text of PDF files automatically saving you time. Redact can apply markups to any part of a PDF file that has searchable text including: page text, headers, footers, text-based annotations, form data, and field properties. You can create a project manually by entering words, terms, phrases, or regular expressions that you would like Redact to apply markups to. Alternatively, you can enter the rules in a .csv file and upload it to Relativity to create the rules for the PDF markup project. Once the project is created and run, markups will be applied automatically based on your selected options. - Second paragraph: Consider creating a saved search with the documents you wish to apply markups to and a markup set that contains the markups you wish to apply to your PDF files before starting the PDF markup project creation process. - Headings: H1: Automated PDF markup project | H2: Before you begin | H2: Supported file types | H2: Creating a PDF markup project manually | H2: Creating a PDF markup project using .csv or .xlsm rules | H3: .csv or .xlsm rules | H2: Fields | H3: Create PDF markup project section | H3: Rules section | H2: Running the project | H2: Removing a markup applied by a project | H2: Reviewing markups - [Automated production preparation project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Automated_production_preparation_project.htm): The production preparation project has been deprecated and as a result, this project should no longer be used as part of your Redact workflow. - Second paragraph: If you have documents that were locked by a production preparation project and you need to produce and export them, we recommend using Import/Export. Any unlocked documents can also be exported using Import/Export but the newly unlocked documents must be run or re-run as part of a production so that the markups are burned in before the export. - Headings: H1: Automated production preparation project - [Automated spreadsheet markup project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Automated_spreadsheet_markup_project.htm): Creating a spreadsheet markup project can save you time over manually redacting by applying markups to Excel spreadsheet and .csv files automatically. You can create a project by entering words, terms, phrases, or regular expressions that you would like Redact to apply markups to. Alternatively, you can enter project rules into a .csv file and upload it to the project page that will populate the rules for a spreadsheet markup project. Once the project is created and run, markups will be applied automatically based on the rules you create. - Second paragraph: To learn more about which file types are compatible with Redact, see Redact supported file types. - Headings: H1: Automated spreadsheet markup project | H2: Supported file types | H2: Preparing Excel documents | H2: Before you begin | H3: Considerations | H2: Creating a spreadsheet markup project manually | H2: Creating a spreadsheet markup project using .csv or .xlsm rules | H3: .csv or .xlsm rules | H2: Fields | H3: Create spreadsheet markup project section | H3: Rules section | H2: Running the project | H2: Reviewing markups | H2: Reviewing the original native document - [Automated spreadsheet propagation project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Automated_spreadsheet_propagation_project.htm): The spreadsheet propagation project can be used to take the markups applied to an Excel spreadsheet and apply them to another group of Excel documents that require similar markups. You can also take markups applied to a .csv document and apply them to a different group of .csv documents. This project uses a saved search that contains the source documents and a saved search with documents you wish to apply markups to and it propagates the markups based on a duplicate identifier such as MD5 Hash. - Second paragraph: We recommend running the Prepare Excel for Redact mass operation, formerly known as the Unhide Excel Content mass operation, on all Excel documents before applying markups with Redact. This preparation is done to ensure data is not lost after the markups are applied and also to prevent information that is covered by markups from being restored by third parties. - Headings: H1: Automated spreadsheet propagation project | H2: Preparing Excel documents | H2: Before you begin | H2: Creating a spreadsheet propagation markup project | H2: Fields | H2: Running the project | H2: Reviewing markups | H2: Reviewing the original native document - [Blackout migration] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Blackout_Migration.htm): Relativity now supports Blackout when using ARM to restore a workspace from Relativity Server to RelativityOne. Native redactions from Blackout are migrated to Redact during this process. The event handlers run when updating to the next version of Redact post-installation. The event handlers do not need to be configured and they will automatically update previously migrated Blackout workspaces. - Second paragraph: You can now migrate documents that were included in the Redact External Markups workflow. To learn more about this workflow, see Redact External Markups. If you have used this workflow to upload documents with external markups, they are now be supported in the archive and restore of the workspace. - Headings: H1: Blackout migration | H2: Limitations | H2: Production preparation | H3: For native spreadsheets and PDFs before the migration | H3: Unlocking documents in Redact or Blackout before migration - [Convert Markups] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Convert_Spreadsheets_Markup.htm): You can use the Convert Markups mass operation, formerly known as Convert Spreadsheets Markup, to change the highlights to redactions or vice versa, regardless of whether the markups were created manually or by an automated project. The Convert Markups mass operation works with native spreadsheets, native PDFs, and stored PDF documents. Alternatively, you can use this mass operation to change the redactions from one type in a document to another. - Second paragraph: Only text or cell content redactions can be applied to .csv files. - Headings: H1: Convert Markups | H2: Changing markup types | H2: Reviewing converted markups - [Manual markups with PDF files] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Manual_Markups_with_PDF_files.htm): Redact allows you to apply markups to PDF files in the Viewer. An audit of the markups applied to each document can be viewed at any time to make tracking markups easy. You can also quickly locate any markups in a document and approve or reject them as part of your quality control process by using the Redaction Navigation card. Additionally, the Original Text field in the Redaction Navigation card is now supported with PDF documents so that you can see what text each markup covers. - Second paragraph: If you would prefer to have markups applied automatically, see Automated PDF markup project. - Headings: H1: Manual markups with PDF files | H2: PDF markup considerations | H2: Supported file types | H2: PDF basic redactions | H2: PDF highlights | H2: Rejecting highlights or markups | H2: Reviewing markups | H2: Downloading and exporting marked up documents - [Manual markups with spreadsheet files] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Manual_markups_with_spreadsheet_files.htm): Redact allows you to apply manual markups to Excel or .csv files in the Viewer. You can apply markups to specific parts of an Excel file including the sheet names, charts, objects, and headers and footers. An audit of the markups applied to each document can be viewed at any time to make tracking markups easy. You can also quickly locate any markups in a document and approve or reject them as part of your quality control process by using the Redaction Navigation card. - Second paragraph: Placing a markup on a document causes the coding layout to refresh. If you are editing a layout and place a markup, any unsaved edits to the layout fields will be lost. We recommend editing the fields on a layout and saving your changes before applying manual markups to a document. - Headings: H1: Manual markups with spreadsheet files | H2: Preparing Excel documents | H2: Excel file markup considerations | H2: Supported file types | H2: .csv file markup considerations | H2: Applying markups to .csv files | H2: Applying markups to Excel files | H3: Manually applying markups | H3: Applying the same markup repeatedly | H3: Cell Content redactions | H3: Sheet Name redactions | H3: Chart redactions | H3: Comment redactions | H3: Header and footer redactions | H3: Object redactions | H2: Convert Spreadsheets Markup | H2: Inverting markups | H2: Excel document keyboard shortcuts | H2: Reviewing markups | H2: Reviewing the original native document | H2: Downloading and exporting marked up documents - [PDF annotation and attachment markups] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redacting_PDF_annotations_and_attachments.htm): Markups can be applied to PDF annotations and attachments. The different types of annotations and attachments are described below as well as how to apply markups to them. - Second paragraph: Annotations are commonly used in PDFs and with Redact you can apply markups to any annotations you desire. There are two different kinds of annotations used in PDF files including annotations that are used to mark up the PDF file and annotations that consist of interactive forms or multimedia. To learn more about the different annotations, see PDF annotation types below. - Headings: H1: PDF annotation and attachment markups | H2: PDF annotation redactions | H3: PDF annotation types | H3: Applying redactions to PDF annotations | H2: Redacting PDF attachments | H3: Applying markups to PDF attachments - [Redact] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact.htm): With Redact, you can apply markups to imaged documents, spreadsheet files, and PDF files either manually or automatically as part of a project. You determine how a project applies markups by creating rules that establish what words, terms, or regular expressions will receive markups. You also determine which markup set is used by a project to apply markups. To learn more about markup sets, see Markup sets. Once a project has been run, Redact also provides tools to make reviewing markups easy. - Second paragraph: While Redact is flexible enough to support different workflows, the following is a typical workflow: - Headings: H1: Redact | H2: Example workflow | H2: Installing Redact to a workspace | H2: Before you begin | H2: File size considerations | H2: Redact supported file types | H2: Permissions | H3: All Redact permissions | H3: Native PDF Redactions permissions | H3: Native Excel Redactions permissions | H3: Image Redactions permissions | H3: Redact Mass Operations permissions | H3: Markup set permissions | H3: Permissions for redacting documents outside of Relativity - [Redact Audits] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_Audits.htm): As users interact with markups in Redact, an audit of each action is maintained. You can use this audit to track who applied markups, reverted them, and/or who approved/rejected each markup. - Second paragraph: The ten most recent markup actions display in the Redact Audits tab. You can view additional markup actions by clicking the left or right icons in the upper-right. - Headings: H1: Redact Audits - [Redact Client Usage Report] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_Client_Usage_Report.htm): Redact offers the Client Usage Report to help you track data and billing information. - Second paragraph: You can generate a usage report to help you track how much you have used Redact for billing and/or data tracking purposes. A usage report can be generated for a specific date range and it provides detailed usage statistics for each workspace. - Headings: H1: Redact Client Usage Report - [Redact External Markups] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_External_Markups.htm): Some documents cannot receive markups using Redact and if you open a document like this in the Viewer, a notification displays. For documents that cannot have markups applied in Redact or are too large for the Viewer, we recommend using Redact External Markups. - Second paragraph: External Markups only supports native files. Stored PDFs are not compatible with this feature. - Headings: H1: Redact External Markups | H2: Example workflow | H2: File size considerations | H2: Adding documents to External Markups tab | H2: Recommended uses of External Markups | H2: External Markups tab columns - [Redact Language Support] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_Language_Support.htm): While Redact only supports English when it is initially installed, it can support over 100 languages. If you are interested in having non-English languages added to Redact, please reference the following Community article or contact Relativity Support. - Second paragraph: Language packs can be included in an image project either individually or mixed together to cover multiple languages. In some cases you may find that the results are more accurate if you use a single language pack even if there are words in English in the documents. Since results can vary, we recommend testing non-English language support on a set of documents before doing a full project run. - Headings: H1: Redact Language Support | H2: Language settings in Relativity | H2: Entering Language Codes in an image markup project - [Redact Project Status] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_Project_Status.htm): The Redact Project Status tab lets you view all of the projects in an instance to track their status. This is useful when there are multiple projects queued across an instance and you want to see when a particular project might begin. Additionally, you can change the priority of projects that have been queued and have not been completed yet from this tab. This allows you to prioritize key Redact projects when several have been queued. Only users who have the system admin permission can access this tab. - Second paragraph: To view the status of every project in an instance, do the following: - Headings: H1: Redact Project Status | H2: Redact queue priority | H2: Redact project Priority queue | H2: Removing a project from the Priority queue - [Redact Reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_Reports.htm): Redact Reports allow you to create a custom report that contains markup and/or document field information for all of the documents in a saved search. A Markup Report contains a row for each markup applied to documents in the selected saved search. A Document Report contains a single row for each document in the saved search so you can efficiently view document field information. The user that generates the report receives a .csv copy via email. - Second paragraph: Redact can report on any field that is currently associated with the document object, Redact specific fields, and fields from the Viewer redaction table. This flexibility allows the creation of many different types of reports. - Headings: H1: Redact Reports | H2: Available report fields | H2: Generate a Markup or Document Report | H2: Redact specific fields - [Redact Settings] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_Settings.htm): The Redact Settings tab lets you determine what text displays in the text redaction options when you access the right-click menu in a spreadsheet document. - Second paragraph: The Default Redaction Text field can be edited to determine the contents of the text redaction that is applied when the Custom Redaction Text option is selected from the right-click menu. - Headings: H1: Redact Settings - [Redact validation workflow] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redact_validation_workflow.htm): The Redact validation workflow prevents production issues with markups on native spreadsheet and PDF documents. The workflow runs nightly based on your region on any eligible spreadsheet or PDF documents to prevent interruptions. The Redact validation workflow alerts users early on about issues they may experience while applying markups. The Redact validation workflow does not apply to images. - Second paragraph: When a document that cannot be redacted is identified by the validation workflow, two choices are applied to the Redact Document Warnings field: Caught by Validation Workflow and Cannot be Redacted in Native Viewer. The Cannot be Redacted in the Native Viewer value automatically adds the document to the Redact External Markups tab. The Caught by Validation Workflow value is informational. - Headings: H1: Redact validation workflow - [Redacting linked documents] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Redacting_linked_documents.htm): There are limitations to redacting documents that are exported as links from a repository workspace using Integration Points and ARM. To learn more about how to export linked documents with Integration Points, see Transferring (promoting) data between workspaces. - Headings: H1: Redacting linked documents | H2: Considerations - [Regular expression examples] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Regular_expression_examples.htm): Regular expressions can be used to help locate sensitive information including contact information, credit card numbers, and personal identification numbers. Examples of regular expressions that can be used to create rules are provided below. - Second paragraph: If you are using regular expressions for an automated image markup project, results may be improved by being defensive against common OCR mistakes. Each instance of any digit match can be replaced with a character replacement pattern that will evaluate numbers as common alphanumeric characters. - Headings: H1: Regular expression examples | H2: Before you begin | H3: Image markup considerations | H3: Named groups | H2: Email addresses and phone numbers regular expressions | H2: Universal regular expressions | H2: Financial accounts regular expressions | H3: Credit cards | H2: Government identification numbers regular expressions - [Reviewing markups to ensure accuracy] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Reviewing_markups_to_ensure_accuracy.htm): After markups have been applied, whether it be manually or automatically by a project, it is important to review them for quality control purposes. The Redact Navigation card allows you to track whether a markup has been reviewed and remove any markups that are no longer needed. Alternatively, to ensure that automated projects applied markups correctly, you can use Quality Review to compare the number of matches found in the extracted text of a document versus the number of markups that were applied by the project(s) to help you identify discrepancies before producing documents. - Second paragraph: The Redact Navigation card offers you the ability to indicate that a markup has been approved or you can remove any markups that are no longer needed as you perform quality control. After a markup has been applied to a document, the file will be marked with Yes for the Redact - Has Native Redactions field. You can then create a saved search using that field to organize a set of documents that have had markups applied in Redact. For more information on this, see Searching for documents with Redact fields. - Headings: H1: Reviewing markups to ensure accuracy | H2: Using the Redact Navigation card to review markups | H2: Using the Redact navigation card in the Image Viewer | H2: Review image markups using Quality Review | H2: Delete Native Markups - [Running and reverting a Redact project] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Running_and_reverting_a_project.htm): A project can be run once it has a Project Name, Saved Search, Markup Set, and rules. To help you track a project's readiness, a status message that indicates whether it is ready to be run or not displays when viewing a project. If there are multiple projects that have been queued to run, they will be completed in order of when they were queued. Once a spreadsheet or PDF markup project finishes running, it generates a report that contains a list of any documents where Redact could not apply a markup for quality control purposes. - Second paragraph: To begin running a project, do the following: - Headings: H1: Running and reverting a Redact project | H2: Running a project | H2: Redact project performance expectations | H3: Viewing a project's run status | H3: Viewing completed project's results | H2: Stopping a project that is running | H2: Reverting a project | H3: Adjusting Redact time out length - [Searching for documents with Redact fields] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Searching_for_documents_with_Redact_fields.htm): Redact comes with several fields to help make tracking markups applied both inside and outside of Redact easy. You can use these fields in a saved search to view documents that have certain types of markups applied with Redact. - Second paragraph: The following fields can be used to track markups: - Headings: H1: Searching for documents with Redact fields | H2: Creating a saved search using Redact fields - [Using Find and Redact] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Redact/Using_Find_and_Redact.htm): You can apply markups to a spreadsheet file in the Native Viewer while using the search capabilities of the Contextual Search card. - Second paragraph: This feature finds terms in a spreadsheet, native PDF, or stored PDF document and applies a markup to the desired terms without having to run a Redact project or manually apply markups. - Headings: H1: Using Find and Redact ### Relativity Short Message Format - [Creating an RSMF file] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/Creating_an_RSMF_File.htm): To use the Short Message Viewer, you will need to create an RSMF file and Relativity 10.3 or above. RSMF is an agnostic chat platform data format which means that as long as a platform's functionality contains messaging capabilities, it will likely be supported in RSMF. Over 40 different chat platforms’ data have been transformed and reviewed in RSMF. Examples of chat data that have been supported in RSMF include, but are not limited to: Slack, Microsoft Teams, Text messages (MMS, SMS, iMessage, Whatsapp), Google Chat, Bloomberg Chat, Instagram, and more. - Second paragraph: There are two methods you can use to create an RSMF file. Each method and some resources that provide additional information are provided below. - Headings: H1: Creating an RSMF file | H2: RSMF file support in Processing | H2: RSMF file creation process - [Processing an RSMF file] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/Processing_an_RSMF_file.htm): Relativity Processing is the recommended method of importing RSMF files into Relativity. Using processing ensures that the appropriate metadata header fields are extracted and families and attachments within the RSMF file are properly linked to give you the best near-native review experience. - Second paragraph: One recommended workflow is to use Import/Export to bring in multiple RSMF files zipped together as Raw (Unprocessed) Data and immediately processing the data. Another option is to prepare your RSMF files to be processed into Relativity using RelativityOne Staging Explorer to get the data ready. - Headings: H1: Processing an RSMF file | H2: Checklist for processing an RSMF file | H2: How parts of RSMF files are processed | H3: RSMF Header | H3: RSMF.zip | H2: RSMF deduplication | H3: Troubleshooting steps | H3: Troubleshooting attachments - [RSMF Slicing] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/RSMF_Slicing.htm): This feature allows you to select events in a conversation and "slice" them to create a new document that contains the selected events which can then be imaged and produced like any other document in Relativity. Slicing reduces the need to apply markups to short message conversations and lets you tailor the content of short message documents to your needs. - Second paragraph: Once a document has been sliced, it is also easy to track and manage them. When viewing a sliced document in the Short Message Viewer, a banner appears above the document to identify that it is sliced. You can quickly navigate to the original document by clicking on the document's name in the banner. To learn more, see Short Message Viewer. - Headings: H1: RSMF Slicing | H2: Slicing permissions | H2: Slicing an RSMF document | H2: RSMF slicing filters | H2: RSMF slicing audits - [RSMF-supported Emoji, Emoticons, and Attachments] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/RSMF-supported_Emoji_Emoticons_and_Attachments.htm): Relativity Short Message Format files are compatible with a wide range of Emoji, emoticons, and attachments. Any emoji or emoticons without visual support will display text instead. - Second paragraph: An emoji is a small image used alongside or instead of text in short messages. Emojis display in RSMF files as text strings surrounded by colons. For example, an emoji, :smile:, is included in the following section of a message body: - Headings: H1: RSMF-supported Emoji, Emoticons, and Attachments | H2: Supported emoji | H2: Supported emoticons | H2: Supported attachments | H2: Supported avatars - [Short message coding] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/Short_message_coding.htm): You can code individual messages in the Short Message Viewer. Using this workflow, you can highlight specific messages in a document that are relevant to your case. RSMF documents should be ingested using Processing or re-processed if they are already in Relativity. To learn more, see Short message investigative workflow. - Second paragraph: The following portions of the Short Message Viewer are relevant for short message coding: - Headings: H1: Short message coding | H2: Permissions | H2: Coding messages | H2: Message-level search highlights - [Short message investigative workflow] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/Short_message_investigative_workflow.htm): You can search and code messages in the Short Message Viewer using the investigative workflow. This workflow makes searching and reviewing RSMF documents and the short message metadata faster. For example, this workflow can be used to search messages based on date or time, messages sent by specific participants, edited or deleted messages, and any messages with reactions. Any messages that you find which are relevant to your case can be coded to make it easy to find later. - Second paragraph: To search short message metadata and messages, you can use Elasticsearch. To learn more, see Short message search index. Once you are done searching, you can code at the message-level in the Short Message Viewer. This makes finding relevant messages in a document faster. To learn more, visit Short message coding. - Headings: H1: Short message investigative workflow | H2: Before you begin | H3: Permissions | H3: Installing the short message search application | H3: Considerations | H2: Short message investigative workflow | H2: Collecting short message data | H3: Collection | H3: Importing and converting to RSMF | H2: Processing an RSMF file | H3: Before you begin | H3: Processing | H2: Integration Points | H2: Searching messages | H2: Reviewing RSMF documents | H3: Coding RSMF documents in the Short Message Viewer | H3: Coding messages | H2: Performing QC on RSMF documents | H2: Troubleshooting | H3: Mapping the document_uuid field - [The Relativity Short Message Format (RSMF)] (https://help.relativity.com/RelativityOne/Content/System_Guides/Relativity_Short_Message_Format/Relativity_short_message_format.htm): A Relativity Short Message File (RMSF) contains normalized short message data which can come from text messages like SMS or Apple iMessage or it can come from instant messenger services such as Skype, Bloomberg, or Slack. This document provides a list of requirements for RSMF files, the process you use to prepare those files for ingestion into Relativity, and how to use the Short Message Viewer once they are in your workspace. - Second paragraph: Once you’ve generated the files, the recommended workflow is to use Processing to ensure attachments maintain the proper relationship. You can also import the attachments separately and overlay the relationship to ingest an RSMF file into Relativity in order for attachments to display in-line in our Short Message Viewer, and to ensure those attachments are associated with the correct messages. To learn more, visit RelativityOne Staging Explorer. - Headings: H1: The Relativity Short Message Format (RSMF) | H2: RSMF structure | H3: Reaction | H3: Viewing the RSMF in an email application ### Relativity Transcripts - [Annotating transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Annotating_transcripts.htm): When you open a transcript in the Viewer, you can add the following annotations: Notes, Designations, Exhibits, URLs. - Second paragraph: If you are working with an MDB file, you can use the Relativity.Transcripts application. If you are working with another transcript file type, you can use the Transcripts application. - Headings: H1: Annotating transcripts | H2: Designations and Exhibits tab | H3: Uploading designations | H3: Exporting a designations or exhibits report | H2: Exhibits | H2: Designations | H3: Viewing designations in the Native Viewer | H3: Add a designation in Relativity.Transcripts | H3: Add a designation in Transcripts application | H3: Remove a designation | H2: Additional Transcripts application features | H3: Transcripts layout | H3: Adding notes | H3: Linking to URLs | H3: Working with Case Dynamics - [Copying text from a transcript] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Copying_text_from_a_transcript.htm): You can copy transcript text using either Relativity.Transcripts or the Transcript application. If you open an MDB file in the Native Viewer, you can copy text in the Transcript Text panel and if you open a .ptf, .xmptf, .rtf, .trn, .lef, .xmef, .txt, or .mp4, you can copy text in the Transcript Viewer. - Second paragraph: To copy transcript text only: - Headings: H1: Copying text from a transcript | H3: Copying text only | H3: Copying text with page:line numbers - [Printing transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Printing_transcripts.htm): You must have the Transcripts application installed to use this feature. - Second paragraph: To print transcripts from the Transcript Viewer: - Headings: H1: Printing transcripts | H2: Transcripts application | H3: Printing with the Transcript Viewer - [Searching transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Searching_transcripts.htm): Depending on which type of transcript file you're using, the search features vary. You can search the Transcript text and use persistent highlighting with MDB transcript files. You can use the Word Index with all other supported transcript file types which lets you search for phrases in the text and navigate to specific lines within the transcript. - Second paragraph: You can search the text of a transcript MDB file in the Viewer using the Transcript text panel. After you enter a search term and initiate a search, any search term hits are identified and you can navigate through them. - Headings: H1: Searching transcripts | H2: Relativity.Transcripts | H3: Transcript text searching | H3: Persistent highlighting | H2: Transcripts application | H3: Word Index - [Supported file types for the Transcripts application] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Transcript_supported_file_types.htm): Transcripts provides the capacity to upload the following file types: .ptf, .xmptf, .rtf, .trn, .lef, .xmef, .txt, xmp4. - Second paragraph: The Transcripts application supports a number of file types and each one is described below. - Headings: H1: Transcript supported file types | H2: Supported file types | H2: Transcripts application | H3: Special considerations | H3: Transcripts sync to video | H3: Transcripts with hyperlinked exhibits | H3: Text transcript file types - [Transcript reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Transcript_reports.htm): If you have the Transcripts application installed, you can export the different annotations and items that have been linked to transcripts, including Case Dynamics items. This feature only works with the following transcript file formats: .ptf, .xmptf, .rtf, .trn, .lef, .xmef, and .txt. - Second paragraph: To create a transcript report: - Headings: H1: Transcript reports | H2: Transcripts application | H3: Creating a transcript report | H3: Annotations Digest | H3: Key Terms - [Transcript Summary] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Transcripts_Summary.htm): You can create a summary of a transcript using Generative AI to quickly find relevant information for your case. Once a Transcript Summary has been created, it can be viewed in the Viewer or if you have aiR for Case Strategy installed, you can also view a more detailed summary on the Case Home tab. - Second paragraph: Summaries are supported for MDB transcripts with the Relativity.Transcripts application and summaries of ptf, .xmptf, .rtf, .trn, .lef, .xmef, .txt transcripts are supported with the installation of the Transcripts application. - Headings: H1: Transcript Summary | H2: Before you begin | H3: Permission | H3: Relativity.Transcripts billing and usage | H2: Creating a Transcript Summary | H2: Viewing a Transcript Summary | H2: Citation navigation | H3: Downloading a Transcript Summary | H3: Editing a Transcript Summary | H3: Clearing a Transcript Summary | H2: Transcript Summary prompt criteria - [Transcript video clips] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Transcript_video_clips.htm): You can create, save, merge, and export video clips with the transcripts application. - Second paragraph: The sample files below can be downloaded to your workstation and then uploaded to Relativity to help you test how video files work in the Transcripts application. For step-by-step instructions on this process, visit Uploading transcripts. - Headings: H1: Transcript video clips | H2: Transcripts application | H3: Sample video files | H3: View video clips | H3: Create a video clip | H3: Edit a video clip | H3: Export a video clip in .css or .csv - [Transcripts in Relativity] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Relativity_Transcripts.htm): Using both Transcripts applications, you can annotate transcripts, generate summaries, and create reports to support your workflows. We support a range of transcript file types, and the exact experience may vary depending on the file type you’re working with. - Second paragraph: Today, the transcripts experience in Relativity is supported by two applications: Relativity.Transcripts and Transcripts application. Their capabilities partially overlap, and some features are available only in one application or the other. The two applications are now installed together to ensure access to the full feature suite. - Headings: H1: Transcripts in Relativity | H3: Relativity.Transcripts | H3: Transcripts application | H2: Transcripts application comparison | H2: Before you begin | H3: Installation | H3: Relativity.Transcripts | H3: Transcripts billing and usage | H2: Permissions | H3: Relativity.Transcripts permissions | H3: Transcripts application permissions | H3: Reviewer security permissions - [Transcripts tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Transcripts_tab.htm): The Transcripts tab contains individual tabs with views for Notes, Exhibits, URLs, Comments, Designations, and Designation types. - Second paragraph: The Notes tab contains the following fields: - Headings: H1: Transcripts tab | H2: Transcripts application | H3: Notes tab | H3: Exhibits tab | H3: URLs tab | H3: Comments tab | H3: Designations tab | H3: Designation Types tab - [Uploading transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Relativity_Transcripts/Uploading_Transcripts.htm): When uploading Transcripts, Relativity automatically creates folders named after the Deponent Name field. Transcripts are stored in these folders, along with any corresponding attachments. - Second paragraph: When uploading transcripts using the Transcripts application, Relativity automatically creates a folder to house all transcripts with sub folders named after the Deponent Name field. Transcripts are stored in these folders, along with any corresponding attachments. If there are no exhibits, an exhibit folder is not created. - Headings: H1: Uploading transcripts | H2: Transcripts application | H3: Special considerations | H3: Upload a transcript from the Documents tab | H3: Mass importing transcripts with Import/Export | H3: Reading transcripts with page number | H3: Supported file types | H3: Editing the Transcripts Import Layout ### Relativity Unified Experience - [Configuring Your Environments] (https://help.relativity.com/RelativityOne/Content/Relativity_Unified_Experience/Configuring_your_environments.htm): You can use the Relativity User and Group Synchronization application to synchronize groups, users, OpenID login methods, and clients from a designated master instance to a connected duplicate instance. - Second paragraph: For User Group Synchronization functionality to work properly, your primary instance must be able to communicate with the duplicate instance over port 443. - Headings: H1: Configuring your environments | H2: Provision your environments | H2: Configure your duplicate instance | H2: Configure your primary instance | H2: (Optional) Set up single sign-on - [Installing the User and Group Synchronization Applications] (https://help.relativity.com/RelativityOne/Content/Relativity_Unified_Experience/Installing_the_User_and_Group_Synchronization_applications.htm): The User Group Synchronization application has two different RAP files. One version is for the primary instance, and one version for the duplicate instance. - Second paragraph: To install User and Group Synchronization, follow the steps below: - Headings: H1: Installing the User and Group Synchronization applications | H2: Install both applications - [Relativity Hybrid Model] (https://help.relativity.com/RelativityOne/Content/Relativity_Unified_Experience/Relativity_hybrid_model.htm): With the introduction of RelativityOne, hybrid environments (combining cloud and on-premise instances) are becoming a common deployment scenario. The Relativity hybrid model provides a compelling alternative to on-premises hosting of cases. - Second paragraph: Hybrid environment business scenarios: - Headings: H1: The Relativity hybrid model | H2: Basic high-level workflow for setting up the hybrid model | H2: Single sign-on workflow (SSO) - [User Synchronization] (https://help.relativity.com/RelativityOne/Content/Relativity_Unified_Experience/User_synchronization.htm): You can use the Relativity User and Group Synchronization application to synchronize groups, users, OpenID login methods, and clients from a designated master instance to a connected duplicate instance. - Second paragraph: This functionality is only available for customers running at least one RelativityOne instance, as well as a second instance running either RelativityOne or Relativity 9.5.224.9 and above. - Headings: H1: Relativity User and Group Synchronization | H2: User and Group Synchronization topics - [Working with User and Group Synchronization] (https://help.relativity.com/RelativityOne/Content/Relativity_Unified_Experience/Working_with_User_and_Group_Synchronization.htm): After installing and configuring the User and Group Synchronization application in your environments, you can sync users from your primary instance to your duplicate instance, view user and group synchronization information, and monitor the status of jobs that the User Group Sync agent processes during a sync. - Second paragraph: Special considerations include: - Headings: H1: Working with User and Group Synchronization | H2: Special considerations | H2: Specifying which users to sync with your duplicate instance | H2: User sync data flow | H3: Special considerations | H3: Object fields that are synced to the duplicate instance | H2: Viewing User and Group Synchronization information | H2: Excluding groups and clients from synchronization - [Workspace Portal] (https://help.relativity.com/RelativityOne/Content/Relativity_Unified_Experience/Workspace_Portal.htm): In Relativity, a workspace provides a secure data repository for documents used in cases or for applications developed with Dynamic Objects. Workspace portal refers to a Relativity application that enables you to view all your workspaces from a single tab that exists in both your master on-premise Relativity instance and a satellite RelativityOne instance in the cloud. You can navigate between the instances seamlessly using single sign-on, and easily create and edit new workspaces in either environment. - Headings: H1: Workspace Portal ### RelativityOne - [Managing data] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Managing_data.htm): Managing data in RelativityOne involves various steps and processes. You can do everything from ingest data, process data, transferring, producing, and storing data. Managing data in RelativityOne involves leveraging its various features and tools to efficiently process, review, and analyze electronic documents and data, while adhering to strict data security and compliance standards. - Headings: H1: Managing data - [Managing security and permissions] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Managing_security.htm): Security and permissions are of paramount importance in RelativityOne, as they play a crucial role in safeguarding sensitive legal and e-discovery data, ensuring compliance with privacy regulations, and maintaining the integrity of legal proceedings. Configuring security measures properly can help organizations strike a balance between data protection and the collaboration necessary for effective legal work. - Headings: H1: Managing security and permissions - [Managing users and groups] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Managing_users_and_groups.htm): Managing users and groups in RelativityOne is a critical aspect of administering the platform and ensuring that the right users have access to the appropriate workspaces and resources. Properly configuring roles, permissions, and access controls helps ensure that users have the right level of access to the platform's features and the workspaces within it. Regularly reviewing and updating user and group settings is essential for maintaining a secure and well-organized environment. - Headings: H1: Managing users and groups - [Managing workspaces] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Managing_workspaces.htm): Managing workspaces in RelativityOne involves setting up, organizing, and configuring the digital environments to process, review, and analyze electronic documents and data. Managing workspaces in RelativityOne is essential for efficiently handling eDiscovery and legal processes. It involves creating and configuring the digital environment, ensuring data security and compliance, and facilitating collaboration among team members. Regular monitoring and maintenance of workspaces are crucial to maximize the platform's effectiveness and to ensure adherence to your organization’s policies. - Headings: H1: Managing workspaces - [Navigating] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Navigating.htm): Relativity is an application with many screens and functions. Being familiar with the interface will be helpful as you work with the software. This section describes some of the standard procedures you'll need to perform as you use the product. For example, to navigate well, you’ll need to understand RelativityOne tabs, views, and layouts. - Second paragraph: Get started navigating RelativityOne with: - Headings: H1: Navigation | H2: Logging in | H2: Tab navigation | H3: Sidebar | H2: All tabs menu | H2: Tab strip | H3: Parent and child tab display | H2: User options | H3: Changing the default Home tab | H3: My settings | H3: Dashboards | H2: Creating a dashboard | H2: Adding widgets to a dashboard | H2: Saving changes to a dashboard | H2: Deleting a dashboard | H2: Renaming a dashboard | H3: Using the search panel | H2: Resetting your password | H3: Resetting your password inside Relativity | H3: Resetting your password outside Relativity | H2: Favorites | H2: Quick nav - [Performance and Usage Guidelines] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Performance_and_Usage_Guidelines.htm): Describes known or estimated performance limitations in RelativityOne - Second paragraph: These limits and measures are subject to change. - Headings: H1: Performance and Usage Guidelines - [Technical aspects and requirements] (https://help.relativity.com/RelativityOne/Content/Getting_Started/RelativityOne/Technical_aspects.htm): The listed topics give background information on browser or workstation prerequisites, downtime windows, and describe some aspects of Relativity that may be of interest. - Second paragraph: Get started in RelativityOne with: - Headings: H1: Technical aspects and requirements ### RelativityOne Staging Explorer - [Best practices and limitations] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Best_Practices_and_Limitations.htm): The following are some good practices, limitations, and performance factors to consider when using Staging Explorer. - Second paragraph: For information on Staging Area folders, refer to the Staging Area topic and Staging Area FAQ article in Community. - Headings: H1: Best practices, limitations, and data transfer performance considerations | H2: Best practices | H2: Limitations | H2: Data transfer performance considerations - [Calculating folder size] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Calculating_folder_size.htm): For information on Staging Area folders, refer to the Staging Area topic and Staging Area FAQ article in Community. - Second paragraph: You must enable View Client Domain Staging Reports permission in Admin Operations to be able to utilize the Calculate Size function. - Headings: H1: Calculating folder size in Local/Staging panes | H2: Calculating folder size - [File and folder operations (copy, move, delete, zip, unzip)] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/File_and_folder_operations.htm): File operations are available for files and folders in the Local and Staging panes. - Second paragraph: Below are the top-level directories included in the Staging area within each tenant or client domain storage area: - Headings: H1: File and folder operations (copy, move, delete, zip, unzip) | H2: Button legend | H2: Copying files and folders | H2: Moving files and folders | H2: Zipping (compressing) and unzipping (extracting) files and folders | H3: Considerations and Limitations | H3: Zipping (compressing) files and folders | H3: Unzipping (extracting) files and folders - [Installing, launching, and updating] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Installing__launching__and_updating.htm): For information on Staging Area folders, refer to the Staging Area topic and Staging Area FAQ article in Community. - Second paragraph: Use the sections below to learn how to install Staging Explorer as well as how to launch and update it. - Headings: H1: Installing, launching, and updating Staging Explorer | H2: System requirements | H3: Recommended browser settings | H3: Supported browsers | H3: Port requirements | H2: Installing Staging Explorer | H2: Launching Staging Explorer | H2: Manually updating Staging Explorer | H2: Automatically updating Staging Explorer - [Navigation] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Navigation.htm): For information on Staging Area folders, refer to the Staging Area topic and Staging Area FAQ article in Community. - Second paragraph: When you open Staging Explorer, there is user drop-down menu next to your name. - Headings: H1: Navigation | H2: User drop-down menu | H2: General navigation | H2: Pagination - [Permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Permissions.htm): Data Transfer is a modernized feature permission at the instance level. You can only grant or revoke access to Staging Explorer by enabling or disabling the Data Transfer feature permission directly. The underlying granular permissions are locked and controlled by the feature toggle. - Second paragraph: Existing groups and their permission configurations are not impacted at this time. However, aligning your groups with the Data Transfer feature permission is recommended. If a group's permissions are out of alignment, a blue banner and lightbulb icon appear in the Permissions UI with migration tooling to help. For details on modernized feature permissions and the full list of granular permissions controlled by the Data Transfer permission, see Feature Permissions. - Headings: H1: Permissions - [RelativityOne Staging Explorer] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/RelativityOne_Staging_Explorer.htm): The RelativityOne Staging Explorer is used to upload and download files to RelativityOne workspaces. - Second paragraph: Staging Explorer enables you to rapidly transfer large amounts of data to and from RelativityOne to jump-start and sustain the data pipeline for critical projects. Use it to upload files to a staging area for RelativityOne or to download files from your RelativityOne storage location to a local computer. - Headings: H1: Staging Explorer - [Requesting a throughput check] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Requesting_Throughput_Check.htm): Throughput Check is used to provide reference transfer throughput based on your current connection. - Headings: H1: Requesting a Throughput Check - [Transfer workflows] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Transfer_workflows.htm): For information on Staging Area folders, refer to the Staging Area topic and Staging Area FAQ article in Community. - Second paragraph: Refer to the sections below for the various transfer workflows available in Staging Explorer. - Headings: H1: Transfer workflows | H2: File and folder naming rules | H3: Unsupported characters | H2: Uploading files | H2: Downloading files | H2: Starting and canceling a transfer | H2: Retrying a transfer | H2: Deleting a transfer | H2: Viewing transfer history | H2: Viewing and editing transfer details | H3: Viewing transfer details | H2: Saving the path issues report - [Updating transfer settings] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/Updating_Transfer_Settings.htm): Complete the following steps to update various transfer settings and apply automatic updates. - Headings: H1: Updating Transfer Settings - [User access permissions to file shares] (https://help.relativity.com/RelativityOne/Content/Relativity/RelativityOne_Staging_Explorer/User_access_permissions_to_file_shares.htm): The Staging Area permissions managed in Staging Explorer, released in late January, introduce a new model for managing file share access and will replace the process of setting file shares permissions for Client Domains.Customers are required to complete the transition by June 1, as the process described in Granting user access to specific file shares will no longer be valid.Please review the new workflow in Assigning user group access permissions and begin setting up access for your RelativityOne Staging Explorer user groups in the Staging Explorer tab to prepare for the transition. Also, see this Community article on upcoming changes. - Second paragraph: Follow the instructions below to assign permissions to user groups for accessing specific file shares in the Staging Explorer pane. As a result, each user will only be able view file shares they are allowed to access. - Headings: H1: User access permissions to file shares | H2: Assigning user group access permissions | H2: Default workflow in RelativityOne for user access to file shares | H2: Granting user access to specific file shares ### Review Center - [Active Learning application history] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Active_Learning_history.htm): If your workspace includes projects from the older Active Learning application, you can review their statistics and results from the Active Learning History tab. This tab shows read-only data for each project. - Second paragraph: This tab can be accessed through the Review Center dashboard. For more information, see Viewing archived Active Learning projects. - Headings: H1: Active Learning application history | H2: Selecting an Active Learning project | H2: Project Statistics section | H2: Manually Selected section | H2: Prioritized Review section | H2: Coverage Review section | H2: Project Validation History section | H2: Model Updates section - [Creating a Review Center queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Creating_a_Review_Center_project.htm): Review Center queues are flexible, customizable, and can be used for any stage of review. You can also create templates for common workflows, which shortens the setup time for a new queue to only a few clicks. These queue templates can be saved as part of workspace templates, making it easy to re-use them for other cases. You can also use the AI training from previous queues to improve the relevance predictions in new queues. - Second paragraph: Even after creating a queue, you can still edit the settings or add new documents without interrupting reviewers. - Headings: H1: Creating a Review Center queue | H2: Installing Review Center | H2: Choosing a queue type | H3: Saved search queues | H3: Prioritized review queues | H2: How document assignment works | H3: Keeping document families together | H2: Setting up the reviewer group | H3: Checking document permissions | H2: Creating required queue fields | H2: Creating the saved search | H3: Reducing document clutter | H3: Saved search recommendations for prioritized review queues | H2: Creating a queue template | H2: Editing premade templates | H2: Queue and template settings list | H2: Creating a new queue from a template - [Monitoring a Review Center queue] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Monitoring_a_Review_Center_project.htm): The Review Center dashboard provides a centralized location to track, manage, and edit all Review Center queues. In addition, you can track reviewer coding decisions through a variety of methods. - Second paragraph: See these related pages: - Headings: H1: Monitoring a Review Center queue | H2: Review Center dashboard | H3: Queue tab strip | H3: Queue Summary section | H3: Review Progress section | H2: Charts and tables | H3: General charts and tables | H3: Prioritized review charts | H3: Reviewed Documents table | H2: Preparing or refreshing the queue | H3: Checking refresh status | H3: Auto-refreshing the queue | H3: Reviewer access during refreshes | H3: Auto-refreshing in Coverage Mode | H3: Caching text in prioritized review queues | H2: Starting the queue | H2: Editing queues and other actions | H3: Editing recommendations | H3: Turning Coverage Mode on and off | H2: Deleting a queue | H2: Fixing a misconfigured queue | H2: Understanding document ranks | H2: Tracking reviewer decisions | H3: Using the Documents tab | H3: Using the Field Tree | H3: Using the Track Document Field Edits by Reviewer application | H2: Moving Review Center templates and queues | H2: Viewing archived Active Learning projects - [Reusing saved models] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Reusing_saved_models.htm): A saved model in Review Center provide the ability to take the knowledge, or the training, from one Review Center queue and re-use it in another queue - Second paragraph: See these related pages: - Headings: H1: Reusing saved models | H2: Saved model | H2: What a saved model contains | H3: How predictions work with multiple models | H3: Privacy considerations when reusing saved models | H2: Common use cases for saved models | H2: Creating a saved model | H3: Creating from queues with linked models | H2: Linking a saved model to a Review Center queue | H3: Removing a linked model from a queue | H3: How linked models behave with ARM | H2: Managing saved models | H3: Copying saved models to another workspace | H3: Editing or deleting saved models | H3: Saved models from Active Learning - [Review Center] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Review_Center.htm): Review Center is a review management tool that helps you build custom queues, use AI to prioritize relevant documents, and leverage a rich reporting dashboard to understand the state of your data and track productivity. With streamlined administrative features and flexible AI algorithms, you can tailor the review process to your needs. - Second paragraph: Some of Review Center's key features include: - Headings: H1: Review Center | H2: Review Center overview | H2: Review Center workflow | H2: Understanding the integrative learning classifier | H3: Support Vector Machine learning (SVM) | H2: Language support in Review Center | H2: Using Review Center versus batching | H2: Archiving and restoring workspaces with Review Center | H2: Review Center resources - [Review Center - admin quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Review_Center/Review_Center_-_Admin_QRG.htm): For more detailed instructions, see the Review Center section of the documentation site. - Second paragraph: All queues can be set to serve entire relational groups to the same reviewer. - Headings: H1: Review Center - Admin quick reference guide | H2: Choose a queue type | H2: Set up the reviewer permissions group | H2: Set up the layout | H2: Create the saved search | H2: Create or customize the queue template | H2: Create the queue | H2: Activate and manage the queue | H3: Update the queue and the classifier | H2: Review documents | H3: Review Center queue checklist - [Review Center - reviewer quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Review_Center/Review_Center_-_Reviewer_QRG.htm): For more detailed instructions, see the Review Center section of the documentation site. - Second paragraph: As you review, you can navigate to documents you already reviewed in the queue by clicking on Documents on the left-hand navigation. This opens the Documents panel. - Headings: H1: Review Center - Reviewer quick reference guide | H2: Accessing your queue | H2: Navigating the queue | H2: Review Center dashboard - [Review Center performance baselines] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Review_Center_performance_baselines.htm): This page acts as a reference to track the general performance of Review Center in RelativityOne. - Second paragraph: Because of data and configuration differences, do not use this as a benchmark for what to expect in your own organization's environment. The results may not scale linearly. - Headings: H1: Review Center performance baselines | H2: Queue size recommendations | H2: Performance testing definitions | H2: Overall build speed | H2: Build time variance with document coding and caching | H2: Build time variance with more documents - [Review Center security permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Review_Center_security_permissions.htm): This page contains information on the security permissions required for creating and interacting with the Review Center application. For more information on setting permissions, see Workspace security. - Second paragraph: To create a Review Center template or queue, you need the following permissions: - Headings: H1: Review Center security permissions | H2: Creating a Review Center template or queue | H2: Editing and controlling Review Center queues | H2: Deleting a Review Center template or queue | H2: Viewing the Review Center dashboard | H2: Managing saved models | H2: Tracking reviewer decisions from the Documents tab | H2: Reviewer permissions | H3: Checking document permissions - [Review validation] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Review_validation.htm): Review validation evaluates the accuracy of a Review Center queue. The goal of validation is to estimate the accuracy and completeness of your relevant document set if you were to stop the queue immediately and not produce any unreviewed documents. The primary statistic, elusion rate, estimates how many uncoded documents are actually relevant documents that you would leave behind if you stopped the queue. The other statistics give further information about the state of the queue. - Second paragraph: Review validation does not check for human error. We recommend that you conduct your own quality checks to make sure reviewers are coding consistently. - Headings: H1: Review validation | H2: Key definitions | H2: Determining when to validate a Prioritized Review queue | H2: Starting a validation queue | H3: Choosing the validation settings | H3: Inherited settings | H2: Coding in a validation queue | H2: Monitoring a validation queue | H3: Viewing formulas for validation statistics | H3: Editing a validation queue | H3: Releasing unreviewed documents | H3: Tracking sampled documents | H2: Accepting or rejecting validation results | H3: Manually rejecting validation results | H2: Reviewing validation results | H3: Recalculating validation results | H3: Viewing results for previous validation queues | H2: How adding or changing documents affects validation | H3: Scenarios that require recalculation | H3: Scenarios that require a new validation queue - [Review validation statistics] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Review_validation_statistics.htm): Review Center provides several metrics for evaluating your review coverage: elusion, richness, recall, and precision. Together, these metrics can help you determine the state of your Review Center project. - Second paragraph: Once you have insight into the accuracy and completeness of your relevant document set, you can make an educated decision about whether to stop the Review Center workflow or continue review. - Headings: H1: Review validation statistics | H2: Defining elusion, recall, richness, and precision | H2: Groups used to calculate validation metrics | H3: Variables used in the full calculations | H2: How setting a cutoff affects validation statistics | H3: High versus low cutoff | H2: Validation metric calculations | H3: Elusion rate | H3: Recall | H3: Richness | H3: Precision | H2: How the validation queue works | H2: How validation handles skipped and neutral documents - [Reviewing documents using Review Center] (https://help.relativity.com/RelativityOne/Content/Relativity/Review_Center/Reviewing_documents_using_Review_Center.htm): The Review Queues tab is the starting point for reviewers. Every Review Center queue that a reviewer is assigned to shows up here. - Second paragraph: This topic provides step-by-step instructions for accessing a queue and reviewing documents. - Headings: H1: Reviewing documents using Review Center | H2: Reviewing documents in the queue | H2: Finding previously viewed documents | H2: Queue card statistics | H2: Viewing the dashboard | H2: Best practices for Review Center review | H3: Coding according to the "four corners" rule | H3: Factors that affect Review Center's predictions ### Review Interface QRG - [Review Interface quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Review_Interface_QRG/Review_interface.htm): Each viewer serves its own purpose and own file type, but there are common functions within all of them. There are also viewer-specific functionality that is called out in the viewer tables. - Second paragraph: Use this section to understand the Native Viewer and its options. - Headings: H1: Review Interface quick reference guide | H2: Document actions and Viewer settings | H2: Native Viewer | H2: Short Message Viewer | H2: Image Viewer | H2: Extracted Text Viewer | H2: Productions Viewer | H2: PDF Viewer ### Review Template - [RelativityOne Review Workspace template] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Review_Template/RelativityOne_Review_workspace_template.htm): The RelativityOne Review Template simplifies the end-to-end document review and production workflow by making visible only the tabs, views, layouts, and fields recommended by Relativity for typical document review. All workspace functionality is available, but less-common tabs are nested in hidden parent tabs which can be unhidden if needed. - Second paragraph: The RelativityOne Review Template simplifies the end-to-end document review and production workflow by making visible only the tabs, views, layouts, and fields recommended by Relativity for typical document review. All workspace functionality is available, but less-common tabs are nested in hidden parent tabs which can be unhidden if needed. - Headings: H1: RelativityOne Review Workspace template | H2: Review Queues | H2: Documents | H2: Review Center | H2: Processing | H2: Search Setup | H2: Imaging and Production | H2: Review Management | H2: Workspace Setup | H2: Admin | H2: Change Log - [Reviewing and producing documents] (https://help.relativity.com/RelativityOne/Content/Getting_Started/Review_Template/Reviewing_and_producing_documents.htm): RelativityOne provides you with a set of tools to quickly and proficiently review, redact, and produce documents in litigation or in response to government inquiries. Accelerate through review and production efficiently and accurately with intuitive workflows that allow you to identify and organize the most relevant information and confidently get to the crux of your litigation matter faster. ​ - Second paragraph: For videos and tutorials that cover the basics of Review and Production in RelativityOne, see the Using the RelativityOne Review Template learning path. - Headings: H1: Reviewing and producing documents | H2: Step 1 – Gather background and other reference materials | H2: Step 2 - Setup data for review | H2: Step 3 - Review documents | H2: Step 4 – QC documents for Responsiveness and Privilege | H2: Step 5 – Redact documents | H2: Step 6 – Prepare Non-Privileged documents for production | H2: Step 7 – Produce documents ### Saved search - [Common Saved Searches Applications] (https://help.relativity.com/RelativityOne/Content/Relativity/Saved_search/Common_Saved_Searches_application.htm): There are a standard set of searches common to basic use of Relativity. The searches provided in this application provide a starting point for common searches needed for basic functions. There are still fields that might need to be displayed, but the conditions of these searches are set. This template may be a starting point for you. - Second paragraph: The installation process follows the same steps used to install other Relativity applications. For more information, see Installing applications. - Headings: H1: Common Saved Searches application | H2: Installing the application | H2: Using the application - [Creating or editing a saved search] (https://help.relativity.com/RelativityOne/Content/Relativity/Saved_search/Creating_or_editing_a_saved_search.htm): To create or edit a saved search. - Second paragraph: Before creating or editing a saved search, consider the following: - Headings: H1: Create and edit a saved search | H2: Considerations | H2: Create a saved search | H2: Search fields | H3: Information | H3: Advanced | H3: Conditions | H3: Fields | H3: Sort | H2: Pop-up pickers | H3: Select items pop-up picker | H3: System user fields | H3: Folder name field | H2: Search bar | H3: Recent Searches | H2: Link a Relativity application to a saved search | H2: Link a dashboard to a saved search | H2: Rerun out-of-date saved searches - [Defining criteria for saved searches] (https://help.relativity.com/RelativityOne/Content/Relativity/Saved_search/Defining_criteria_for_saved_searches.htm): You define the criteria used for saved searches in the Conditions section of the saved search form. You can build complex queries using a combination of fields and operators that are set to required values. This page provides information about the operators available for building these queries, as well as specific options for searching batches and developing combined searches. - Second paragraph: When defining search criteria in the Conditions section of a saved search form, you use operators to determine how a field is queried for the value that you selected or entered. The operators available for a search criterion depend upon the field type: - Headings: H1: Defining criteria for saved searches | H2: Operators | H3: Fixed-length, long, or extracted text operators | H3: Whole number, decimal, and currency operators | H3: User operators | H3: Date operators | H3: Yes or no operators | H3: Single and multiple choice field operators | H2: Batch fields as search conditions | H2: Using saved searches as conditions (combined searches) | H3: Preventing circular references | H3: Including related items in combined searches | H2: Lists as search conditions - [Saved search] (https://help.relativity.com/RelativityOne/Content/Relativity/Saved_search/Saved_search.htm): A saved search is a saved set of criteria that returns the latest documents that meet that criteria. For example, if you want to reference documents that contain the terms confidential and property and are also marked as Relevant, you can create a saved search with that criteria. However, saved searches can be much more complex. - Second paragraph: In Relativity, you can create saved searches by defining custom queries and unique views, as well as by selecting public or private security settings, specific folders to query, and nested sort orders. You can also execute a search on the fly, save it for later use, or perform a combination of these tasks. - Headings: H1: Saved search | H2: Permissions | H2: Navigating the saved searches browser | H3: Filtering the list of saved searches | H3: Performing mass operations on saved searches | H2: Controlling the visibility of saved searches | H2: Organizing saved searches in folders | H3: Adding sub-folders to the root | H3: Managing subfolders | H3: Adding existing searches to folders - [Saved search history] (https://help.relativity.com/RelativityOne/Content/Relativity/Saved_search/Saved_search_history.htm): On the History tab, you can view the audit records for saved searches, unsaved searches, and queries performed on views (such as filtering on a column). - Second paragraph: Use the following guidelines to view search history records: - Headings: H1: Saved search history - [Saving searches on the Documents tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Saved_search/Saving_searches_on_the_Documents_tab.htm): On the Documents tab, you can click Save as Search to save a search based on the criteria that you - Second paragraph: To use Save Search, you must have add permissions for Search, and access to the Saved Searches Browser. See Setting workspace permissions. - Headings: H1: Saving searches on the Documents tab ### Search term reports - [Create and edit search term reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_term_reports/Create.htm): You can create, edit, and copy search term reports on the Search Term Reports tab. - Second paragraph: Use the following guidelines to ensure that your search terms report properly highlights the required terms: - Headings: H2: Create search term report | H3: Adding search terms report information | H3: Workspace templates | H2: Editing search term reports | H3: Editing terms | H3: Editing highlight colors | H3: Deleting terms | H3: Copying a search terms report - [Errors] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_term_reports/Errors.htm): As the search terms report runs, Relativity checks for errors. If Relativity encounters errors, you will see a red banner just above the list of terms. You will also see a message in the Error message column for each term that Relativity could not process. The Status column displays Error. - Second paragraph: The error messages tell you the type of error encountered. For example, you can resolve syntax errors yourself and then retry them, while support errors require customer support for resolution. - Headings: H1: Errors | H2: Syntax errors | H2: Support errors - [Run a search terms report] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_term_reports/Run.htm): You generate a search terms report by using the options available in the search terms report console. The console appears after you save a search terms report or when you open an existing report from the Search Terms Reports tab. - Second paragraph: The console includes the following options: - Headings: H1: Run a search terms report | H2: Search terms reports status - [Search terms report hit count] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_term_reports/Hit_count.htm): This recipe describes how to calculate and store the number of terms in a Search Terms Report (STR) that hit on a document. You can then sort, filter and search for documents based on the number of STR hits, allowing you to prioritize review based on STR hit count or create searches that return documents having a minimum number of STR hits. - Second paragraph: You can then sort, filter and search for documents based on the number of STR hits, allowing you to prioritize review based on STR hit count or create searches that return documents having a minimum number of STR hits - Headings: H1: Search terms report hit count | H2: Prerequisites | H3: Downloading the Delimiter Count by Saved Search script | H3: Creating Search term report fields | H2: Saved search | H2: Import | H2: Run script - [Search terms reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_term_reports/STR.htm): Search terms reports provide the ability to identify documents containing specific keywords or terms that are important to a case. You can enter multiple terms and generate a report listing the number of hits for each term in a document. You can determine the output of the report by selecting one of the following type options. - Second paragraph: For information on how to calculate and store the number of terms in a Search Terms Reports (STR) that hit on a document, see Search terms report hit count. - Headings: H1: Search terms reports | H2: Permissions - [Tag hits] (https://help.relativity.com/RelativityOne/Content/Relativity/Search_term_reports/Tag_hits.htm): Enabling the Tag option gives you the changes to access documents in the Field Tree browser and tag terms in a saved search. - Second paragraph: When enabled, Relativity saves the results to a multiple object field named after the search terms report with the prefix STR. For example, STR - Industry terms. This is so you can review the results later. During the search, Relativity tags each document containing search hits using the STR multiple object field with the search terms found in each document. - Headings: H1: Tag Hits | H2: Tagged documents in the Field Tree browser | H2: Tagged search terms in a saved search ### Searching - [Multiple object searching] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Multiple_object_searching.htm): This page describes the logic behind multiple object searching. - Second paragraph: When searching using These Conditions or NOT These Conditions, keep in mind the following: - Headings: H1: Multiple object searching | H2: These Conditions | H2: These Conditions and These Conditions | H2: NOT These Conditions | H2: These NOT | H2: None of these and Not all of these operators - [Search conditions] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Search_conditions.htm): You can use the search conditions option to build complex queries by selecting fields, operators, and values. While this feature has the same functionality as the search condition section of the saved search form, it - Second paragraph: To use the search conditions option, you must have add or edit permissions for Search and access to the Saved Searches Browser assigned to you through the Security page. See Workspace security. - Headings: H1: Search conditions | H2: Setting up search conditions | H3: Setting up search conditions in the Search panel | H3: Setting up search conditions in the Search browser | H3: Using the multiple object condition builder | H2: Canceling queries | H2: Frequently asked searching questions | H3: Multiple terms in dtSearch queries | H3: Proximity searches in dtSearch queries | H3: Using reserved characters in dtSearch queries | H3: Multiple conditions | H3: Nesting searches - [Search panel] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Search_panel.htm): Using the search panel, you can build complex searches using drag-and-drop to rearrange and visualize nested conditions. You can easily set conditions and drag and drop them into logic groups. The logic display at the top of the panel updates automatically to reflect your drag-and-drop changes. You can access your dtSearch and keyword search indexes and fields in the workspace when creating your search. - Second paragraph: Using the search panel, you can build complex searches using drag-and-drop to rearrange and visualize nested conditions. You can easily set conditions and drag and drop them into logic groups. The logic display at the top of the panel updates automatically to reflect your drag-and-drop changes. You can access your dtSearch and keyword search indexes and fields in the workspace when creating your search. - Headings: H1: Search panel | H2: Permissions | H2: Collapsing, expanding, and moving the search panel | H2: Condition card icons | H2: Using the auto-run search setting | H2: Creating a search in the search panel | H2: Applying logic groups to search conditions | H2: Navigating the search panel | H3: Copying conditions | H3: Toggling conditions on and off | H3: Expanding/collapsing cards | H3: Removing conditions - [Searching overview] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Searching.htm): Relativity includes flexible search features designed to facilitate the document review process. These easily accessible features support a range of searching needs from filtering on fields and simple keyword searches to the development of complex queries. The following list summarizes the searching features available in Relativity. - Second paragraph: See these related pages: - Headings: H1: Searching | H2: Filters | H2: Search panel | H2: Keyword searches | H2: Saved searches | H2: dtSearch | H2: Regular expressions | H2: aiR Assist | H2: Additional features - [Searching with the Entity object and name normalization] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Searching_with_the_Entity_object_and_name_normalization.htm): This topic describes the types of searches you can conduct using the Entity object and Name Normalization results. - Second paragraph: Note the following special considerations: - Headings: H1: Searching with the Entity object and name normalization | H2: Considerations | H2: Emails within a specific organization | H2: Communications between two specific individuals and no one else | H2: Communications between any two individuals and no one else | H2: Emails across entity metadata | H2: Emails sent from two different internal domains | H2: Emails someone sent to themselves | H2: Entities that communicated on privileged documents | H2: Emails where a specific person drops off of a communication - [Searching workflows] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Searching_workflows.htm): Relativity provides great flexibility to help you identify documents through searches so that you can ready them for further review and analysis. This recipe highlights some of that flexibility, such as setting up multiple search indexes, applying various search techniques, and using filters properly when executing searches. - Second paragraph: This topic highlights setting up multiple search indexes, applying various search techniques, and using filters properly when executing searches. - Headings: H1: Searching workflows | H2: Workflow details | H2: Best practices for advanced operators | H3: Proximity search | H3: Auto-Recognition | H3: Searching for times | H3: Filters | H3: Troubleshooting workflow ### Searching Quick Reference - [Advanced search quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Searching_Quick_Reference/Advanced_search.htm): This guide does not include analytics indexes and will not provide details on the operators suitable for use in these search engines. - Second paragraph: How is it enabled? - Headings: H1: Advanced search quick reference guide | H2: Common search scenarios | H2: Is Like and Contains operators on field level searching - [Search] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Searching_Quick_Reference/Search.htm): Use this search quick reference to improve your understanding of searching within Relativity. - Second paragraph: Date - Headings: H1: Searching quick reference guide | H2: Fields types and filter types | H2: dtSearch strings and operators | H2: dtSearch fuzzy searching and stemming | H2: Search operators and field types for saved searches - [Symbols] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Searching_Quick_Reference/Symbols.htm): Use the following table to quickly reference how to search for special characters. Note that you can search for the ampersand symbol without using RegEx. - Second paragraph: Update the alphabet file and use RegEx with the hexadecimal Unicode value. - Headings: H1: Symbols quick reference guide | H2: Common characters ### Security Center - [RelativityOne Security Center] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_Center/SecurityCenter.htm): RelativityOne Security Center - Second paragraph: These areas include: - Headings: H1: RelativityOne Security Center | H2: Permissions | H3: System administrators | H3: Client domain administrators | H2: Security Center dashboard | H2: User 2-factor authentication | H3: Notifying users who do not have 2-factor authentication (2FA) enabled | H3: Enforcing 2-factor authentication (2FA) | H2: Login map and activity details | H3: Login map controls | H3: Using the login map | H3: The Login Activity Details grid | H2: User activity | H3: Disabling users | H3: Deleting users | H2: Lockbox access | H2: JIT access detail behavior | H3: Viewing Relativity staff access to a workspace | H3: Removing Relativity staff access to a workspace | H2: Relativity employee workspace access | H3: Access data columns | H2: Threat Intel - [Security Alerts] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_Center/Security_Alerts.htm): The Security Alerts interface shows recent events that may impact the security of your instance. These events can be sorted, filtered, and viewed in detail in order to assess their impact. In addition, the Alert Details section provides recommended remediation steps tailored to each alert type. - Second paragraph: See the following related pages: - Headings: H1: Security Alerts | H2: Security alert types | H2: Alert severity levels | H2: Security alert states | H3: Dismissing Alerts | H3: Resolving Alerts and Automated Remediation | H3: Moving Alerts back to Unresolved | H3: Tracking State Change History | H2: Alert Timelines section | H3: Alert Type and Level graph | H2: Alert Details section | H3: Summary tab | H3: Events tab | H3: Remediation Steps tab | H2: Security Alerts grid | H3: Alert Notifications tab - [Security Best Practices] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_Center/Security_Best_Practices.htm): To assist client System Administrators with maintaining a secure environment, the Security Configurations tab of Security Center evaluates and displays alignment with various security best practices. Each best practice focuses on a client-controlled configuration which impacts the environment’s overall security posture. - Second paragraph: Progress towards meeting all best practices is shown at the top of the tab as a progress bar for quick assessment. - Headings: H1: Security Best Practices | H3: 1. Reduce access users with basic authentication | H3: 2. Passwords have a minimum required length | H3: 3. Previous passwords cannot be reused within a secure limit | H3: 4. The AdminsCanSetPasswords Instance Setting is False | H3: 5. Reduce the number of inactive user accounts | H3: 6. Prevent unauthorized data access via Lockbox Controls | H3: 7. Security High and Critical alert types are reviewed | H3: 8. System Administrators are in the Security Notifications group ### Security permissions - [Feature permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Feature_permissions.htm): Relativity allows you to manage varying levels of security for users, systemadmins, and individual objects such as views, tabs, and fields, across your instance of Relativity and in each workspace. User access permissions are assigned at the group level, allowing you to quickly edit security for a number of users simultaneously. After configuring a group - Second paragraph: Features represent key system capabilities such as Preservation, Production, Imaging, and Configure Doc Review. Each feature groups together the necessary permissions from the three tabs. When you enable a feature, all related permissions are automatically applied. - Headings: H1: Feature permissions | H3: Currently modernized features | H2: Considerations | H2: Scenarios | H2: Using the Features tab | H2: Modernized feature permissions behavior | H2: Aligning permissions with modernized features (migration tooling) | H3: Identifying out-of-alignment permissions | H3: Aligning a group's permissions | H2: Frequently asked questions | H2: Workspace-level permissions | H2: Instance-level permissions - [Instance security] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Instance_security.htm): With instance security you can apply permissions to system admin groups to limit or grant access to particular system admin objects. You can access the Admin Security dialog from the Instance Details tab. - Second paragraph: See the following related pages: - Headings: H1: Instance security | H2: Features | H2: Object Security tab | H2: Tab Visibility tab | H2: Admin Operations tab | H3: A Note on View Admin Repository | H2: Group Permissions report | H3: Reading the Group Permissions Report | H2: Uneditable admin permission settings for the Everyone group | H2: Script and application library permissions | H2: System administrator privileges - [Permissions scenarios] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Permissions_scenarios.htm): In this topic, you can explore various scenarios that involve managing permissions. - Second paragraph: See the following related pages: - Headings: H1: Permissions scenarios | H2: Hierarchical structure | H2: Client domains | H2: User groups | H2: Template groups | H3: Review templates | H3: Investigation templates | H3: Early case assessment (ECA) templates | H3: Security workspace templates | H2: Object-level permissions | H2: Item-level permissions | H2: Document unitization | H3: Important considerations | H3: Deployment and configuration | H2: Scenarios | H3: Additive permissions and Staging Explorer across workspaces | H2: Frequently asked questions - [Preview security] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Preview_security.htm): The preview security feature allows system admins to interact with Relativity as if they are logged in as a specific user or a member of a specific group. This allows a system admin to more easily verify that the correct permissions are applied without logging in to Relativity under a different account. - Second paragraph: For example, say you secured a layout from a user and you want to verify that person no longer has access to the layout. With the preview security feature, you can select the user and view Relativity as that person right from your system admin account. - Headings: H1: Preview security | H2: Previewing security from the Workspace Details tab | H2: Previewing security from the Groups tab | H2: Previewing security from the Users tab | H2: Preview security audit - [Relativity object security] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Setting_permissions_on_Relativity_objects.htm): Individual items inherit their objects - Second paragraph: Say you have a group doing contract review, and you want the group to be able to see the custodian field, but not be able to edit it. You can customize object permissions to ensure users have view rights, and not edit rights to the custodian field object. - Headings: H1: Relativity object security | H2: Securing a folder for selected groups | H3: Folder security inheritance | H3: Identify and edit item-level security - [RelativityOne Lockbox] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Lockbox.htm): Customer lockbox. - Second paragraph: Lockbox also offers built-in alerting, providing notifications whenever access changes occur. This ensures you have full visibility into your tenant's security posture. - Headings: H1: RelativityOne lockbox | H2: Instance settings: | H2: Lockbox reports | H2: Lockbox security notifications - [Sanitizer object] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Sanitizer_object.htm): The Sanitizer object is a Relativity system object that stores the Sanitizer Whitelist information. The Sanitizer Whitelist is used to parse embedded HTML code in HTML-enabled and custom text fields and labels. - Second paragraph: The sanitization process parses HTML content located in “Message of the day” page, HTML enabled fields, labels and custom text fields on layouts, when rendered on user interface, strips any HTML markup which is not included in the allow list. - Headings: H1: Sanitizer object | H2: Sanitizer Allow list | H3: Modifying the allow list | H2: Sanitizer tab | H3: Adding the Sanitizer tab - [Security and Permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Managing_security.htm): Relativity allows you to manage varying levels of security for users, systemadmins, and individual objects such as views, tabs, and fields, across your instance of Relativity and in each workspace. User access permissions are assigned at the group level, allowing you to quickly edit security for a number of users simultaneously. After configuring a group - Second paragraph: Feature Permissions modernization: Learn how modernized Feature Permissions streamline permissions management by making the Features tab the primary way to grant or revoke access for supported features. Includes migration tooling and alignment guidance. - Headings: H1: Security and permissions | H2: Levels of Security in Relativity - [Setting instance permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Setting_instance_permissions.htm): Edit instance permission settings from the Instance Details tab. - Second paragraph: Edit instance permission settings from the Instance Details tab. Access Admin security with the following steps: - Headings: H1: Setting instance permissions | H2: Groups Management tab | H3: Add/Remove Groups | H2: Features tab | H3: Considerations | H3: Using the Features tab | H3: Frequently asked questions | H2: Object Security tab | H2: Tab Visibility tab | H2: Admin Operations tab - [Setting workspace permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Setting_workspace_permissions.htm): Edit workspace permissions using the Workspace Security dialog accessible from the Workspace Details tab. Access the dialog using the following steps in a workspace. - Second paragraph: Edit workspace permissions using the Workspace Security dialog accessible from the Workspace Details tab. Access the dialog using the following steps in a workspace: - Headings: H1: Setting workspace permissions | H2: Group Management | H3: Add/Remove Groups | H2: Saving permissions for a group | H2: Features tab | H3: Considerations | H3: Using the Features tab | H3: Frequently asked questions | H2: Object Security tab | H3: Assigning object-level permissions | H2: Tab Visibility tab | H3: Selecting parent and child tabs | H2: Other Settings tab - [Workspace security] (https://help.relativity.com/RelativityOne/Content/Relativity/Security_permissions/Workspace_security.htm): Relativity’s security rights are highly customizable. Each group you add to a workspace can have vastly different permissions than others. You can also copy an existing group’s permissions to save time on configuring them. - Second paragraph: When the Customer lockbox feature is enabled, Relativity system admins must also belong to a group within a workspace in addition to the System Administrators group to access and administer security within that workspace. Refer to Support if you need more information on this feature. - Headings: H1: Workspace security | H2: Workspace permissions | H3: Features | H3: Object security | H3: Object list | H3: Tab visibility | H3: Browsers | H3: Mass operations | H3: Admin operations | H2: Customer lockbox | H2: Workspace admin group ### Sentiment analysis - [Running sentiment analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/Sentiment_analysis/Running_sentiment_analysis.htm): Sentiment analysis is an artificial intelligence tool that scores documents on the likelihood that they contain negativity, anger, desire, or other emotions. Through this analysis, you can quickly and easily locate documents that show unusual or highly charged interactions between participants. - Second paragraph: By detecting unusual communications between key actors, you can locate communications that need further investigation and build deeper context around the conversations and ideas that are central to a case or matter. - Headings: H1: Sentiment analysis | H2: Installing Sentiment Analysis | H2: Running sentiment analysis | H3: Choosing the document set | H3: Running the sentiment analysis mass operation | H3: Reviewing sentiment analysis results | H2: Common ways to use sentiment analysis | H2: How sentiment analysis works | H3: Predictions versus certainty | H3: How emails are analyzed | H3: Sentiment list | H2: Language and culture considerations | H3: Addressing bias in sentiment analysis | H2: Best practices for interpreting results - [Sentiment analysis results] (https://help.relativity.com/RelativityOne/Content/Relativity/Sentiment_analysis/Sentiment_analysis_results.htm): After you have run sentiment analysis on a set of documents, the results are available as a set of fields attached to each document. These can be viewed either from the document list page or from the Sentiment Results tab. - Second paragraph: Similarly, information about each sentiment analysis run is recorded on the Sentiment Analysis Jobs tab. You can view all jobs together as a list, or view details of each individual job. - Headings: H1: Sentiment analysis results | H2: Adding results to the document view | H3: Filtering and sorting results | H2: Viewing the Sentiment Analysis Jobs tab | H3: Viewing job details | H2: Viewing the Sentiment Results tab | H3: Viewing results details | H2: Highlighting sentiments in the Viewer | H2: Troubleshooting sentiment analysis errors | H3: Job-level errors | H3: Document-level errors - [Sentiment analysis security permissions] (https://help.relativity.com/RelativityOne/Content/Relativity/Sentiment_analysis/Sentiment_analysis_security_permissions.htm): This topic contains information on the security permissions required for working with sentiment analysis. - Second paragraph: See these related pages: - Headings: H1: Sentiment analysis security permissions | H2: Running the sentiment analysis mass operation | H2: Viewing sentiment analysis jobs and results ### Short message search - [Creating a short message search] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Short_message_search/Creating_a_short_message_search.htm): After you build the short message search index, you can search it from the Documents tab. For more information on building the index, see Short message search index. - Second paragraph: To create a short message search: - Headings: H1: Creating a short message search | H2: Defining search criteria operators | H3: Long text operators | H3: Fixed-length text operators | H3: Date operators | H3: Whole number operators | H3: Yes/No operators | H2: Searchable fields - [Short message search] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Short_message_search/Short_message_search.htm): Short message search uses the short message search index which allows for a detailed search on RSMF documents by examining message-level metadata. For example, it helps to: - Second paragraph: Once messages are found, message-level coding can be performed on them in the Viewer if necessary. - Headings: H1: Using short message search | H2: Short message search workflow | H2: Short message terminology | H2: Considerations - [Short message search index] (https://help.relativity.com/RelativityOne/Content/Relativity/Searching/Short_message_search/Short_message_search_index.htm): Before you can begin searching short message data, you must build a search index. The index enables you to perform more complex searches on RSMF documents processed in Relativity. It provides enhanced accuracy by storing and searching on the message-level and event-level metadata by using Elasticsearch. - Second paragraph: Once the index is built, you can begin using the short message search feature. For more information on searching short message metadata, see Using short message search. - Headings: H1: Building a short message search index | H2: Installing the Search AI application | H2: Building the full index | H2: Running incremental index builds | H2: Automating incremental index builds using Automated Workflows | H2: Retry errors | H2: Eventing ### Simple File Upload - [Simple file upload] (https://help.relativity.com/RelativityOne/Content/Relativity/Simple_File_Upload/Simple_File_Upload.htm): Simple File Upload, formerly Single File Upload, gives users the ability to add new documents to Relativity without using the Relativity Desktop Client. - Second paragraph: Keep the following considerations in mind: - Headings: H1: Simple File Upload | H2: Special considerations | H2: Workspace security permissions | H2: Accessing Simple File Upload | H2: Uploading new documents | H2: Replacing documents ### Site Resources - [aiR Units in RelativityOne standard workspaces] (https://help.relativity.com/RelativityOne/Content/Site_Resources/aiR_Units_in_RelativityOne_Standard_Workspaces.htm): If your RelativityOne subscription includes aiR access and aiR Units in standard workspaces, the following products are currently available: - Second paragraph: For more details, see aiR Units, Thresholds, and Included Products on the Community. You must have valid Relativity Community credentials to access that content. - Headings: H1: aiR Units in RelativityOne standard workspaces | H2: Key definitions for standard workspaces with aiR | H2: Available aiR products included and the associated aiR Unit usage details | H2: How aiR Unit Analyses are counted | H3: How aiR for Review counts each aiR Unit Analysis | H3: How aiR for Privilege counts each aiR Unit Analysis - [Capabilities] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Products.htm): Describes the available capabilities and extend products in Relativity - Second paragraph: - Headings: H1: Capabilities | H2: Standard Capabilities | H3: Legal Hold | H3: Collect | H3: Purview Sync | H3: Processing | H3: Analytics & Assisted Review | H3: Production | H3: Review | H3: Supporting applications | H3: Mobile | H2: Extend Capabilities | H3: aiR for Privilege | H3: aiR for Review | H3: Contracts | H3: aiR for Data Breach Response | H3: Translate | H3: aiR for Case Strategy - [Certification exam resources] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Certification_exam_resources.htm): Find links to documentation resources for each of our certification exams. - Headings: H1: Certification exam resources - [Data transfer] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Data_transfer.htm): Data transfer refers to moving your case data from one environment to another environment. This can be transferring your data between Relativity instances or from a legacy system. Relativity provides you with a suite of tools that can help you with this. - Second paragraph: Before anyone in your organization can transfer data, you should ensure that your network and firewall settings have been configured correctly. See RelativityOne network access in the RelativityOne technical overview. - Headings: H1: Data transfer | H2: Data transfer considerations | H2: Data transfer network considerations | H2: Data transfer workflows in RelativityOne | H3: Workflow 1: Loading processed and unprocessed data directly into RelativityOne using Import/Export with Express Transfer (recommended) | H3: Workflow 2: Loading processed and unprocessed data directly into RelativityOne using Import/Export with Express Transfer from the Utility Server | H3: Workflow 3: Loading processed data to the staging directory and then into RelativityOne | H3: Workflow 4: Loading unprocessed data to your RelativityOne staging directory for processing | H3: Workflow 5: Migrating case data to the staging directory into RelativityOne - [Knowledge base] (https://help.relativity.com/RelativityOne/Content/Site_Resources/RecipesHome.htm): Relativity - Second paragraph: You must have valid Relativity Community credentials in order to download any Community file linked to the documentation site. You'll need to enter those credentials on the Community login screen if you're not already logged in. If you're already logged in to the Community at the time you click a link, the file is automatically downloaded in the bottom left corner of your screen. If you get an error message stating "URL No Longer Exists" after clicking a Community link, it may be due to a single sign-on error related to the SAML Assertion Validator, and you should contact your IT department. - Headings: H1: Knowledge base | H2: Conceptual Analytics | H2: Legal Hold | H2: Non-English Languages | H2: Processing | H2: Production | H2: Review | H2: Review Center | H2: Searching | H2: Structured Analytics | H2: Workspace Administration - [Production] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Production.htm): Relativity helps make your production process fast and easy by creating custom workflows to meet the needs of each unique case. - Second paragraph: Run a production - Headings: H1: Production - [Quick reference guides] (https://help.relativity.com/RelativityOne/Content/Site_Resources/User_quick_reference.htm): Use these quick reference guides to quickly access information about the following topics. - Headings: H1: Quick reference guides | H2: Product quick reference guides - [Relativity A-Z] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Relativity_A-Z.htm): This page contains an alphabetical list of features available on the documentation site. - Headings: H1: Relativity A-Z | H2: A | H2: B | H2: C | H2: D | H2: F | H2: G | H2: I | H2: K | H2: L | H2: M | H2: O | H2: P | H2: Q | H2: R | H2: S | H2: T | H2: U | H2: V | H2: W - [Resources] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Resources.htm): In addition to the documentation on this site, Relativity provides a host of resources to help you use Relativity and its applications. - Second paragraph: Relativity provides video tutorials to teach you the basics of Relativity and its features. You can find the tutorials on Relativity's website. - Headings: H1: Resources | H2: Tutorials | H2: Relativity Community | H2: Relativity Support team - [Review] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Review.htm): Relativity helps make your review process fast and easy by creating custom workflows to meet the needs of each unique case. - Second paragraph: - Headings: H1: Review - [Solutions, Recipes, and White Papers] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Solutions.htm): Customize and optimize your Relativity environments using these solutions and custom recipes. - Second paragraph: Visit the Community site to explore the full library of knowledge base articles, discuss workflows, and connect with other Relativity Community members. - Headings: H1: Solutions, knowledge base, and white papers | H2: Solving review case challenges with Analytics | H2: Relativity Community site | H2: Relativity white papers - [Supporting applications] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Supporting_Applications.htm): RelativityOne provides you with additional tools to customize your e-discovery platform needs from beginning to end. Follow the links below to learn more about RelativityOne's supporting applications. - Second paragraph: Relativity Case Dynamics, formerly Fact Manager, assists in organizing and analyzing case details such as facts, issues, organizations, people, interview questions, and documents. This analysis helps identify strengths and weaknesses in litigation strategy and leads to better preparation for depositions, interviews, and trial. - Headings: H1: Supporting applications - [Using this site] (https://help.relativity.com/RelativityOne/Content/Site_Resources/Using_this_site.htm): Whether you - Second paragraph: Whether you're a reviewer, system admin, or IT specialist, this site and the information within it is designed to meet your needs. Key information includes: - Headings: H1: Using this site | H2: Search features | H2: Version switcher | H2: Toolbar buttons | H2: Support for smaller screens and devices | H2: Drop-down text | H2: Heading Hyperlinks | H2: Feedback form ### Solutions - [Recommendations for managing large and very large workspaces in RelativityOne] (https://help.relativity.com/RelativityOne/Content/Solutions/Recommendations_for_managing_very_large_workspaces_in_RelativityOne.htm): The management of very large and complex workspaces requires an advanced level of knowledge and expertise as these workspaces generally bring a new set of challenges and potential complications. As an administrator, you should know the best approach for identifying and addressing performance and workflow complications that may arise when managing very large or complex workspaces in RelativityOne. - Second paragraph: A workspace qualifies as a large and complex matter when it meets any of the following thresholds. For such workspaces, please request a project scoping call via the Incoming Project Details: RelativityOne form available on the Community site: - Headings: H1: Recommendations for managing large and very large workspaces in RelativityOne | H2: What's New, Release Notes, and Known Issues | H2: Identifying a need to scale and RelativityOne’s automated response | H2: Proactive Monitoring of RelativityOne Environments | H2: Contacting RelativityOne in advance for upcoming large and complex projects - [Reviewing documents in Relativity] (https://help.relativity.com/RelativityOne/Content/Solutions/Reviewing_documents_in_Relativity.htm): This guide walks you through a generic workflow for a first-pass review. To start your first-pass review, log in to Relativity by browsing to your Relativity website. The login screen appears and you can enter your email address and password. After logging in to Relativity, a list of workspaces you have access to appears. To access workspace documents, click on the name of the relevant workspace. The workspace opens with a list of available documents and you can begin your review. - Second paragraph: See these related pages: - Headings: H2: Accessing documents | H2: Coding documents | H3: Coding permissions | H3: Working with layouts | H3: Using the Viewer - [Supported languages matrix] (https://help.relativity.com/RelativityOne/Content/Solutions/Supported_languages_matrix.htm): This table displays each language supported by a Relativity feature and its corresponding functionality status. The features include OCR, Relativity Assisted Review, Structured Analytics, Processing, and the Viewer. Stemming, date recognition, and querying on abbreviations (i.e., a single letter followed by a period) are only available in English text in a dtSearch index. The SQL Server settings determine the languages available for word-break characters used in the full text index. - Second paragraph: Use the following resources for more information on SQL Server and dtSearch supported languages: - Headings: H2: Special considerations | H2: Language support in aiR products | H2: Language support in AV transcription | H2: Supported languages - [Workflow solutions for very large workspaces] (https://help.relativity.com/RelativityOne/Content/Solutions/Workflow_solutions_for_very_large_workspaces.htm): Very large Relativity workspaces (VLRWs) require a great deal of time and effort to maintain. As a result, it’s important to develop a plan to accommodate the workflow before your workspace reaches VLRW status. Making workflow changes after this point is inefficient and can be very time consuming. - Second paragraph: Use the following best practices to plan your VLRW workflow and improve overall performance. These guidelines can also be a helpful starting point for educating Relativity users. This guide also outlines the best practices for setting up and working in VLRWs. - Headings: H1: Workflow solutions for very large workspaces | H2: Workspace Administration and Optimization | H3: Workspace size and activity factors | H3: Fields | H3: Folders | H3: Index management | H3: Automated Workflows | H3: Search terms reports | H3: Persistent highlight sets | H3: Layouts | H3: Mass Operations | H3: Security Permissions | H3: Snapshot auditing | H3: Views | H3: Relativity system admins | H2: Ingestion, Data Management, Data Migration | H3: Processing | H3: Importing load-ready data | H3: Relativity Integration Points | H3: RelativityOne Data Migration | H2: Analysis and Review | H3: Searching | H3: Reviewer statistics script | H3: Review Center | H3: Relativity Short Message Format | H3: Conceptual Analytics | H3: Translate | H3: Redact | H2: Productions | H3: Exporting data using Import/Export | H3: Production scripts ### Solving review case challenges with Analytics - [Implementing clustering with batching] (https://help.relativity.com/RelativityOne/Content/Solutions/Solving_review_case_challenges_with_Analytics/Implementing_clustering_with_batching.htm): The steps required to complete a large document review with limited time and limited access to subject matter experts involve creating document clusters automatically with Analytics, followed by batching documents for review based on the resulting clusters. The following sets of steps explain how to. - Second paragraph: You must have an Analytics index in order to use clustering. For information on creating an Analytics index, see Analytics indexes. - Headings: H1: Implementing clustering with batching | H2: Creating clusters | H3: New fields | H2: Creating batches from clusters | H3: Creating a new saved search | H3: Creating a new batch set | H2: Assigning and coding - [Solving review case challenges with Analytics] (https://help.relativity.com/RelativityOne/Content/Solutions/Solving_review_case_challenges_with_Analytics/Solving_review_case_challenges_with_Analytics.htm): Relativity Analytics allows you to speed up review and identify critical documents in a case by searching and quickly organizing document sets. Search results depend on how and where similar ideas and concepts in a document collection intersect. You can leverage Analytics throughout the review workflow to go faster and work smarter. - Second paragraph: See these related pages: - Headings: H1: Solving review case challenges with Analytics | H2: Getting started with Analytics | H2: Going faster with Analytics | H3: Reviewing documents under time and SME constraints | H3: Identifying and prioritizing the opposition’s hot documents | H2: Working smarter with Analytics | H3: Identifying additional privileged documents prior to production | H3: Identifying unknown relevant terms | H2: Analytics resources | H3: Documentation | H3: Educational resources | H3: Support team ### Staging - [Staging Inventory Report] (https://help.relativity.com/RelativityOne/Content/Management_Console/Staging/StagingInventoryReport.htm): This topic has been deprecated as of 9/30/24. You will be re-directed to Staging Reports. - Headings: H1: Staging Inventory Report - [Staging Reports] (https://help.relativity.com/RelativityOne/Content/Management_Console/Staging/Staging_Reports.htm): Administrators can access Staging Reports from the Management Console. With the correct permissions, System Administrators and Client Domain Administrators can create CSV reports on any of the four Staging folders and subfolders, detailing the number and size of files and folders. Additionally, they can monitor and download reports from the Report List. - Second paragraph: Both reports contain data from the following Staging Allowance folders: - Headings: H1: Staging reports | H2: Access and role functionality | H2: Considerations | H2: Security permissions | H2: Generating custom reports | H3: Billable summary reports | H3: Staging report CSV output ### Tab QRG - [Tab navigation quick reference guide] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Tab_QRG/Tab_navigation.htm): Use this guide to understand tab navigation in Relativity's Aero user interface. - Second paragraph: The tab is added to the Sidebar and will display based on the number of tabs you have already created and the size of your currently opened browser. If the vertical resolution is not high enough, the tab will display in the More menu. - Headings: H1: Tab navigation quick reference guide | H2: Navigation features | H2: Show a tab in the sidebar ### Tab Sync - [Tab Sync] (https://help.relativity.com/RelativityOne/Content/Relativity/Tab_Sync/Tab_Sync.htm): Tab Sync allows system administrators to specify a source template (e.g., an existing workspace) for their tab navigation structure, and then apply that template across multiple destination workspaces quickly and efficiently. - Second paragraph: See Tabs. - Headings: H1: Tab Sync | H2: Tab Sync considerations | H3: Tab Sync limitations | H2: Installing Tab Sync | H2: Running a Tab Sync job workflow | H2: Selecting a source template | H3: Workspace source template | H3: Tab Profile source template | H2: Choosing sync settings | H2: Selecting a destination workspace | H2: Removing a destination workspace | H2: Previewing changes to each destination workspace | H2: Email summary report | H2: Tab Sync errors and troubleshooting ### Transcripts application - [Annotating transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Annotating_transcripts.htm): When you open a transcript in the Viewer, you can add the following annotations: Notes, Designations, Exhibits, URLs. - Headings: H1: Annotating transcripts - [Copying text from a transcript] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Copying_text_from_a_transcript.htm): You can copy transcript text with or without page:line numbers with the Transcripts application. - Headings: H1: Copying text from a transcript - [Installing the Transcripts application] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Installing_the_Transcripts_application.htm): This page provides instructions for how to install the Transcripts application. - Headings: H1: Installing the Transcripts application - [Printing transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Printing_transcripts.htm): This page provides instructions for how to print transcripts from the Viewer. - Headings: H1: Printing transcripts - [Supported file types for the Transcripts application] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Supported_file_types_for_the_Transcripts_application.htm): Transcripts provides the capacity to upload the following file types: .ptf, .xmptf, .rtf, .trn, .lef, .xmef, .txt, xmp4. - Headings: H1: Supported file types for the Transcripts application - [Transcript reports] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Transcript_reports.htm): You can export the different annotations and items that have been linked to the transcript(s), including Case Dynamics items. - Headings: H1: Transcript reports - [Transcript video clips] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Transcript_video_clips.htm): You can create, save, merge, and export video clips with the transcripts application. - Headings: H1: Transcript video clips - [Transcripts application] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Transcripts_application.htm): The Transcripts application gives users the ability to upload, review, code, and annotate transcript files in Relativity. - Headings: H1: Transcripts application - [Transcripts tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Transcripts_tab.htm): The Transcripts tab contains individual tabs with views for Notes, Exhibits, URLs, Comments, Designations, and Designation types. - Headings: H1: Transcripts tab - [Uploading transcripts] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Uploading_transcripts.htm): When uploading Transcripts, Relativity automatically creates folders named after the Deponent Name field. Transcripts are stored in these folders, along with any corresponding attachments. - Headings: H1: Uploading transcripts - [Word index] (https://help.relativity.com/RelativityOne/Content/Relativity/Transcripts_application/Word_Index.htm): The Word Index lists out all the different terms that are found in the transcript. - Headings: H1: Word Index ### Translate - [Translate] (https://help.relativity.com/RelativityOne/Content/Relativity/Translate/Translate.htm): With Translate, you can select a set of documents that are in different languages and translate them to another language to support searching and review workflows. You can also translate a single document from the Viewer. For dozens of file types, including Microsoft Office files and PDFs, you can receive a translation in the native format of the document where supported, along with the translated extracted text. After successfully starting a Translate job, you will receive an email notifying you when it has completed along with a link to the translated documents. - Second paragraph: Each document that is successfully processed for translation is charged to you individually. Each errored document will not incur any charge to you. Translated documents can then be viewed in either the native format or the translated language in the Translation Viewer. - Headings: H1: Translate | H2: Translate requirements | H2: Installing the Translate application | H2: Translate permissions | H2: Translating multiple documents | H2: Translating a single document | H2: Fields | H3: Populated fields | H2: Working with translated documents | H2: Re-translating documents | H2: Mass exporting translated documents | H2: Viewing a job's status and usage | H2: Supported languages | H2: Troubleshooting Translate jobs | H2: Deployment and processing geographies ### Viewer - [aiR for Review Analysis] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/aiR_for_Review_Analysis.htm): Once you have run aiR for Review on a set of documents, you can open a document in the Viewer and see the aiR results highlighted as well as analysis for each one that explains why it might and might not be relevant to your case. This information helps you make decisions on what documents are useful as part of the review process. To learn more, see aiR for Review. - Second paragraph: The following permissions are required to use aiR for Review Analysis: - Headings: H1: aiR for Review Analysis | H2: Permissions | H2: Reviewing aiR for Review Analysis results | H2: aiR for Review Analysis highlighting | H2: aiR for Review Analysis results order - [Document Comments] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Document_Comments.htm): You can create comments that are visible to other users to share information with them in the Native Viewer while reviewing AV files with transcripts and documents that display native, searchable text such as an email, Word document, PowerPoint file, and other text documents. To learn more about AV documents, see AV transcription in the Viewer. - Second paragraph: Reviewers can also respond to comments which empowers case team collaboration. If there are comments on an AV file or text-based document, an orange circle displays on the Comments icon. Comments can be searched to make locating them easy and you can edit any comments that you have created as well. - Headings: H1: Document Comments | H2: Permission | H3: Comments searching | H3: Adding a comment | H3: Replying to a comment | H3: Editing a comment | H3: Deleting a comment - [Document compare] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Document_compare.htm): You can use Document Compare to view the key differences between the extracted text of two documents. To access the Document Compare system field, you must first add it to a view. - Second paragraph: To compare two documents in Relativity from the document list: - Headings: H1: Document Compare - [Markups] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Markups.htm): Markups in Relativity refer to highlights and redactions. You can add markups to documents using the Relativity image viewer. When you open a document in the core reviewer interface, select Image to image the document if necessary and open the document as an image. - Second paragraph: If two people edit a markup at the same time, an error occurs. - Headings: H1: Markups | H2: Permissions | H2: Highlights | H3: Creating highlights | H2: Redactions | H3: Creating basic redactions | H3: Creating inverse redactions | H3: Creating full-page redactions | H3: Creating mass redactions | H2: Editing markups | H2: Deleting markups | H3: Working with overlapping markups | H3: Working with markups outside of page boundaries | H3: Editing redaction text with a markup set | H3: Editing redaction text | H3: Editing font size in text box redactions | H2: Mass deleting markups | H2: Controlling markup visibility | H2: Viewing markup history | H2: Using the Markup Navigation pane | H2: Reviewing markups using Redact - [Running conceptual analytics from the viewer] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Running_conceptual_analytics_from_the_viewer.htm): You can run conceptual analytics operations (categorization, concept search, keyword expansion, and find similar documents) directly from the viewer as long as the following conditions are met: - Second paragraph: See these related pages: - Headings: H1: Running conceptual analytics from the viewer | H2: Permissions and special considerations | H2: Running a concept search from the viewer | H2: Running find similar documents from the viewer | H2: Running keyword expansion from the viewer | H2: Navigating results | H3: Changing the active index - [Sentiment analysis highlights] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Sentiment_analysis_highlights.htm): Sentiment analysis highlights allow you to use artificial intelligence to identify emotionally charged statements in the Native and Extracted Text Viewer, including the Document preview panel. Sentiment analysis identifies documents that contain negativity, anger, desire, or other emotions and highlights the emotional statements in the Viewer. To begin using this feature, you must first run the Detect Sentiment mass operation. For more information, see Running sentiment analysis. - Second paragraph: The following permission is needed to see sentiment analysis highlights in the Viewer: - Headings: H1: Sentiment analysis highlights | H2: Permissions | H2: Utilizing sentiment analysis highlights - [Short Message Viewer] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Short_Message_Viewer.htm): The Relativity Short Message Viewer displays conversations or individual messages sent using SMS such as iMessage and instant messenger services such as Skype Messenger, Slack, and Bloomberg. - Second paragraph: Using the Viewer's built-in search capabilities, the Short Message Viewer allows you to find participant names, specific statements, or emojis in conversations. Additionally, you can easily find what was said during a particular time period by using the Timeline Navigator. - Headings: H1: Short Message Viewer | H2: Permissions | H2: Short Message Viewer | H3: Short Message Viewer toolbar options | H3: Left drawer Short Message Viewer options | H2: Navigating the Short Message Viewer | H3: Platform Icon | H3: Conversation Pane | H3: Navigating the Conversation | H3: Viewer interface for missing information | H3: Troubleshooting attachments | H3: RSMF Slicing | H3: Timeline Navigator | H3: Copying text in the viewer | H3: Audit Records | H3: Adjusting the Time Zone in Short Message Viewer | H2: Short Message Image Viewer | H2: Navigating the Short Message Image Viewer | H3: Short Message Report and Outline of Conversations | H3: Navigating the conversation | H3: Short Message Image Viewer interface for missing information | H2: Extracted Text Viewer - [Viewer] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Viewer.htm): Relativity - Second paragraph: Using your internet browser to zoom to any size other than 100% while using the Viewer is not supported and can cause unexpected behavior. - Headings: H1: Viewer | H2: Native Viewer | H3: Navigating the Native Viewer | H3: Copying text in the Viewer | H3: Streaming audio and video files | H3: Document Intelligence | H2: Image Viewer | H3: Navigating the Image Viewer | H3: Saving an image as a PDF | H2: Extracted Text Viewer | H3: Navigating the Extracted Text Viewer | H3: Extracted Text Viewer toolbar options | H3: Left drawer Viewer options | H3: Right drawer Viewer options | H3: Document actions menu | H3: Viewer settings menu | H3: Viewer breadcrumbs | H2: Productions Viewer | H3: Navigating the Productions Viewer | H3: Imaging on the fly | H2: PDF Viewer | H3: PDF Viewer toolbar options | H3: Left drawer Viewer options | H3: Right drawer Viewer options | H3: Document actions menu | H3: Viewer settings menu | H3: Viewer Breadcrumbs | H2: Document actions menu | H2: Viewer settings menu | H2: Pop Out Viewer | H3: Standalone Viewer | H3: Document preview panel | H2: Related items card | H3: Document actions in the related items card | H2: Document and Production History card | H3: Document and Production History card permissions | H2: Documents card | H3: Email thread visualization tool | H2: .eml and .msg header dates and times in the Viewer | H2: Thumbnail Viewer - [Viewer precedence] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Viewer_precedence.htm): Using the ReviewInterfaceViewerOrderPrecedence instance setting, you can determine the order of which Viewers display first in the Review Interface for your entire instance. Viewer precedence lets system admins or project managers configure the Review Interface to automatically switch Viewers based on whether or not a document is present in the Viewer. This reduces the number of clicks needed to review documents and saves time switching between different Viewers. For example, you can set the Viewer precedence to the Image Viewer so that when you're reviewing imaged documents with the occasional native spreadsheet document without images, the Viewer will load the Image Viewer first and only switch to the Native Viewer when an image isn't present to speed up your review time. - Second paragraph: The ReviewInterfaceViewerOrderPrecedence setting does not hide Viewers but instead helps you create an order to which Viewers display first, depending on which are available and the type of document you are opening. While you can enter a single value to prioritize that Viewer above the rest, you can also enter several Viewers in an order to determine a Viewer precedence. For example, if you enter native, image, text, then the Native Viewer will open first if a native document exists. If a native doesn't exist, then the Image Viewer will display first. If the document does not have a native or an image, the Text Viewer will display first instead. - Headings: H1: Viewer precedence - [Viewer troubleshooting and FAQ] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Viewer_troubleshooting_and_FAQ.htm): You can use the following information to learn about potential errors when attempting to access a document in the Viewer. Where possible, ideas for how to troubleshoot and resolve issues are also provided. If you have questions or need assistance after following the troubleshooting information provided below, please contact Relativity Customer Support. - Second paragraph: If a document does not load correctly, you can modify the user's permissions or try accessing a folder on the document list. If neither of those strategies work, we recommend clearing your internet browser's cache. The Settings menu has browsing data for most browsers. You can often find an option to remove cached images or files there. There is no need to clear cookies or your browser history. - Headings: H1: Viewer troubleshooting and FAQ | H2: General Viewer troubleshooting | H3: What can you do if a document is not loading? | H3: What browser settings can cause Viewer performance issues? | H3: What prevents a document from being downloaded? | H3: How can I disable Viewer extensions to troubleshoot performance issues? | H2: Troubleshooting Viewer errors | H2: Short Message Viewer troubleshooting | H3: Why are images not displayed in-line within the Native Short Message Viewer? | H3: How do I resolve common error messages received from the RSMF Validator located in the Short Message Viewer? | H2: PDF Viewer troubleshooting | H3: What won’t a PDF load? | H2: Excel troubleshooting | H2: Persistent highlighting in the Viewer | H3: Highlight terms are missing in either the Native or Extracted Text Viewer but the text exists on the Extracted Text or Native Viewer. - [Viewer-supported file types] (https://help.relativity.com/RelativityOne/Content/Relativity/Viewer/Viewer-supported_file_types.htm): This is a sample page that shows the new supported file types formatting. - Second paragraph: When converting email file types such as EML, the Viewer will not download images from the internet. Any linked images will display as a gray box in the Viewer. - Headings: H1: Viewer-supported file types | H2: Viewer audio and video-supported file types | H2: Troubleshooting errors | H2: Supported audio file types | H2: Supported video file types | H2: Text-only designation | H2: File ID only designation ### What s New - [In-App What's New Notifications] (https://help.relativity.com/RelativityOne/Content/What_s_New/What_s_New_feature.htm): The What’s new in RelativityOne feature lists new and noteworthy updates and enhancements. You can access the What's New listing directly from within RelativityOne. - Second paragraph: Upon logging into RelativityOne, you will see a megaphone icon in the header, indicating that are new What’s New notifications to read. - Headings: H1: In-App What's New Notifications | H2: How does it work? | H2: Who sees these updates? | H2: When will these What’s New notifications be posted? - [Known issues] (https://help.relativity.com/RelativityOne/Content/What_s_New/Known_issues_list.htm): The following list provides descriptions of known issues in Relativity. For a current list of Relativity enhancements and resolved issues, please visit the Relativity release notes on the help site. - Second paragraph: The known issues list receives updates when the following occurs: - Headings: H1: Known issues - [Known issues] (https://help.relativity.com/RelativityOne/Content/What_s_New/KnownIssuesArchive.htm): The following list provides descriptions of known issues in Relativity. For a current list of Relativity enhancements and resolved issues, please visit the Relativity release notes on the help site. - Second paragraph: Relativity publishes known issues to provide transparency and to give you the information you need when making upgrade decisions. Relativity Customer Support and Engineering publishes known issues at its own discretion based criteria such as on the number of customer reports, the severity of the issue, and the availability of a workaround. Not all defects are published as known issues. - Headings: H1: Known issues archive (2016-2020) - [RelativityOne Release Notes] (https://help.relativity.com/RelativityOne/Content/What_s_New/Release_notes.htm): The Release Notes summarize the changes that were made to RelativityOne. - Second paragraph: In the following table, click on any column heading to sort the column in alphanumeric order: - Headings: H1: RelativityOne release notes - [What's new] (https://help.relativity.com/RelativityOne/Content/What_s_New/What_s_new.htm): This page highlights selected new features in RelativityOne. - Headings: H1: What's new in RelativityOne - [What's new in RelativityOne] (https://help.relativity.com/RelativityOne/Content/What_s_New/What_s_new_in_RelativityOne.htm): Discover new features in RelativityOne that will help you tackle every phase of your e-discovery projects. - Second paragraph: The date shown represents when the feature or change is available in most Relativity environments. Due to differences in deployment and update schedules between regions or environments, the features listed may be available before the date shown or may not yet be available in all Relativity environments.For a full list of changes, please refer to the RelativityOne release notes**Indicates features that will be deployed using a Phased Rollout approach. - Headings: H1: What's new in RelativityOne | H2: Collect: New Collection Source - Claude Enterprise | H2: Permissions: Feature Permissions Modernization | H2: Collect: Collect OneDrive Data From Custodians’ Inactive Accounts | H2: PDF: Create Searchable PDFs From Non-Searchable Natives | H2: Data Transfer: New User Interface in ARM | H2: Legal Hold: Send communications from Service Accounts/Shared Mailboxes without logging In | H2: Permissions: Feature Permissions Modernization | H2: aiR for Review: Confidential Business Information Analysis | H2: Collect: Microsoft 365 Outlook Inactive Mailbox Connector | H2: aiR for Review: Introducing Granular User Permissions | H2: aiR for Case Strategy: Fact Editing in Fact Navigator | H2: aiR for Review: Increased Prompt Kickstarter Limits | H2: User Interface Updates | H2: aiR for Data Breach Response: PI Detection and PI-to-Entity Linking | H2: aiR for Review: Document Summaries | H2: Data Transfer: Upload Azure Data to RelativityOne | H2: aiR for Case Strategy | H2: aiR for Case Strategy: Fact Navigator | H2: Data Transfer: Staging Area Permissions in Staging Explorer | H2: PDF Workflows: Integrate Automated Workflows with PDF Sets | H2: Collect: Purview Sync | H2: aiR for Review: Prompt Kickstarter for Issues | H2: PDF Workflows: Store PDFs with new PDF Sets | H2: aiR for Review: Project Sets | H2: Validate aiR for Review Prompt Criteria in Review Center | H2: PDF Workflows: Transparent Redactions on Stored PDF Downloads | H2: Processing: Office 2024 Impact on EML Appointment Files | H2: Processing: Support for HEIC File Type | H2: Data Management: Cold Storage determined based on Workspace State | H2: Review: Conditional Coding Rules | H2: aiR for Review: All Issues tab | H2: Collect: Google Gemini integration | H2: aiR for Review: Prompt-Kickstarter | H2: aiR for Review and aiR for Privilege: Improved performance | H2: Transcripts: A/V Transcription Viewer | H2: Review: Short Message Investigative Workflow | H2: Redact: Redact Markup Validation Workflow | H2: aiR for Review and aiR for Privilege Regional Expansion | H2: End of Processing and Imaging Support for Publisher Files | H2: aiR for Privilege: Accelerating Time-to-Results | H2: Review: Document Notes and Comments | H2: Processing: EDRM Message ID Hash | H2: Model Update for Relativity’s Generative AI Solutions | H2: Usage Reports: Run as Template | H2: Review Center: Queue Build Status Visibility | H2: Errors Tab Deprecation | H2: Relativity aiR for Review: Export Prompt - [What's new in RelativityOne Government] (https://help.relativity.com/RelativityOne/Content/What_s_New/What_s_new_in_RelativityOne_Government.htm): Learn about new or updated features that have recently been deployed to RelativityOne Government environments. - Second paragraph: The date shown represents when the feature or change is available in RelativityOne Government environments. Due to differences in deployment and update schedules between regions or environments, the features listed may be available before the date shown or may not yet be available in all RelativityOne Government environments. For a list of released or upcoming items, please refer to the RelativityOne release notes**Indicates features that will be deployed using a Phased Rollout approach. - Headings: H1: What's new in RelativityOne Government | H2: Collect: New Collection Source — Claude Enterprise | H2: PDF: Create Searchable PDFs From Non-Searchable Natives | H2: Collect: Collect OneDrive Data From Custodians’ Inactive Accounts | H2: Collect: Collect API Now Available | H2: Permissions: Feature Permissions Modernization | H2: Data Transfer: New User Interface in ARM | H2: Legal Hold: Send communications from Service Accounts/Shared Mailboxes without logging In | H2: Permissions: Feature Permissions Modernization | H2: Collect: Microsoft 365 Outlook Inactive Mailbox Connector | H2: aiR for Review: Introducing Granular User Permissions | H2: aiR for Case Strategy | H2: aiR for Review: Increased Prompt Kickstarter Limits | H2: User Interface Updates | H2: Data Transfer: Staging Area Permissions in Staging Explorer | H2: PDF Workflows: Integrate Automated Workflows with PDF Sets | H2: aiR for Review: Prompt Kickstarter for Issues | H2: PDF Workflows: Store PDFs with new PDF Sets | H2: aiR for Review: Project Sets | H2: Validate aiR for Review Prompt Criteria in Review Center | H2: PDF Workflows: Transparent Redactions on Stored PDF Downloads | H2: Processing: Office 2024 Impact on EML Appointment Files | H2: Management Console: Introducing Usage Reports | H2: Processing: Support for HEIC File Type | H2: Data Management: Cold Storage determined based on Workspace State | H2: Review: Conditional Coding Rules | H2: aiR for Review: All Issues tab | H2: Collect: Google Gemini Integration | H2: Transcripts: A/V Transcription Viewer | H2: aiR for Review: Prompt-Kickstarter | H2: Redact: Redact Markup Validation Workflow | H2: Review: Document Notes and Comments | H2: Processing: EDRM Message ID Hash | H2: Review Center: Queue Build Status Visibility - [What's new in RelativityOne Sandbox] (https://help.relativity.com/RelativityOne/Content/What_s_New/What_s_new_in_RelativityOne_Sandbox.htm): Learn about selected new or updated features that have recently been deployed to RelativityOne Sandbox environments. - Second paragraph: The date shown represents when the feature or change is available in RelativityOne Sandbox environments. Due to differences in deployment and update schedules, the features listed may be available before the date shown or may not yet be available in all Relativity Sandbox environments. Features deployed to Sandbox environments will be deployed to RelativityOne production environments at a future date, based on that feature’s release plan. This page highlights noteworthy enhancements and changes available in Sandbox environments; not all changes to Sandbox environments will be described in this topic.☑ – denotes features that have been deployed to RelativityOne Production environment. - Headings: H1: What's new in RelativityOne Sandbox | H2: Collect: Purview Sync | H2: Data Transfer: New ARM UI | H2: PDF Workflows: Store PDFs with new PDF Sets | H2: PDF Workflows: Transparent Redactions on Stored PDF Downloads | H2: Collect: Google Gemini Integration | H2: Processing: Cellebrite UFDR to RSMF Conversion | H2: Review: Conditional Coding Rules | H2: Processing: Support for HEIC File Type | H2: Data Management: Cold Storage determined based on Workspace State | H2: Transcripts: A/V Transcription Viewer | H2: Review: Document Notes and Comments | H2: Review: Short Message Investigative Workflow | H2: Redact: Redact Markup Validation Workflow | H2: Review Center: Queue Build Status Visibility ### White Papers - [Relativity White Papers] (https://help.relativity.com/RelativityOne/Content/Solutions/White_Papers/White_Papers.htm): These white papers explain various topics related to Relativity. ### Workspace security Quick Reference - [Workspace security quick reference] (https://help.relativity.com/RelativityOne/Content/System_Guides/User_quick_reference/Workspace_security_Quick_Reference/Workspace_security_quick_reference.htm): The Workspace security Quick Reference Guide (PDF) provides an overview of the security options and functions in a workspace. - Headings: H1: Workspace security quick reference | H2: Feature permissions view | H2: Groups permission view | H2: Object security permissions view | H2: Item overrides view | H2: Tab visibility | H2: Other settings ### Workspaces - [Cold Storage] (https://help.relativity.com/RelativityOne/Content/Relativity/Workspaces/Cold_Storage.htm): Cold Storage is a feature that allows you to archive inactive workspaces for long-term retention when they are not regularly accessed. By moving a workspace to Cold Storage, you can reduce storage costs for dormant cases while preserving the data. When the workspace becomes needed again, you can retrieve it from Cold Storage to return it to an active state for use. Cold Storage is ideal for cases on hold or near completion. It provides a lower-cost storage tier for inactive data, with the trade-off of limited accessibility until retrieval. You migrate workspaces to Cold Storage to archive them, retrieve workspaces to bring them back for use, and can delete workspaces after a minimum retention period in Cold Storage. - Second paragraph: Certain security permissions are required to migrate or retrieve workspaces to/from Cold Storage. These permissions involve both instance-level and workspace-level settings: - Headings: H1: Cold Storage | H2: Permissions | H2: Migrating a Workspace to Cold Storage | H2: Retrieving a Workspace from Cold Storage | H3: Key points about Cold Storage retrieval: | H2: Deleting a workspace from Cold Storage | H3: Key points about Cold Storage deletion: | H2: Frequently Asked Questions (FAQ) | H2: Troubleshooting Cold Storage Operations | H3: Additional Considerations - [Document and item list navigation] (https://help.relativity.com/RelativityOne/Content/Relativity/Workspaces/Workspace_navigation.htm): The workspace offers several ways to view documents and items. Using the Browsers panel, you can navigate from folder to folder to see the documents contained within each. The Document Preview panel allows you to view specific documents from the document list. Additionally, you can also sort and filter the document or item list based on any fields in the current view or using the search panel. - Second paragraph: For more information about workspace navigation, see the following pages: - Headings: H1: Document and item list navigation | H2: Browsers panel | H3: Document browser menu | H2: View bar | H2: Document Preview panel | H3: Navigating the Document Preview panel | H2: Item list | H3: Freeze and unfreeze columns in a list | H3: Copy column values | H3: Saving a search from the Documents tab | H3: Previewing a document | H3: Sorting - [Recycle Bin] (https://help.relativity.com/RelativityOne/Content/Relativity/Workspaces/Recycle_Bin.htm): With the Recycle Bin feature, you can recover deleted workspaces within a specified time-frame at no additional cost. It also provides a self-service option for restoring workspaces that have been accidentally deleted, which can minimize downtime and data loss. - Second paragraph: See these related pages: - Headings: H1: Recycle Bin | H2: Billing and permissions | H2: Moving to the Recycle Bin | H2: Managing workspaces in the recycle bin - [Repository Workspaces in RelativityOne] (https://help.relativity.com/RelativityOne/Content/Relativity/Workspaces/Repository_workspaces_in_RelativityOne.htm): When setting up a workspace for documents, it is useful to understand that RelativityOne provides administrators the flexibility to setup a workspace either as a regular workspace or as a repository workspace. - Second paragraph: This topic highlights some of the items that admins need to be aware of as they create the repository workspace in RelativityOne. It also covers how to prepare and handle the flow of data between the review and the repository workspaces. - Headings: H2: Setting up a repository workspace | H2: Example 1 | H2: Example 2 | H2: Special considerations - [Workspaces] (https://help.relativity.com/RelativityOne/Content/Relativity/Workspaces/Workspaces.htm): 003 - Second paragraph: At the workspace level, you can also define views, layouts, fields, and choices. These features streamline workflows, as well as simplify the processes for organizing and categorizing content. Views support filtering on item lists, while layouts, fields, and choices are used for categorizing documents. - Headings: H1: Workspaces | H2: Creating and editing a workspace | H2: Fields | H2: Viewing workspace details | H3: Deleting a workspace | H2: Using the utilities console | H3: System Settings | H2: Managing system keyboard shortcuts | H2: Viewing the personal items of workspace users | H2: Cold storage management | H2: Adding and editing production restrictions | H3: Managing production restrictions in templates | H2: Workspace admin group - [Workspaces Tab] (https://help.relativity.com/RelativityOne/Content/Relativity/Workspaces/Workspaces_tab.htm): 003 - Second paragraph: You can navigate between the instances seamlessly using single sign-on. - Headings: H1: Workspaces tab | H2: Using the Workspaces tab | H3: Common Workspaces tab icons and actions | H3: Managing your instance connections | H3: Creating a new workspace in one of your instances | H3: Searching for a workspace | H2: Workspaces security permissions | H2: Linking additional Relativity instances | H3: Linking to additional RelativityOne instance workspaces | H3: Linking to Relativity Server instance workspaces | H3: Required prerequisites for configuration | H3: Configuring your primary and duplicate RelativityOne instances ### Workstation Configuration - [Browser specific considerations] (https://help.relativity.com/RelativityOne/Content/System_Guides/Workstation_Configuration/Browser_specific_considerations.htm): Refer to the following browser specific considerations when using Relativity 9 cross browser. - Second paragraph: RelativityOne is not supported on a mobile browser. To use RelativityOne on a mobile device, please download the RelativityOne Mobile application. For more information, see RelativityOne's mobile experience . - Headings: H1: Browser-specific considerations | H2: Supported browsers | H2: Considerations for all browsers | H2: Changing the language settings in Chrome | H2: Using single sign-on (SSO) on a Mac in Chrome and Safari | H2: Pop-up blockers in Firefox | H2: Pop-up blockers in Safari | H2: Enable tabbing on a Mac in Safari or Firefox | H3: Safari | H3: Firefox - [User software requirements] (https://help.relativity.com/RelativityOne/Content/System_Guides/Workstation_Configuration/User_software_requirements.htm): This section outlines requirements and recommendations for a workstation used to access Relativity. - Second paragraph: RelativityOne supports the following operating systems: - Headings: H1: User software requirements | H2: Supported operating systems | H2: Supported browsers | H2: Hardware settings