RelativityOne - Admin Guide
RelativityOne - Admin Guide
For the most recent version of this document, visit our documentation website.
Table of Contents
1 Admin guide overview 28
1.1 Navigation 28
1.1.1 Logging in 28
1.1.2 Tab navigation 28
1.1.3 All tabs menu 31
1.1.4 Tab strip 32
1.1.5 User options 34
1.1.6 Resetting your password 39
1.1.7 Favorites 40
1.1.8 Quick nav 41
1.2 Logging into RelativityOne 42
1.2.1 Logging in to RelativityOne with a password 42
1.2.2 Password 42
1.2.3 Two-factor authentication 43
1.2.4 OpenID Connect 45
1.2.5 SAML 2.0 45
1.2.6 Creating or resetting a password 45
2 Relativity applications 47
2.1 System secured applications 47
2.1.1 Applications installed in the Application Library 47
2.1.2 Applications installed in workspaces 47
2.2 Relativity custom applications 48
2.3 Administering Relativity applications 48
2.4 Global applications 49
2.4.1 Viewing global applications 49
2.5 Exporting applications 50
2.5.1 Downloading application .rap files 50
2.5.2 Avoiding errors during application export 51
2.5.3 Application state settings on export 53
2.5.4 Exporting an application 53
2.6 Locking and unlocking applications 54
2.6.1 Locking an application 54
Admin Guide 2
2.6.2 Customizing locked applications 54
2.6.3 Modifying saved searches in a locked application 55
2.6.4 Unlocking an application 56
2.7 Installing applications 56
2.7.1 Installing applications to the Application Library 56
2.7.2 Pushing an application from the Application Library to a workspace 57
2.7.3 Installing applications to workspaces 57
2.8 Troubleshooting application installation errors 62
2.8.1 Installation error list 63
2.8.2 Resolving installation errors 63
2.8.3 Pre and Post Install event handler errors 64
2.8.4 Checking the error statuses 64
2.9 Uninstalling and deleting applications 64
2.9.1 Uninstalling applications 65
2.9.2 Deleting applications 72
2.10 Upgrading applications 72
2.10.1 Upgrading an application 72
2.10.2 Troubleshooting application upgrades 74
3 Authentication 76
3.1 Permissions 76
3.2 Authentication overview 76
3.2.1 Authentication methods 76
3.2.2 Authentication object model 77
3.2.3 Authentication object permissions 77
3.3 Configuring Relativity authentication 78
3.3.1 Creating authentication providers 78
3.3.2 Assigning a login method to individual users 78
3.3.3 Enabling RelativityOne Connect 78
3.4 Authentication provider settings 78
3.5 Managing user authentication methods 79
3.5.1 Invitation workflow 79
3.5.2 Manually setting passwords 83
3.5.3 OpenID Connect 83
3.5.4 SAML 2.0 84
Admin Guide 3
3.6 SAML 2.0 provider 84
3.6.1 Considerations 84
3.6.2 Configuring a SAML 2.0 authentication provider 84
3.6.3 Configuring specific SAML providers 85
3.7 OpenID Connect 91
3.7.1 Configuring an OpenID Connect authentication provider 91
3.7.2 OpenID Connect authentication provider flows 92
3.7.3 Just-in-time provisioning 92
3.7.4 Okta OpenID Connect 94
3.7.5 Relativity OpenID Connect 95
3.7.6 Microsoft Entra ID - OpenID Connect 97
3.8 OAuth2 clients 99
3.8.1 Creating or editing an OAuth2 client 99
3.8.2 Resetting a client secret 101
3.8.3 Deleting an OAuth2 client 102
Viewing an OAuth2 client audit history 102
3.9 RelativityOne connect 102
3.9.1 Enabling RelativityOne Connect 103
3.9.2 Connecting users to different instances 105
3.9.3 Navigating between instances 106
3.9.4 Billing information 106
3.10 SSO Troubleshooting console 106
3.10.1 Considerations 106
3.10.2 Viewing the SSO Troubleshooting console 106
3.11 Federated instances 107
3.11.1 Creating or editing a federated instance 107
3.11.2 Deleting a federated instance 109
Viewing a federated instance audit history 109
4 Batches 110
4.1 Batch fields in Relativity 110
4.2 Creating and editing batch sets 110
4.2.1 Batch Sets for Reviewers 111
4.2.2 Fields 111
4.2.3 Batch Set console 113
Admin Guide 4
4.2.4 Auto Batching Status 113
4.3 Deleting an individual batch 113
4.4 Deleting a batch set 114
4.5 Searching for documents not in existing batch sets 114
4.6 Assigning batches and checking batches in and out 114
4.6.1 Assign a batch or check a batch out 115
4.6.2 Reassign a batch or check a batch in 115
4.7 Building views for checked-out documents 115
4.7.1 Build a checked-out documents view 115
5 Choices 117
5.1 Accessing the Choice editor 117
5.1.1 Accessing the Choice editor from the Fields tab 117
5.1.2 Accessing the Choice editor from the Choices tab 117
5.1.3 Accessing the Choice editor from layouts 118
5.2 Permission considerations for the Choice editor 119
5.3 Adding choices 120
5.3.1 Adding a choice from the Fields tab 120
5.3.2 Adding a choice from the Choices tab 120
5.3.3 Adding a choice from a layout 121
5.3.4 Adding multiple choices 121
5.4 Editing choices 122
5.4.1 Editing choice names 122
5.4.2 Editing choice details 122
5.5 Choice detail fields 122
5.6 Deleting choices 124
5.7 Performing mass operations on choices 124
5.8 Organizing choices 125
5.8.1 Dragging and dropping choices 125
5.8.2 Alphabetizing choices 126
5.8.3 Reordering top level choices 126
5.9 Fields in workspaces 127
5.10 Admin choices 127
5.10.1 Admin fields 128
6 Clients 129
Admin Guide 5
6.1 Creating or editing a client 129
6.1.1 Fields 129
6.2 Enabling client domains on a client 129
7 Dashboards 131
7.1 Commonly-used dashboards 135
7.1.1 Communicators 137
7.1.2 Data Load QC 137
7.1.3 Database Stats 138
7.1.4 Document Characteristics 139
7.1.5 Review Prioritization 139
7.1.6 Review Progress/QC 140
7.1.7 Privilege Review/QC 141
7.1.8 Search Term Review 142
7.1.9 Pre-Production QC 143
7.1.10 Email Threading 144
7.1.11 Language Identification 145
7.1.12 Special considerations 146
8 Fields 147
8.1 Fields permissions 147
8.2 System fields 147
8.3 Creating and editing fields 149
8.4 Fields 149
8.4.1 Field information 149
8.4.2 Field settings 150
8.4.3 Advanced settings 152
8.4.4 List and Dashboard Settings 158
8.4.5 Choices 159
8.5 Field types 160
8.5.1 Fixed-length text 160
8.5.2 Long text 161
8.5.3 Date 161
8.5.4 Whole number 161
8.5.5 Decimal 161
8.5.6 Currency 161
Admin Guide 6
8.5.7 Yes/No 161
8.5.8 Single choice 162
8.5.9 Multiple choice 162
8.5.10 User 162
8.5.11 File 162
8.5.12 Single object 163
8.5.13 Multiple object 163
8.5.14 Fields and performance 163
8.5.15 Linking Fields to Field Categories 164
8.6 Applying propagation to documents 164
8.6.1 Propagating to documents in multiple groups 165
9 Field categories 167
9.1 Creating a field category 167
9.2 Viewing fields associated with a field category 167
9.3 Link a field or fields to a field category 168
9.4 Unlink a field or fields from a field category 169
10 Filters 170
10.1 Showing and hiding filters in the item list 170
10.2 Filter types 171
10.2.1 Using Boolean filters 172
10.2.2 Using numeric filters for numbers 172
10.2.3 Using List filters 173
10.2.4 Using date filters 175
10.2.5 Using multi-list filters 177
10.2.6 Using text box filters 180
10.2.7 Text box filter search examples 181
10.2.8 Using advanced text box filtering 183
10.3 Changing item sets per page 184
10.4 Saving filters as a search 184
11 Groups 185
11.1 System groups 185
11.2 Creating and editing groups 185
11.3 Fields 186
11.4 Adding users to groups 186
Admin Guide 7
11.5 Adding external users through groups 187
11.6 Adding or removing groups from a client domain 188
12 Imaging 190
12.1 Required security permissions for imaging 190
12.2 Troubleshooting imaging 190
12.3 Image on the fly 191
12.4 Mass image 191
12.5 Imaging profiles 191
12.5.1 Creating and editing an imaging profile 191
12.5.2 Fields 192
12.5.3 Native file imaging profile validation 200
12.5.4 Viewing imaging profile details 202
12.6 Imaging sets 203
12.6.1 Using imaging sets 203
12.6.2 Creating and editing an imaging set 203
12.6.3 Fields 204
12.7 Image upload 205
12.7.1 Required security permissions 206
12.7.2 Uploading an image 206
12.7.3 Audits for image upload 208
12.8 Application Field Codes 208
12.8.1 Application Field Codes in Relativity 208
12.8.2 Application Field Code formats 210
12.8.3 Creating or editing an Application Field Code 210
12.8.4 Fields 211
12.8.5 Linking an Application Field Code to a native imaging profile 212
12.9 Running an imaging set 212
12.9.1 Special considerations 212
12.9.2 Imaging Set console 213
12.9.3 Imaging profile caching 214
12.9.4 Password Bank 214
12.10 Monitoring imaging status 214
12.11 Imaging errors 216
12.11.1 Viewing imaging errors 216
Admin Guide 8
12.11.2 Imaging error scenarios 219
12.11.3 Error email notification 219
12.11.4 Retrying imaging errors 219
12.11.5 Password Bank in imaging workflow 220
12.12 Imaging Warnings 221
12.12.1 Special considerations 221
12.12.2 Imaging Warnings tab 221
12.12.3 All imaging warnings 223
12.12.4 Core Reviewer layouts 224
12.12.5 Re-imaging emails with tables 225
12.13 QC Review 227
12.13.1 Hiding images for QC 227
12.13.2 Releasing images 228
12.14 Imaging jobs in the Processing and Imaging Queue 230
12.15 Native imaging - dithering algorithm options 232
12.15.1 Dithering algorithm details 232
12.16 Imaging native types 245
12.16.1 Editing a native type 246
12.16.2 Generating a complete list of native types and their respective imaging engines 246
12.17 Supported file types for imaging 247
13 Instance Details tab 249
13.1 Security 249
13.1.1 Manage Permissions 250
13.1.2 Group Permissions Report 250
13.2 Message of the Day 250
14 Keyboard shortcuts 252
14.1 Keyboard shortcuts legend 252
14.2 Special considerations for keyboard shortcuts 253
14.3 Document field type shortcuts 254
14.4 Document choice shortcuts 254
14.5 Creating keyboard shortcuts 255
15 Layouts 256
15.1 Layouts permissions 256
15.2 Creating and editing layouts 256
Admin Guide 9
15.3 Layout Information fields 256
15.3.1 Changing layouts 258
15.4 Using the layout builder 259
15.4.1 Layout Options console 259
15.4.2 Creating and editing a layout group 260
15.4.3 Saving the layout 262
15.5 Adding a choice to a layout 262
15.6 Pop-ups on the layout 262
15.7 Adding and editing an object list 263
15.7.1 Adding and editing an object list 263
15.8 Adding fields and text 264
15.8.1 Layout options 265
15.8.2 Adding fields to a category 266
15.8.3 Removing fields from a category 267
15.8.4 Making a field one or two column 267
15.8.5 Making a field read-only 267
15.8.6 Other fields considerations 268
15.8.7 Field properties 268
15.9 Creating a new category 269
15.9.1 Adding and editing categories 269
15.9.2 Category properties 269
15.10 Copy from Previous 270
15.10.1 Adding the Copy from Previous toolbar 270
15.10.2 Using Copy from Previous 271
15.11 Using the rich text editor 272
15.11.1 Rich text editor features 273
16 Lists 276
16.1 Enabling lists on an object 276
16.2 Viewing items in a list 277
16.2.1 Incorporating a list of documents as a search criterion in a saved search 277
16.2.2 Creating a view from a saved list 277
17 Relativity Script Library 279
17.1 Analytics billable estimate 280
17.1.1 Special considerations 280
Admin Guide 10
17.1.2 Inputs 280
17.1.3 Results 281
17.2 Australian Document ID 281
17.2.1 Installing to the Relativity Script Library 281
17.2.2 Installing Australian Document ID application to a workspace 281
17.2.3 Running the solution 282
17.3 Billing statistics - case rollup 282
17.3.1 Inputs 282
17.3.2 Results 283
17.4 Billing statistics - users 287
17.4.1 Inputs 287
17.4.2 Results 287
17.4.3 Retrieving historical data 288
17.5 Choice field stratified sampling 288
17.5.1 Special considerations 289
17.5.2 Inputs 289
17.5.3 Results 289
17.6 Copy To Legacy Document Fields 290
17.6.1 Special considerations 290
17.6.2 Inputs 290
17.6.3 Results 290
17.7 Create sample set 290
17.8 Forgotten password reset audit 290
17.9 Globally administer keyboard shortcuts 290
17.9.1 Category 291
17.9.2 Special considerations 291
17.9.3 Inputs 291
17.9.4 Results 291
17.10 Propagate sent date to family documents 291
17.10.1 Special considerations 291
17.10.2 Inputs 292
17.10.3 Results 292
17.11 Billing statistics - RelativityOne - case rollup 292
17.11.1 Installation 293
Admin Guide 11
17.11.2 Inputs 293
17.11.3 Results 293
17.12 Report sample-based statistics 297
17.12.1 Report types 297
17.12.2 Inputs 298
17.12.3 Results 298
17.13 Reviewer statistics 298
17.13.1 Inputs 299
17.13.2 Results 299
17.14 Set duplicate flag field 301
17.14.1 Special considerations 301
17.14.2 Inputs 302
17.14.3 Results 302
17.15 Set extracted text size field 302
17.16 Set native file size field v4 302
17.16.1 Special considerations 303
17.16.2 Inputs 303
17.16.3 Results 303
17.17 Set production beg/end attach fields 303
17.17.1 Special considerations 303
17.17.2 Inputs 303
17.17.3 Results 304
17.18 Set Relativity folder path field 304
17.18.1 Special considerations 304
17.18.2 Inputs 304
17.18.3 Results 305
17.19 Upgrade legacy applications 305
17.19.1 Inputs 305
17.19.2 Results 306
18 Markups 307
18.1 Highlights 307
18.1.1 Creating highlights 307
18.2 Redactions 307
18.2.1 Creating basic redactions 307
Admin Guide 12
18.2.2 Creating inverse redactions 308
18.2.3 Creating full-page redactions 308
18.2.4 Creating mass redactions 309
18.3 Editing markups 309
18.4 Deleting markups 310
18.4.1 Working with overlapping markups 310
18.4.2 Working with markups outside of page boundaries 311
18.4.3 Editing redaction text with a markup set 312
18.4.4 Editing redaction text 312
18.4.5 Editing font size in text box redactions 312
18.5 Mass deleting markups 312
18.6 Controlling markup visibility 313
18.7 Viewing markup history 313
18.8 Using the Markup Navigation pane 313
19 Markup sets 315
19.1 Permissions 315
19.2 Creating and editing a markup set 316
19.3 Fields 316
19.4 Copying markup sets 316
20 Mass operations 318
20.1 List of standard mass operations 318
20.2 Mass operations permissions 319
20.3 Mass Operation Jobs status 320
20.4 Cancel production job 321
20.4.1 Security configuration 321
20.4.2 Using Cancel Production Job 322
20.5 Mass edit 322
20.5.1 Working with multi-choice fields on the mass edit form 323
20.6 Mass copy 325
20.7 Mass move 325
20.8 Mass delete 326
20.8.1 Performing a mass delete on documents 326
20.8.2 Performing a mass delete on other objects 327
20.8.3 Enabling or disabling snapshot auditing on delete 327
Admin Guide 13
20.9 Mass Operation Jobs status 328
20.10 Mass replace 329
20.11 Mass image 330
20.12 Tally/sum/average 331
20.13 Mass export to file 333
20.13.1 Considerations 333
20.13.2 Using mass export to file 333
20.13.3 Fields 333
20.14 Move to folder path 334
20.14.1 Prerequisites for the move to folder path mass operation 334
20.14.2 Running the move to folder path mass operation 336
20.15 Mass Save as List 338
20.16 Mass PDF 339
20.16.1 Considerations 339
20.16.2 PDF permissions 340
20.16.3 PDF profile 340
20.16.4 Creating PDF 341
20.16.5 Branding PDF 346
20.16.6 Creating PDFs via mass operation 348
20.17 PDF Queue 352
20.17.1 PDF Queue columns 352
20.17.2 Cancel a PDF job 353
20.18 Mass convert 354
20.19 Retry Production Job 355
20.19.1 Security configuration 355
20.19.2 Retrying production jobs 356
20.20 Set long text field size 356
20.20.1 Before you begin 356
20.20.2 Using the mass operation 357
20.21 Invite users 357
21 Matters 359
21.1 Creating or editing a matter 359
21.2 Adding or removing matters from a client domain 359
22 Client domains 361
Admin Guide 14
22.1 Client domains software architecture 361
22.2 Client domains cloud infrastructure 361
22.3 Considerations before enabling client domains 362
22.4 Enabling client domains on a client 363
22.5 Client domain admins 363
22.5.1 Client domain admin considerations 364
22.5.2 Assigning a client domain admin 366
22.6 Client domain limitations and considerations 366
22.7 Adding or removing objects from a client domain 368
23 OCR 369
23.1 Creating and editing an OCR profile 369
23.2 Fields 370
23.3 Creating and editing an OCR set 371
23.4 Fields 372
23.5 Running an OCR set 373
23.6 Viewing OCR text 375
23.7 OCR queue 376
23.8 OCR on redacted production documents 377
23.8.1 Running the OCR job 377
23.8.2 Exporting a production 377
24 Pivot 378
24.1 Pivot profiles 378
24.1.1 Creating or editing a pivot profile 378
24.2 Running Pivot reports 380
24.2.1 Pivot color map 380
24.2.2 Adding a Pivot widget 381
24.2.3 Pivot options 382
24.2.4 Working with Pivot chart results 384
24.2.5 Working with Pivot table results 386
25 Persistent highlight sets 390
25.1 Getting started with persistent highlight sets 390
25.1.1 Showing and hiding persistent highlight sets in the Viewer 391
25.1.2 Navigating persistent highlight hits in the Viewer 393
25.1.3 Recent searches in the Persistent Highlight Sets pane 394
Admin Guide 15
25.1.4 Navigating highlighted terms in the Viewer 395
25.1.5 Persistent highlight set behavior across Viewers 397
25.1.6 Persistent highlight behavior 397
25.2 Using multiple persistent highlight sets 398
25.3 Performance considerations 399
25.3.1 Individual document size 399
25.3.2 Number of terms 399
25.3.3 Types of operators used 399
25.3.4 Local machine 400
25.4 Creating persistent highlight sets 400
25.4.1 Fields 400
25.5 Entering highlight terms 401
25.5.1 Color-coding persistent highlights 401
25.5.2 Guidelines for adding terms or phrases 403
25.6 Using the highlight fields source 403
25.6.1 Best practices 406
25.7 Creating efficient searches for persistent highlighting 407
25.7.1 Using terms search 407
25.7.2 Using highlight fields 408
26 Printing in Relativity 410
27 Production 411
27.1 Security permissions to run productions 411
27.2 Upgrading production 411
27.3 Basic production workflow 411
27.4 Production information 412
27.4.1 Production information tab 412
27.5 Production sets 414
27.5.1 Post production 414
27.5.2 Creating and editing a production set 414
27.5.3 Basic Settings 414
27.5.4 Numbering 416
27.5.5 Branding 423
27.5.6 Sorting 425
27.5.7 Post Production 426
Admin Guide 16
27.5.8 Other 427
27.5.9 Viewing production set details 427
27.5.10 Tracking multiple redaction sets 428
27.5.11 Advanced Formatting for Branding 428
27.6 Production data source 436
27.6.1 Adding a production data source 436
27.7 Placeholders 438
27.7.1 Creating an image placeholder 438
27.7.2 Creating a custom placeholder 439
27.7.3 Creating a PDF placeholder 439
27.7.4 Previewing placeholders 440
27.8 Production console 440
27.8.1 Manage Production 441
27.8.2 Run Production 442
27.8.3 Advanced Options 442
27.8.4 Stage and run a production 443
27.8.5 Stage a production 449
27.8.6 View documents 451
27.8.7 Check for production conflicts 452
27.9 Run a production 452
27.9.1 Checking production status 453
27.10 Production errors 454
27.10.1 Staging errors 454
27.10.2 Validation errors 455
27.10.3 Branding errors 456
27.11 Re-production 457
27.11.1 Special considerations 457
27.11.2 Security configuration 458
27.11.3 Re-production types 459
27.11.4 Re-production scenarios 462
27.11.5 Re-produce documents 464
27.11.6 Re-production job status 465
27.11.7 Re-production views 466
27.12 Branding queue 467
Admin Guide 17
27.12.1 Branding queue fields 467
27.13 Production queue 467
27.13.1 Change job priority 468
27.13.2 Retry Production Job mass operation 468
27.13.3 Cancel Production Job mass operation 469
27.13.4 Production queue fields 470
28 Redact 472
28.1 Example workflow 472
28.2 Installing Redact to a workspace 472
28.3 Before you begin 473
28.4 File size considerations 473
28.5 Redact supported file types 473
28.6 Permissions 473
28.6.1 All Redact permissions 474
28.6.2 Native PDF Redactions permissions 475
28.6.3 Native Excel Redactions permissions 475
28.6.4 Image Redactions permissions 476
28.6.5 Redact Production Preparation permissions 476
28.6.6 Redact Mass Operations permissions 477
28.6.7 Markup set permissions 477
28.6.8 Permissions for redacting documents outside of Relativity 477
28.7 Automated spreadsheet markup project 477
28.7.1 Supported file types 477
28.7.2 Preparing Excel documents 477
28.7.3 Before you begin 478
28.7.4 Creating a spreadsheet markup project manually 478
28.7.5 Creating a spreadsheet markup project using .csv or .xlsm rules 479
28.7.6 Fields 480
28.7.7 Running the project 484
28.7.8 Reviewing markups 484
28.7.9 Reviewing the original native document 484
28.8 Automated image markup project 484
28.8.1 Before you begin 484
28.8.2 Creating an image markup project manually 484
Admin Guide 18
28.8.3 Creating an image markup project using .csv or .xlsm rules 485
28.8.4 Fields 486
28.8.5 Running the project 489
28.8.6 Reviewing markups 490
28.9 Automated image template markup project 490
28.9.1 Before you begin 490
28.9.2 Creating an image template markup project 490
28.9.3 Fields 491
28.9.4 Running the project 491
28.9.5 Reviewing markups 491
28.10 Automated PDF markup project 491
28.10.1 Before you begin 491
28.10.2 Supported file types 491
28.10.3 Creating a PDF markup project manually 492
28.10.4 Creating a PDF markup project using .csv or .xlsm rules 492
28.10.5 Fields 493
28.10.6 Running the project 496
28.10.7 Removing a markup applied by a project 497
28.10.8 Reviewing markups 497
28.11 Automated production preparation project 497
28.12 Automated spreadsheet propagation project 497
28.12.1 Preparing Excel documents 497
28.12.2 Before you begin 498
28.12.3 Creating a spreadsheet propagation markup project 498
28.12.4 Fields 499
28.12.5 Running the project 499
28.12.6 Reviewing markups 499
28.12.7 Reviewing the original native document 500
28.13 Convert Spreadsheets Markup 500
28.13.1 Changing markup types 500
28.13.2 Reviewing converted markups 500
28.14 Manual markups with spreadsheet files 501
28.14.1 Preparing Excel documents 501
28.14.2 Excel file markup considerations 501
Admin Guide 19
28.14.3 Supported file types 502
28.14.4 .csv file markup considerations 502
28.14.5 Applying markups to .csv files 502
28.14.6 Applying markups to Excel files 502
28.14.7 Convert Spreadsheets Markup 505
28.14.8 Inverting markups 505
28.14.9 Excel document keyboard shortcuts 506
28.14.10 Reviewing markups 506
28.14.11 Reviewing the original native document 506
28.14.12 Downloading and exporting marked up documents 507
28.15 Manual markups with PDF files 507
28.15.1 PDF markup considerations 507
28.15.2 Supported file types 507
28.15.3 PDF basic redactions 508
28.15.4 PDF highlights 508
28.15.5 Rejecting highlights or markups 508
28.15.6 Reviewing markups 508
28.15.7 Downloading and exporting marked up documents 509
28.16 Redact Audits 509
28.17 Redact Client Usage Report 510
28.18 Redact External Markups 511
28.18.1 Example workflow 512
28.18.2 File size considerations 512
28.18.3 Adding documents to External Markups tab 512
28.18.4 Recommended uses of External Markups 513
28.18.5 External Markups tab columns 513
28.19 Redact Language Support 514
28.19.1 Language settings in Relativity 514
28.19.2 Entering Language Codes in an image markup project 514
28.20 Redact Project Status 515
28.20.1 Redact queue priority 515
28.20.2 Redact project Priority queue 515
28.20.3 Removing a project from the Priority queue 515
28.21 Redact Reports 516
Admin Guide 20
28.21.1 Available report fields 516
28.21.2 Generate a Markup or Document Report 516
28.21.3 Redact specific fields 517
28.22 Redact Settings 518
28.23 PDF annotation and attachment markups 519
28.23.1 PDF annotation redactions 519
28.23.2 Redacting PDF attachments 520
28.24 Regular expression examples 520
28.24.1 Before you begin 521
28.24.2 Email addresses and phone numbers regular expressions 521
28.24.3 Universal regular expressions 522
28.24.4 Financial accounts regular expressions 523
28.24.5 Government identification numbers regular expressions 526
28.25 Reviewing markups to ensure accuracy 529
28.25.1 Using the Redact Navigation card to review markups 529
28.25.2 Using the Redact navigation card in the Image Viewer 531
28.25.3 Review markups using Quality Review 531
28.25.4 Delete Native Markups 532
28.26 Running and reverting a Redact project 532
28.26.1 Running a project 532
28.26.2 Redact project performance expectations 533
28.26.3 Stopping a project that is running 535
28.26.4 Reverting a project 536
28.27 Searching for documents with Redact fields 536
28.27.1 Creating a saved search using Redact fields 537
28.28 Using Find and Redact 537
29 Sampling 540
29.1 Enabling sampling on an object 540
29.2 Generating a sample 541
29.2.1 Creating a fixed size sample set 542
29.2.2 Creating a percentage sample set 542
29.2.3 Creating a statistical sample set 543
30 Scripts 544
30.1 Script compatibility and updates 544
Admin Guide 21
30.2 Creating a new library script 544
30.3 Selecting an existing library script 546
30.4 Creating a new workspace script 547
30.5 Adding a library script to the script tab 548
30.6 Running a library script 548
31 Script groups 549
31.1 Setting up a script group 549
32 Search terms reports 551
33 Search terms reports 552
34 Searching 553
34.1 Filters 553
34.2 Search panel 553
34.3 Keyword searches 553
34.4 Saved searches 553
34.5 dtSearch 553
34.6 Analytics 554
34.7 Regular expressions 554
34.8 Additional features 554
35 Security and permissions 555
35.1 Levels of Security in Relativity 555
35.2 Instance security 556
35.2.1 Object Security tab 557
35.2.2 Tab Visibility tab 558
35.2.3 Admin Operations tab 559
35.2.4 Group Permissions report 560
35.2.5 Uneditable admin permission settings for the Everyone group 561
35.2.6 Script and application library permissions 562
35.2.7 System administrator privileges 562
35.3 Setting instance permissions 562
35.3.1 Groups Management tab 564
35.3.2 Features tab 567
35.3.3 Object Security tab 570
35.3.4 Tab Visibility tab 572
35.3.5 Admin Operations tab 572
Admin Guide 22
35.4 Workspace security 573
35.4.1 Workspace permissions 573
35.4.2 Features 574
35.4.3 Object security 574
35.4.4 Object list 575
35.4.5 Tab visibility 583
35.4.6 Browsers 585
35.4.7 Mass operations 585
35.4.8 Admin operations 586
35.4.9 Customer lockbox 588
35.4.10 Workspace admin group 588
35.4.11 RelativityOne lockbox 589
35.5 Setting workspace permissions 591
35.5.1 Group Management 592
35.5.2 Saving permissions for a group 595
35.5.3 Features tab 595
35.5.4 Object Security tab 599
35.5.5 Tab Visibility tab 601
35.5.6 Other Settings tab 603
35.6 Relativity object security 604
35.6.1 Securing a folder for selected groups 605
35.7 Preview security 607
35.7.1 Previewing security from the Workspace Details tab 607
35.7.2 Previewing security from the Groups tab 607
35.7.3 Previewing security from the Users tab 608
35.7.4 Preview security audit 608
35.8 Permissions scenarios 608
35.8.1 Hierarchical structure 608
35.8.2 Client domains 609
35.8.3 User groups 609
35.8.4 Template groups 609
35.8.5 Object-level permissions 611
35.8.6 Item-level permissions 612
35.8.7 Document unitization 612
Admin Guide 23
35.8.8 Scenarios 613
35.8.9 Frequently asked questions 614
36 Tabs 620
36.1 Creating and editing tabs 620
36.2 Fields 620
36.2.1 Tab Information 621
36.2.2 Tab Location 622
36.3 Nesting children tabs 623
37 Users 624
37.1 User status 624
37.2 Creating and editing a user 624
37.3 Adding a user log-in type 624
37.4 Fields 625
37.5 Viewing user audit records 627
37.6 Sending messages to users 629
37.7 Bounce list removal 629
37.8 Forcing users to log out 629
37.9 Adding or removing users from a client domain 630
37.10 Auto-disable users 630
38 Views 632
38.1 Workspace system views 632
38.2 System views from Home 633
38.3 Creating a view 634
38.3.1 Creating a view with field categories 634
38.3.2 Creating a view without field categories 635
38.4 Information tab 635
38.5 Other tab 636
38.6 Fields tab 636
38.7 Conditions tab 637
38.8 Sort tab 639
38.9 Editing view information 639
38.9.1 Using the four-step wizard 640
38.10 Basic Information 640
38.11 Fields 641
Admin Guide 24
38.12 Conditions 642
38.13 Sort 644
38.14 Linking a dashboard to a view 645
38.15 Displaying family groups in a view 646
38.15.1 Creating the family group view 646
39 Viewer 648
39.1 Native Viewer 649
39.1.1 Navigating the Native Viewer 651
39.1.2 Copying text in the Viewer 656
39.1.3 Streaming audio and video files 656
39.1.4 Document Intelligence 659
39.2 Image Viewer 662
39.2.1 Navigating the Image Viewer 662
39.2.2 Saving an image as a PDF 666
39.3 Extracted Text Viewer 667
39.4 Productions Viewer 671
39.4.1 Navigating the Productions Viewer 671
39.4.2 Imaging on the fly 674
39.5 PDF Viewer 674
39.6 Document actions menu 679
39.7 Viewer settings menu 680
39.8 Pop Out Viewer 681
39.8.1 Standalone Viewer 684
39.8.2 Document preview panel 684
39.9 Related items card 685
39.10 Document and Production History card 687
39.10.1 Document and Production History card permissions 688
39.11 Documents card 688
39.11.1 Email thread visualization tool 689
39.12 .eml and .msg header dates and times in the Viewer 689
39.13 Thumbnail Viewer 689
39.14 Document Compare 690
39.15 Viewer-supported file types 692
39.15.1 Text only designation 692
Admin Guide 25
39.15.2 File ID only designation 692
39.15.3 Supported File ID-only file types 692
39.15.4 Supported Text-only file types 693
39.15.5 Supported File types 694
39.15.6 Viewer audio and video-supported file types 705
39.15.7 Troubleshooting errors 705
39.15.8 Supported audio file types 706
39.15.9 Supported video file types 706
40 Workspaces 709
40.1 Creating and editing a workspace 709
40.2 Fields 710
40.3 Viewing workspace details 713
40.3.1 Deleting a workspace 714
40.4 Using the utilities console 714
40.4.1 System Settings 715
40.5 Managing system keyboard shortcuts 715
40.6 Viewing the personal items of workspace users 717
40.7 Migrating and retrieving workspaces to and from cold storage 717
40.7.1 Migrate workspaces to cold storage 717
40.7.2 Retrieve workspaces from Cold Storage 719
40.7.3 Deleting workspaces from Cold Storage 721
40.8 Adding and editing production restrictions 721
40.8.1 Managing production restrictions in templates 722
40.9 Workspace admin group 722
40.10 Repository workspaces in RelativityOne 723
40.10.1 Setting up a repository workspace 723
40.10.2 Example 1 723
40.10.3 Example 2 724
40.10.4 Special considerations 724
40.11 Document and item list navigation 725
40.11.1 Browsers panel 725
40.11.2 View bar 729
40.11.3 Document Preview panel 730
40.11.4 Item list 732
Admin Guide 26
40.12 Recycle Bin 735
41 Resources 737
41.1 Tutorials 737
41.2 Relativity Community 737
41.3 Relativity Support team 737
Admin Guide 27
1 Admin guide overview
The Admin guide will help give you the knowledge to effectively manage Relativity's flexibility and granular security
rights. This can help in providing an intuitive interface for your users. This guide explains the majority of features
available to you in Relativity. For more information about features not discussed int his guide, review our available
information on the RelativityOne documentation site.
1.1 Navigation
Relativity is an application with many screens and functions. This section describes the Review Interface you use to
review documents and some of the standard procedures you'll need to perform as you use the product.
1.1.1 Logging in
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.
For procedures to log in, see Logging in to Relativity.
1.1.2.1 Sidebar
The sidebar allows you to place tabs that you commonly use on the left-side of Relativity so that you can access them
at your convenience.
Admin Guide 28
Tabs are ordered from top to bottom of the sidebar based on the value entered in Order. The lowest order value
displays at the top and the highest value displays at the bottom.
The total number of tabs that display in the sidebar is determined by the resolution of your browser. Tabs that have
been assigned to the sidebar and do not fit, are available by hovering your cursor over the More icon. If a tab has one
or more child tabs, you can view and select those tabs by hovering over the parent tab's row in the fly-out menu.
Admin Guide 29
The More icon will display with an orange bar on the right side More to indicate that the active tab is located in the
More menu.
To add a new or pre-existing tab to the sidebar, toggle the Show in Sidebar on and click Save.
Tabs can display in the sidebar with their name and icon. Alternatively, to reduce the width of the sidebar and increase
the number of icons that can display, you can click the collapse arrow icon to only display the icon for each tab.
Admin Guide 30
1.1.3 All tabs menu
Click the icon at the bottom of the sidebar to display the All tabs menu. Every child tab that a user can view, as
determined by their permissions, will display in the menu in alphabetic order. This menu does not display parent tabs.
Admin Guide 31
1.1.4 Tab strip
If you select a tab that either has child tabs or is a child tab to a parent tab, the tab strip will display horizontally across
the top of Relativity. If a tab in the tab strip has one or more children tabs, hover your cursor over it to view and select
the desired tab. Depending on the size of your browser, there may be more tabs than can display in the tab strip. You
can hover your cursor over More in the tab strip to view additional tabs in a fly-out menu.
Admin Guide 32
1.1.4.1 Parent and child tab display
Parent tabs can be displayed in the sidebar or the tab strip. Tabs that have child tabs in the tab strip will display with an
arrow on the right side.
To view the child tabs of a parent tab in the sidebar or tab strip, hover your cursor over the parent tab and the child tabs
will display in a fly-out menu.
Admin Guide 33
When you select a child tab from the sidebar or the tab strip, you are taken to that page. For example, Production
Sets. In addition to an orange bar displaying underneath the parent tab in the sidebar, the child tab and the path to
reach the active tab is highlighted in blue to help you track your location in the sidebar or the tab strip.
Instead of clicking the drop-down arrow, you can also click the parent tab itself. Clicking the parent tab takes you to the
default child tab, which is identified by the order setting for each child tab.
The Relativity Instances section includes federated instances you have access to. Federated instances links allow
reviewers to easily switch to other Relativity environments. For more information, see Federated instances.
The user drop-down menu options are:
Admin Guide 34
l My Settings—opens a pop-up where users can change their personal settings. See My settings below for more
information.
l Other Relativity instances—hover your cursor over this option to display a fly-out menu of federated
instances that have been linked to your current one. Click on the desired federated instance to switch to that
linked instance.
l Help—launches the Relativity documentation website in your internet browser. The documentation site
provides all Relativity user, system admin, and systems documentation in a navigable format.
l Contact Support—opens a new window in your internet browser containing the Technical Support page of the
Relativity website where you can open a support ticket.
l About Relativity—opens a pop-up displaying the Relativity version number, your instance details, and licens-
ing agreement information.
l Search the Community—opens a new window in your internet browser containing the Relativity Community
page where you can find applications for Relativity to download, stay up to date on the latest Relativity events,
and interact with other Relativity users.
l What's New—opens a side panel that gives you the opportunity to learn about new and noteworthy updates
and enhancements directly in RelativityOne.
l Logout—logs users out of Relativity.
Note: If a user is not a member of a group with permission to view the tab set as the default Home tab, Relativity
redirects to the lowest ordered tab the user's permissions allow.
1.1.5.2 My settings
Clicking My Settings from within the user drop-down menu opens a settings mode pop-up, which displays your user
information. Click Edit to change your settings.
Admin Guide 35
l First name—your first name.
l Last name—your last name.
Note: Your first and last name appear as your username throughout Relativity.
l Default Filter Visibility—determines whether or not the filters for columns in views display by default.
l Hidden—hides filters by default.
l Visible—displays filters by default.
l Item list page length—a numeric field indicating the default list length for all lists in Relativity. It can be set
from 1-200.
l Default Selected File Type—the default viewer mode used when first loading the Viewer. Viewer, Native,
Image, Long Text, or Production. If the mode selected is not available, the Viewer will instead use the first avail-
able option. See Viewer on page 648 for details.
l Default Saved Search Owner—determines whether saved searches are public or private by default. If set to
Public, the search is public and all users with rights to it can see it. If set to Logged in User, the search is private
and only the logged in user is able to see it.
Note: Depending on your permissions, you may not have rights to edit the Default Saved Search Owner
field.
l Native Viewer Cache Ahead—if checked, this field pre-loads the next native document in your review queue
when the active document is loaded.
l User-Group Email Notifications—user's preference for email notifications when adding or deleting Users or
Groups.
l All Emails—receive all email notifications.
l No Emails—receive no email notifications.
l Only Failed Operations—receive email notifications on failed operations only.
Note: Depending on your permissions, you may not have rights to edit the User-Group Email Notifications
field.
1.1.5.3 Dashboards
When you've created a page configuration you'd like to preserve, you can create a customized dashboard. You can
save multiple dashboards to quickly change the page configuration. The item list and any widgets on the dashboard
will update automatically in response to filtering or searching. Dashboards only report on data within the workspace
you are in.
Admin Guide 36
Note: For a list of dashboards that provide an effective starting point for administrators to help review teams
visualize their data set, see Common commonly-used dashboards in the Admin Guide.
The page initially appears with the folder browser on the top left, the search panel on the bottom left and the item list to
the right. Within this new framework, you have multiple options for customizing your display.
You can resize, move, or collapse any panel on the page, including any widgets you create.
l To resize any panel, hover over the line separating the item list from the panel until you see the mouse pointer
change to horizontal arrows, then click and drag.
l To move, hover over the top of the panel until you see the Multi-Direction Cursor icon. Then, click and drag the
panel to the new location.
l To collapse the search panel or browser pane, click the Collapse icon. Once collapsed, click the Show
Browser Panel icon to restore the browser pane or the Show Search Panel icon to restore the search panel.
Additionally, you can drag and drop panels to rearrange on the page. Click any panel and drag it to a new location. The
other panels will automatically move to accommodate the panel you're dropping.
Dashboards and widgets can be copied over to newly created workspaces if they are part of a template. Dashboards
only report on data within the workspace you are in if data is loaded in the workspace.
Note: You must have the correct workspace permissions to add, edit, or save a dashboard and to save pivot
widgets to your dashboard.
You can also export individual Pivot widgets to Excel or to PNG format from each widget's context menu. See
Exporting a Pivot widget in the Admin Guide for more information.
Admin Guide 37
Note: To enable the Add Widgets button and Pivot functionality for an Relativity Dynamic Object (RDO), you must
select Enabled for the Pivot property in the Object Type Information section for the object.
Creating a dashboard
To create a dashboard:
1. Click the Dashboards drop-down menu in the top right corner of the screen.
Note: You can only access the drop-down if Pivot is Enabled for the given object type.
2. Click New Dashboard to save the current page configuration as a new dashboard.
3. Enter a name and an order number for the dashboard.
Note: The dashboard with the lowest order number will appear by default when you log in to Relativity.
l Pivot charts and tables—you can use Pivot to summarize data in tables or charts to visually analyze trends in
your data.
l Cluster visualizations—on the Documents tab, you can use Relativity Cluster Visualization to render your
cluster data as an interactive visual map by adding a Cluster Visualization widget. This offers you a quick over-
view of your document cluster sets and quickly drill into each cluster set to view sub-clusters and conceptually-
related clusters of documents. Please note that there may be only one cluster visualization widget per dash-
board.
l Communication Analysis—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.
Note: When you reach the maximum number of widgets allowed on a dashboard, the Add Widget button will be
grayed out and a tooltip displays when you hover over it that lets you know the reason you cannot add any additional
widgets to your dashboard. This is controlled by the MaxNumberDashboardWidgets instance setting.
1. Click the Dashboards drop-down menu in the top right corner of the screen to display the list of dashboards
available on the current tab.
2. Click Save to save the changes to the existing dashboard. Click Save As to save the page configuration as a
new dashboard, and then enter a Name and Order number.
Note: If a dashboard is part of a locked application, the option to save the dashboard is unavailable.
Deleting a dashboard
To delete a dashboard from the current tab you are in, click the Delete icon to the right of the dashboard you want to
delete in the Dashboards drop-down menu.
Click Delete in the Delete Dashboard Confirmation pop-up window to delete the dashboard.
Admin Guide 38
Note: If a dashboard is part of a locked application, the option to delete the dashboard is unavailable.
Renaming a dashboard
To rename a dashboard:
1. Click on the Edit icon next to the name of the dashboard in the Dashboard drop-down menu.
2. Enter a Name and an Order number for the dashboard. The order number controls the order in which the dash-
board displays in the list.
3. Click Save to save your changes.
Note: If a dashboard is part of a locked application, the option to edit the dashboard is unavailable.
Note: If your password has expired, the Reset Password dialog appears automatically when you log in to Relativity.
Your system admin determines when your password expires and the number of previous passwords that you
cannot reuse.
You can use your new password next time you log in to Relativity.
Admin Guide 39
1. Click Forgot your password? on the login screen.
2. Enter your email address in the pop-up dialog.
Relativity sends an email to the address you provide. You should receive this message within a few minutes. If
you do not receive an email, check your spam or junk mail folder.
3. Click the link in the email to reset your password. This link will be active for 15 minutes and expires after that
time. If the link has expired, or if you click the link more than once, you'll have to generate a new password reset
request.
4. The link directs you to a page where you can create a new password.
5. Enter a new password and retype it, then click Submit. After your password successfully resets, you'll get a
message prompting you to log in with your new password. An email will be sent to the address you entered, noti-
fying you that your password reset was successful.
1.1.7 Favorites
The Favorites menu contains all your bookmarks (Favorites) and the last 10 pages in your browsing history (Recents).
The Favorites menu can be accessed by clicking the Favorites icon in the upper-right part of the page.
Use Favorites to quickly navigate the Relativity application. If you visit a particular page on a regular basis, minimize
the number of clicks it takes to get there by adding the page as a favorite.
To mark a page as a favorite, click the star to the right of the breadcrumbs at the top of the page. The star turns yellow
and Relativity adds the page to the Favorites section. Relativity doesn't limit the number of pages you can mark as a
favorite.
Admin Guide 40
Relativity records pages in the Recents section on each page load. That means that pop-up windows aren't recorded
as Recents.
Note: If you're a system admin, you can turn off this feature by editing the RecentHistoryEnabled and
FavoritesEnabled instance setting values. You can also change the number of Recents the Favorites menu displays
by editing the RecentHistoryNumberOfItemsDisplays instance setting value.
Note: Verify that the quick nav Ctrl+/ keyboard shortcut works on custom pages. Contact Customer Support with
any problems.
Open quick nav, and type the name of any tab or workspace.
Any tab or workspace that contains the character string within the name appears in the list of results. Results appear
after you type more than one character, and they refine with each character you type. The results link you directly to
the tab or workspace in Relativity.
Note: In Relativity terms, the search works the same as a leading and trailing wildcard search.
You can click on any result or use the up and down arrow keys to move through the results. Press Enter to navigate to
the selected item.
Your search remains until the page is refreshed or you navigate to a new tab. The Esc key also clears your search
from quick nav. If no text is entered in the quick nav search field, the Esc key closes quick nav. You can also click
anywhere outside the quick nav window to close it.
Quick nav displays three types of results in the following order:
Admin Guide 41
l Workspace tabs—lists all workspace tabs that fit the search criteria and are available with your permission set-
tings.
l Admin Tabs—lists all admin tabs that fit the search criteria and are available with your permission settings.
l Workspaces—lists all workspaces that fit the search criteria and are available with your permission settings.
Click the workspace to go to the default tab for that workspace.
Quick nav results only reflect items available with your permission settings.
The following list highlights more features of quick nav functionality.
l Type the word "home" in quick nav to navigate to your default Home tab.
l Quick nav is enabled or disabled with the QuickNavEnabled instance setting.
l Quick nav is available to look up workspaces and admin tabs from Home for groups assigned the Use Quick
Nav admin permission, and it is available to look up tabs in a workspace for groups assigned the Use Quick
Nav workspace permission.
l The maximum number of returned quick nav search results is limited to any number between 2-50, but the
default is 20.
l The maximum number of searchable characters is 50.
Note: For help with single sign-on error messages, please see the SSO Troubleshooting console on page 106.
Note: The Forgot your password? link only displays if the admin enables Allow Password Recovery via Email
setting, for more information see the Authentication Guide.
1.2.2 Password
This method uses only a username and a password. Your RelativityOne admin provides you with the following:
Admin Guide 42
1. Navigate to the RelativityOne site.
2. Log in with your password. See Logging in to RelativityOne with a password on the previous page
Admin Guide 43
6. Hold phone up and scan the QR code provided by Relativity.
If you are unable to scan the QR code, click the Can't scan QR code? link below the QR code. Once clicked, a
code will appear. Enter the code into your authenticator app on your phone. Once entered into the authenticator
app, you can continue to the next step.
7. Click Next.
8. Re-enter your email and password.
9. Enter the authentication code in the app.
10. Click Next.
11. Click Done.
To log in with an authenticator app method:
Admin Guide 44
4. Click Login.
Note: If you are a system admin, the Password Reset Email will not be sent to you. For more information, see the
Authentication Guide.
Admin Guide 45
1. Within the password request email, click Reset Password or enter the full URL into your browser.
2. Enter a password following the restrictions listed on the screen. You must remember this password to log in.
The link within the email is valid for 15 minutes, and you can only use the most recent email. Although, once the
password is set, you do not have to log in immediately.
Note: The following non-alpha-numeric characters are not allowed: \, ", <, >, £ in passwords.
3. Click Submit.
4. Click Return to RelativityOne.
Admin Guide 46
2 Relativity applications
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."
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.
l Analytics
l Analytics Core
Note: The Analytics Core application must be present in all workspaces, and may not be uninstalled.
l Case Dynamics
l ECA and InvestigationECA and Investigation
l Integration Points
l Processing (requires licensing)
l Production
l Relativity Event Handler Express
l Relativity Legal Hold
l Review Center
l Set Extracted Text Size
Admin Guide 47
2.2 Relativity custom applications
Custom applications extend the existing Relativity functionality by providing new solutions for case management,
review processes, specific workflows, or other business needs for your organization. For example, you might want to
develop an application to manage tasks and projects or to facilitate a large-scale review of structured data.
You can implement custom applications using the following features in Relativity:
l RDOs - You can develop Relativity dynamic objects that represent real world business entities that your organ-
ization uses, such as custodians, contacts, or companies. In addition, you can create custom workflows that
use your objects by designing views, layouts, tabs, and other Relativity objects. You don’t need any pro-
gramming experience just the appropriate security permissions to build these objects. For example, the sample
application Media Tracker illustrates how to use RDOs, views, and layouts to track content received from
vendors, clients, and opposing counsel. See Building Media Tracker with RDOs on the Relativity Docu-
mentation Site.
l ADS - You can use the ADS to package the RDOs, layouts, views, fields, and other Relativity components that
you want included in your custom application. The ADS provides you with a framework available through the
Relativity UI for packing the components that you create, as well as custom code developed to add advanced
functionality to your applications. By using the ADS, you can export your applications for installation across
workspaces and on other Relativity instances. You don’t need any programming experience to package your
applications with the ADS, but you must have the required security permissions. For more information about
the ADS, see the Relativity Developers Site.
l Custom code - You can add advanced functionality to your custom applications by developing custom code for
event handlers, agents, and custom pages. After building files or assemblies with your custom code, you can
easily upload them to Relativity for inclusion in your applications. For more information about event handlers,
agents, and custom pages, see the RelativityOne Developers site.
l Install applications - Add custom applications to your Relativity environment by installing them in the Applic-
ation Library or on individual workspaces. In addition, you can push an application installed on a workspace to
the Application Library.
l Export applications - Export applications from one workspace for deployment in another workspace. You can
also install exported applications in the Application Library on another Relativity instance. In addition, you can
export applications for further customization.
l Uninstall or delete applications - Remove applications that you no longer need from a workspace. You can
choose to delete just the application or uninstall the applications and its related components.
l Upgrade applications - Add new or updated features to an existing custom application.
Admin Guide 48
2.4 Global applications
Global applications are applications installed on the admin level of a Relativity instance. Their schema versions are
not validated, they don't support RDOs, object-type or workspace-based event handlers.
2. In the Views tab in a workspace, click the icon next to All Library Applications.
3. On the right side of the newly opened View window, select Is Global Application under Unselected.
4. Move the Is Global Application in your view to the right box, Selected. You can move fields between boxes
by:
l Double-clicking the field name.
l Using the arrows between the boxes.
5. Click Save.
6. The Is Global Application column is added to the Application Library.
Admin Guide 49
2.5 Exporting applications
You can export applications that you want to install in other workspaces or instances of Relativity. Additionally, you
may want to export an application for upgrading in your development environment. You can export applications as
RAP files.
Admin Guide 50
2.5.2 Avoiding errors during application export
You can't export an application until you manually resolve all errors listed through the Show Errors link on the
application console.
To help you reduce or avoid these errors before you're ready to export the application, consider the following actions:
Object
Notes for preparing the
you're Error you'll avoid
application for export
adding
Object type Make sure the Dynamic field Object Type <Name of Object Type> is not exportable because it is not
on all object types you add dynamic.
to the application is set to
Yes.
Add all object types to the The <Name of Object Type> object type is associated with the <Name
application before adding of Event Handler> event handler. Please add the object type to your
event handlers. application in order to proceed.
Add the objects to the applic- The <Name of Object> object associated with Document field <Name of
ation before adding the Field> is required in order to proceed. Please add this object to your
fields. application.
Add all layouts to the applic- The <Name of Object> object that owns the <Name of Layout> layout
ation before adding the must be added to your application in order to proceed.
object types.
Tab Make sure none of the tabs The <Name of Tab> tab is a parent tab. Parent tabs cannot be included
you link to from your in an application. If your application contains any non-parent tabs they
application are parent tabs. will be placed under an auto-generated tab named after the application
on install. Please remove this tab from your application to proceed.
Add all object types to your The <Name of Tab> tab is associated with the <Name of Object Type>
application before adding object type. Please add this object type to your application in order to
tabs separately. proceed.
View Add the views to the applic- The <Name of View> view includes the following field(s): Field X, Field
ation before adding the lay- Y, etc. Please add the field(s) to your application in order to proceed.
outs and fields.
Add the views to the applic- The <Name of View> view is referenced in the <Name of Layout> lay-
ation before adding the lay- out. Please add this view to your application in order to proceed.
outs and fields.
Add all views to the applic- The <object type> associated with the <view name> is required in order
ation before adding the to proceed. Please add this object to your application.
object types, with the excep-
tion of any non-dynamic
object types.
Layout Add the layouts to the applic- The <Name of Layout> layout includes the following field(s): Field X,
ation before adding the Field Y, etc. Please add the field(s) to your application in order to pro-
fields. ceed.
Add the views to the applic- The <Name of Layout> layout includes popup pickers using the fol-
ation before adding the lay- lowing view(s): View X, View Y, etc. Please add the view(s) to your
outs and fields. application in order to proceed.
Admin Guide 51
Object
Notes for preparing the
you're Error you'll avoid
application for export
adding
Field Make sure all views, includ- The field <Name of Field> is a relational field. The view, Family Docu-
ing relational views, are ments, associated with this relational field must be added to your applic-
added to the application ation in order to proceed.
before you add the fields.
Make sure all unsupported Relativity applications don't support the Batch::Assigned To field.
fields are removed from the Remove Batch::Assigned To field from your application to proceed.
application.
Add all fields to your applic- The Handler associated with the choice <Name of Choice> is required
ation before adding the in order to proceed. Please add this field to your application.
choices with which they are
associated.
Remove all system fields The Document field <Name of Field> is a System field. You must
from the application. remove this field from the application in order to proceed.
Add all fields to the applic- The <object type> associated with the <field name> is required in order
ation before adding object to proceed. Please add this object to your application.
types, with the exception of
any non-dynamic object
types.
Dashboard Make sure all the fields The <Name of Dashboard> dashboard associated with the <Name of
found in the dashboards you Object Type> object type includes the following field(s): Field X, Field Y,
include in the application are etc. Please add the field(s) to your application in order to proceed.
added to the application.
Agent Make sure the correct <Name of Agent> agent is not assigned to the correct application
agents are attached with the domain.
application.
Rule Add all object types to your The <Name of Rule> Object Rule is associated with the <Name of
application before adding Object Type > Object Type. Please add the Object Type to your applic-
object rules separately. ation in order to proceed.
Saved Add all choices to the applic- The <Name of Saved Search> saved search is associated with the
Search ation before adding the <Name of Choice> choice. Please add this choice to your application in
saved searches. order to proceed.
Add all fields to the applic- The <Name of Saved Search> saved search includes the following field
ation before adding the (s) in its conditions: Field X, Field Y, etc. Please add these field(s) to
saved searches that contain your application in order to proceed.
them.
Event Hand- Make sure all event handlers Event Handler <Name of Event Handler> is not assigned to the correct
ler that you intend to add to the application domain.
application are correctly con-
figured.
Mass Oper- Add all object types to the The <Name of Mass Operation> mass operation is associated with the
ation application before adding <Name of Object Type> object type. Please add the Object Type to your
the mass operations with application in order to proceed.
Admin Guide 52
Object
Notes for preparing the
you're Error you'll avoid
application for export
adding
which they are associated.
System Arti- Remove all system artifacts You have included one or more System Artifacts in the application. You
fact from the application. must remove these artifacts to proceed: Artifact X, Artifact Y, etc.
l Locking - Relativity automatically locks any unlocked applications on export. See Locking and unlocking applic-
ations.
l applicationIsDirty flag - Relativity automatically resets the applicationIsDirty to false on any unlocked applic-
ations with the applicationIsDirty flag set to true. The value of false indicates that application is in a clean, uned-
ited state. This flag determined the type of upgrade required for an application installed in a workspace.
l Application version - Relativity increments the revision number of the application version with each export if
the application is unlocked, the application schema has been modified, or if Developer Mode is enabled.
l
Additionally, Relativity automatically increments the version of any application that contains saved searches, which
have been modified. For more information, see Modifying saved searches in a locked application on the Relativity
RelativityOne Documentation site.
Note: If you are writing custom code, you can also use the Export API to export an application programmatically.
For more information, see Export (.NET) on the RelativityOne Developers site.
4. If your application contains external resources, click Export on the Confirm Application Export dialog. Relativity
only displays this dialog for applications with external resources, such as custom pages. It exports those applic-
ations as a RAP files.
Note: If you export an application with a Single or Multiple Choice field without choices, you receive a mes-
sage asking if you want to continue with the export. Click OK on this message dialog.
Admin Guide 53
6. Click Refresh Page in the Application Console. You can find the RAP file for your application in the folder that
you selected. Upload this file to the workspace or Relativity instance where you want to deploy the application.
l Choice
l Field
l Layout
l Object Type
l Relativity Script
l Tab
l View
l Dashboard
Note: Relativity automatically locks an unlocked application on export. See Exporting applications.
1. Navigate to the workspace containing the application that you want to lock.
2. Click the Relativity Applications tab.
3. Click the name of the application that you want to lock.
4. Click Lock Application in the Application Console.
Admin Guide 54
l You can set a tab in a locked application as the default tab for the workspace.
l You can use the Copy mass operation to copy views and layouts in a locked application.
l The copied views and layout are identical to the original and can be customized.
l When you open views and layouts in a locked application, Relativity displays a user-friendly alert:
If you later upgrade the application, Relativity preserves any changes made to the customized layouts, views, and
default tab.
l Move a saved search to a different folder in the saved searches browser. For more information, see Saved
search on the Relativity RelativityOne Documentation site.
l Change the index type for a saved search.
If you later upgrade the application, Relativity preserves any changes made to the saved searches. It also increments
the version when you export an application with modified saved searches.
Admin Guide 55
2.6.4 Unlocking an application
When an application is unlocked, you can add components to it, delete them, or unlink them. You can also edit the
fields on any the components in an unlocked application. For example, you want to modify an unlocked application
with a custom view. You can add or remove columns from the view when you unlock the application. Consequently,
you only want to unlock an application when you purposely want to update it.
The RelativityApplication object has the applicationIsDirty property. This property is set to true when you unlock an
application. The current state of an unlocked application is unknown because users may inadvertently modify it. The
applicationIsDirty property also determines the type of upgrade installation required for an application in a
workspace.
Use the following procedure to unlock an application:
1. Navigate to the workspace containing the application that you want to unlock.
2. Click the Relativity Applications tab.
3. Click the name of the application that you want to unlock.
4. Click Unlock Application in the Application Console.
5. Click OK on the confirmation message. You can now edit the application by adding or removing components. In
addition, you can update individual components by adding, removing, or making other changes to their fields.
l Install an application that exists as an external file to the Application Library. The application becomes available
for installation to all workspaces. This is useful for when you need to install an individual application .xml file or
.rap file to multiple workspaces that Relativity support provided to you. For more information, see Installing an
application from an external file to the Application Library on the next page.
l Push an application that exists in a single workspace to the Application Library, so the application is available
for installation to other workspaces. This is useful for when you install an individual application .xml file or .rap
file to a single workspace, and then decide to install the application to other workspaces. For more information,
see Pushing an application from a workspace to the Application Library on the next page.
l Push an application from the Application Library to one or more workspaces. For more information, see Pushing
an application from the Application Library to a workspace on the next page.
l Install an application from the Application Library to a workspace. This is the standard route of adding an applic-
ation after you install or upgrade to a new version of Relativity and have access to the most up-to-date Applic-
ation Library. For more information, see Installing applications from the Application Library on page 58.
l Install an application that does not exist in the Application Library to a workspace as an external file. This is use-
ful for when you need to install an individual application .xml file or .rap file that was not included in a Relativity
upgrade or installation to a single workspace. For more information, see Installing an application from an
external file to a workspace on page 58.
Admin Guide 56
2.7.1.1 Installing an application from an external file to the Application Library
If you're a RelativityOne customer, and you wish to install an application from an external file to the Application Library,
contact Support before doing so, as your application may require agent configuration or other infrastructure
components.
Note: You override any existing applications with the same GUID when you push an application from a workspace
to the library.
1. Navigate to a workspace where the application you want to add to the Application Library is installed.
2. Click the Relativity Applications tab.
3. Click the name of the application to display its detail view.
4. Click Push To Library in the Relativity Application console.
Note: When you install an application, all components are public regardless of the permissions that you assign to
them in your application. The ADS framework ignores any permissions or security assigned to a component added
to an application during deployment in a workspace.
Admin Guide 57
2.7.3.1 Installing applications from the Application Library
If you added the application to the Application Library, you can install it to the current workspace without importing an
external file to Relativity. In Relativity, confirm that you have the appropriate system admin permissions to install an
application. For more information, see Workspace security on page 573.
Use the following procedure to install an application from the Application Library:
Note: Global applications are not listed in the Select from Application Library option when attempting to
add an application to a workspace.
10. Click Import to save your mappings and import the application.
Relativity installs the application into the workspace.
11. Review the import status of the application. Verify that the install was successful or resolve errors. See Viewing
import status on page 62 and Troubleshooting application installation errors on page 62.
Note: You can also use the Application Install API to import an application programmatically. For more information,
see Application Install (.NET) on the RelativityOne Developers site.
Admin Guide 58
Use the following procedure to install an application from an external file:
1. Navigate to a workspace.
2. Click the Relativity Applications tab.
3. Click New Relativity Application to display an application form.
4. Click Import from File in the Application Type section.
Note: Relativity Applications use .rap files. If you upload the wrong file type, the following error message
appears: The uploaded file is not a valid Relativity Application file.
If the application includes a custom page of a restricted file type, you receive an error message and cannot
install the application. See Best practices for custom pages on the RelativityOne Developers site.
6. Click Open to upload the file to Relativity. The application form displays the following fields:
l Application Name—displays the name of the application.
l Version—displays the version of the application you're installing.
l File Name—displays the name of the application file. To remove the file from the form, click Clear in this
field.
7. Expand the tree to view the artifacts associated with your application in the Application Artifacts section. This
hierarchy tree includes Object Types, External Tabs, Scripts, Custom Pages, Agent Types, as well as Pre and
Post Install Event Handlers contained in your application.
8. Map fields if necessary to prevent installation errors. If your application does not contain any fields cor-
responding to those currently in the workspace, the following message displays. Otherwise, the Map Fields sec-
tion displays a mapping grid. For more information, see Mapping fields on the next page.
9. Click Import to save your mappings and import the application. Relativity installs the application into the work-
space.
10. Review the import status of the application. Verify that the install was successful or resolve errors. See Viewing
import status on page 62 and Troubleshooting application installation errors on page 62.
Admin Guide 59
Note: While Relativity 9 and above assigns a GUID to any saved search added to an application, older versions of
Relativity do not use GUIDs to identify saved searches. You can build an application using a saved search in a
template workspace created before upgrading to Relativity 9 or above. However, deploying your application in a
workspace created with this template results in duplicate copies of the saved search. Since Relativity identifies
saved searches by GUID, it does not recognize that the legacy search in the workspace is the same as the search in
the application, so it creates a new one with the matching GUID.
In general, you install these applications following the same steps used for other applications, but you may want to
complete the verification steps before you install them in a workspace. If the workspace does not contain a dtSearch
or an Analytics index with the same name as the one included in the application, Relativity creates it using the system
defaults. The post-installation steps require you to build the index after Relativity completes this process. For
information about building applications with saved searches, see the Creating an application in Relativity on the
Relativity RelativityOne Developers site.
Note: When you install an application, all saved searches are public regardless of the permissions that you
assigned to them in your application or folder structure. The ADS framework ignores any permissions or security
assigned to a saved search added to an application during deployment in a workspace.
l Saved searches using dtSearches—confirm that a file share for this index type exists in your environment.
The Relativity installer requires you to create this file share during the installation of the primary SQL Server.
l Saved searches using Analytics indexes—confirm that an Analytics server is installed in your Relativity
environment.
Installation steps
To install the application, follow the instructions in Installing applications from the Application Library on page 58 or
Installing an application from an external file to a workspace on page 58.
Post-installation steps
If your workspace already contains a dtSearch or Analytics index, Relativity automatically maps it to the saved search
using the index name and type. It ignores any spaces or case differences in the index name.
If your workspace does not contain an index with a matching name or type, Relativity creates a shell for a dtSearch or
Analytics index. You need to complete one of the following steps to build the index:
l dtSearch index—navigate to the Search Indexes tab in Relativity, and click the Edit link for your dtSearch
index. Select settings for the Order, Searchable set, Index share, or other fields as necessary, and save your
changes. Next, build the index by using Build Index: Full option on the index details page. For more inform-
ation, see dtSearch on the Relativity RelativityOne Documentation site.
l Analytics index—navigate to the Search Indexes tab in Relativity, and click the Edit link for your Analytics
index. Select settings for Analytics profile, Analytics server, Data source, Training data source, and fields
as necessary. Next, build the index. For more information, see Analytic Indexes on the Relativity
RelativityOneDocumentation site.
Admin Guide 60
Addresses. Instead of two fields storing similar information, you might want all applications to use the same field for
this metadata. By mapping these fields, you can avoid renaming the new field and using two different fields to store
this metadata in your workspace.
Use these guidelines when mapping an application to workspace fields:
l Fixed length text fields—you can map application fields of this type only to workspace fields of equal or lesser
length. Workspace fixed text fields that have a length longer than the application fields are not displayed in the
Workspace Fields column of the mapping interface.
l Renaming fields—you can rename a field after you map it without impacting future application upgrades.
l Renaming fields and exporting—if you rename a field in an application installed on Workspace A, and then
export the application, this field is still renamed when you import the application to Workspace B. This practice
does not apply to Document System Fields.
l Target workspace fields renamed—when you map an application field to a workspace field, the application
renames the workspace field to match the application field. The application now owns the field.
l Handling of removed components—if you remove a component from an application installed in Workspace
A, and the export the application, this component is still part of the application when you import it to Workspace
B. In other words, the component that you removed from Workspace A imports to Workspace B. Application
components include choices, fields, object rules, and others.
Use the following procedure to map application fields to workspace fields:
1. Complete the steps for installing an application described in the previous sections.
2. Locate the Map Fields section on the application form. The Map Fields section displays the mapping interface if
the application contains fields corresponding to those in the workspace.
3. Complete these steps to map the available application fields of your choice through the Field Mapping interface:
l Highlight a field in the Application Fields box, and then click the arrow to move it to the center box. The
Workspace Fields box displays the fields in the target workspace that may match the application field.
The Workspace Fields box does not display any fields when no matches exist.
l Highlight a field in the Workspace Fields box, and then click the left arrow to move it to the center box.
Note: You can also double-click a field name to move it to a mapping box. To remove a field from the
mapping box, use the left arrow for the application fields, and right arrow for the workspace fields.
Admin Guide 61
2.7.3.5 Viewing import status
After you install an application through the Relativity Application tab, you can view the status page, which appears
immediately after this process completes. The Import Status section indicates whether your installation was
successful.
The Artifact Name section displays a list of all the artifacts in your application, which includes its Artifact Type, Artifact
ID, and installation status. For artifacts installed without errors, the Status column displays the message Updated
successfully.
For unsuccessful installations, the Import Status section indicates that your application installation failed as illustrated
in the following message. The message lists the number of errors encountered during the installation. In addition, the
Status column describes each error that occurred during a failed installation. For more information, see
Troubleshooting application installation errors.
To export the Status section report to a .csv file, you can click the Export Status Details. You can also view status
information for the installation of an application from the Application Library tab. Click on an application to display a
detail view, and then click its Installed link to display the status page.
Admin Guide 62
2.8.1 Installation error list
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.
Admin Guide 63
2.8.2.2 Name conflicts
You can rename the conflicting artifact so that you can import the components of your application.
Use the following procedure to resolve these errors:
1. Select an option in the Resolve Errors drop-down menu. Available options include Rename and Map Field.
2. Perform one of the following tasks:
l Rename - Enter a new name in this field to resolve the Name Conflict error. When you've entered a valid
name, a green check mark appears next to the new name field.
l Map Field - When you select this option, Relativity automatically maps the field that you're importing to
the conflicting field in the target workspace.
Admin Guide 64
2.9.1 Uninstalling applications
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.
For example, you might need to uninstall an application that you accidentally deployed to a template case. If you want
to remove only the application instance or if you created an application that you haven't added to the library, consider
deleting it instead of uninstalling it. See Deleting applications on page 72.
Note: Applications installed via the Application Library can only be removed by System Administrators.
1. Select the Relativity Applications tab in the workspace that contains the application you want to uninstall.
2. Click the application name to display the details view.
3. Click Unlock Application, if necessary. You can't uninstall a locked application.
4. Click Uninstall Application to display the Component Summary page. This page lists object types fields, event
handlers, custom pages, and other components of your application.
5. (Optional) Click to expand the list of components. The hierarchy tree shows the parent-child relationships for
component types in your application.
6. (Optional) Clear the check box for any components that you don't want to uninstall.
7. Click Validate Components to Uninstall to view the Application Uninstall Alerts and Modification Alerts for
Non-Application Components reports. See Uninstall and modification alerts below.
8. Click Uninstall Application. When the confirmation message appears, click Yes to complete uninstalling the
application. You can manually uninstall custom pages if your application includes these components. See
Manually uninstalling custom pages on the next page.
l Application Uninstall Alerts - lists dependencies that may prevent the removal of an application component.
For example, Relativity doesn't remove an object type referenced by a locked application or the parent object of
a child that you want to retain in the workspace.
l Modification Alerts for Non-Application Components - lists components that aren't part of the application
but must be modified to uninstall the application. Other objects may reference components deleted during the
uninstall process. For example, Relativity may delete an object type referenced by an unlocked application.
To view these reports, click Validate Components to Uninstall on the Component Summary page. See Uninstalling
an application above.
Admin Guide 65
2.9.1.3 Viewing application uninstall errors
Relativity displays the view for the Relativity Applications tab after you click Uninstall Application on the Component
Summary page. When an application fails to uninstall properly, Relativity locks the application and generates a list of
errors that occurred during the uninstall process. The application also continues to appear in the list view of the
Relativity Applications tab.
To view uninstall errors, click the application name in the list view to display the details page, and then click Show
Errors.
Note: You should only uninstall custom pages when you don't want any workspace in your Relativity environment to
use the application associated with them.
Admin Guide 66
select Name, [GUID] from EDDS.eddsdbo.LibraryApplication
where Name = 'YourApplicationName'
3. Right-click on your application GUID, and then click Explore in the menu. Windows Explorer opens and dis-
plays a folder with the same name as your GUID. Minimize this window for later use in step 9.
Admin Guide 67
4. Highlight the Default Web Site, and then click View Applications.
5. Right-click on your application GUID, and then click Remove on the menu. Click Yes on the Confirm Remove
dialog.
Admin Guide 68
6. Click Application Pools located under the server name in the Connections pane.
7. Locate the GUID for your application in the Application Pools pane. Confirm that the Application column dis-
plays 0.
8. Right-click on the application pool with your GUID, and then click Remove on the menu. Click Yes on the Con-
firm Remove dialog.
Admin Guide 69
9. Maximize the Windows Explorer window that you opened in step 3. In the left pane, click the Custom Pages
parent folder for your GUID subfolder.
Admin Guide 70
10. Right-click on your GUID folder, and then click Delete. Click Yes on the Delete Folder dialog.
11. Right-click on the CustomPages folder in the Connections pane of the IIS Manager, and then click Refresh.
The tree no longer displays your GUID subfolder under the CustomPages folder.
Admin Guide 71
12. Open Microsoft SQL Server Management Studio. To ignore the custom pages that you want uninstalled, run
the following update statement on the ApplicationServer table in the EDDS. Replace YourApplicationGUID
with the GUID assigned to your application.
update edds.eddsdbo.ApplicationServer
set State = 3
where AppGuid = 'YourApplicationGUID'
This statement sets the state of the custom pages to 3, which indicates that the custom pages should be
ignored.
13. Repeat these steps 1-12 on each server in your environment where you deployed the application.
1. Select the Relativity Applications tab in the workspace containing the application that you want to delete.
2. Unlock the application if necessary. You can't delete a locked application. See Locking and unlocking applic-
ations on page 54.
3. Click the application name to display the details view.
4. Click Delete.
5. (Optional) Click Dependencies in the pop-up window to view a report containing the following information:
l Child objects to be deleted with the application
l Associative objects to be unlinked from the application
6. Click Delete. Relativity deletes the application and its children and unlinks any associative objects.
Admin Guide 72
l Some Relativity applications are pre-populated with instances of object types used to store settings, which you
can modify to control application functionality. Upgrading the application resets these instances, so any modi-
fications made to them are lost. As a best practice, create new instances of these object types in your applic-
ation instead of modifying the default settings. For example, you might create a new profile with your custom
settings in the Imaging application.
Note: You can avoid resetting instances of object types by developing applications that use Post Install event
handlers set to run only once. Using these event handlers, you can create instances of objects and set default
values on them during the initial application installation, but not on subsequent upgrades. See Post Install
event handlers on the RelativityOne Developers site.
l Relativity preserves modifications made to saved searches included in locked applications. For more inform-
ation, see Modifying saved searches in a locked application on the Relativity RelativityOne Documentation site.
l Confirm that any existing application jobs have completed before upgrading out-of-the-box Relativity applic-
ations, such as OCR, search terms report, transform set, or imaging. You may interrupt the current job if you
upgrade the application while it is running.
1. Confirm that you have the appropriate system admin permissions to install an application in Relativity. For more
information, see Workspace security.
2. Select the Relativity Applications tab in the target workspace.
3. Click the name of the application that you want to upgrade.
4. Click Upgrade Application in the Relativity Application console. If you don't see this button, then you don't
have the appropriate system admin permissions.
5. Select Import from file in the Application Type field.
6. Click Browse to select a application file.
7. Click Open on the browse dialog.
8. Click Upload to initiate upgrade script.
Admin Guide 73
priate system admin permissions.
5. Click Continue on the confirmation modal to proceed with upgrading the application in all the workspaces it's
installed in.
l Physically deletes all DLL resource files that were part of the original application version.
l Removes event handler associations on objects types such as Document or Entities.
l Remaps object references in the workspace database to reference the new DLL.
l Eliminates workspace references to resources that no longer exist.
l If an agent of a removed type is currently running, it will complete its work and then self-destruct.
The following application components are not deleted by the upgrade process:
2.10.2.1 Applications from older versions not available after upgrading to Relativity 7.0
If you have Relativity 6.8 or below installed on a workspace, and you upgraded the server to Relativity 7.0, your
application is no longer available. It continues to exist in the database, but the Relativity Applications tab no longer
Admin Guide 74
includes it. You can't export or upgrade the application.
2.10.2.5 Custom pages not working properly when multiple application versions exist on the same server
If you have an application with custom pages in Workspace A, and import a new version of the same application to
Workspace B on the same server, then the custom pages may not function as expected since they are outdated.
However, they continue to display as components of the application.
Admin Guide 75
3 Authentication
RelativityOne uses several industry-standard technologies, enabling versatile authentication options. It supports local
(such as password related) or external (such as external identification 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.
3.1 Permissions
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
l Password—a method that includes a user name, the user's email address, and a password.
l OpenID Connect—a protocol for an external identity provider, authenticating against an external identity pro-
vider using the OpenID Connect protocol. OpenID Connect is a modern authentication protocol can be used to
connect to providers such as Azure Active Directory. See OpenID Connect for more information.
l SAML 2.0—a method that authenticates against an external identity provider using the SAML 2.0 protocol.
SAML 2.0 is an older authentication protocol that is still in widespread use. See SAML 2.0 for more information.
Notes:
l When implementing single sign-on (SSO) across Relativity instances, the following scenarios are supported:
l Identity Provider-initiated SSO using SAML 2.0
l ID provider and service provider-initiated SSO with OpenID Connect
l To log in using PIV/smartcard, configure RelativityOne with an OpenID Connect or SAML provider that sup-
ports PIV/smartcard logins. PIV/smartcards are not directly supported in RelativityOne.
In addition to the above protocols, Relativity has the following additional authentication features:
l Two-factor Authentication—when logging in with the Password method, you can require the user to pass an
additional two-factor check based on an email or message sent to the user's phone, through a mobile email
gateway.
l Mode—always required or require only for non-trusted IPs
l Method—Authenticator App or email. For more information, see the authenticator app's documentation.
Admin Guide 76
l Trusted IP Range—limit access to the Relativity application based on the user's source IP address.
l System admins only—full permissions, including view, update, delete, secure, add
l Login Method
Admin Guide 77
3.3 Configuring Relativity authentication
System admins must assign users at least one authentication method in order for users to log in. To create and to
assign methods, follow these steps.
Note: Adding a new authentication provider of the same type overwrites the existing ones of the same type.
You may only have one instance of each provider type. The exceptions are for OpenID Provider and SAML 2.0
provided types. You can have multiple instances of those if they have different names.
To create an Authentication Provider:
Note: For help with error messages, please see the SSO Troubleshooting console on page 106.
Admin Guide 78
Each provider instance has at least one setting: Enabled. If set to Yes, this authentication provider is available. If No,
you can't use this method to log in with. To enable an instance both this setting and the Enabled for the Authentication
Provider must be set to Yes. If either one is set to No, that method isn't available for the user.
Authentication providers that require additional settings:
l Default Password provider - additional settings for the Default Password provider include:
l Minimum Password Length – sets the minimum number of characters for a password.
l Maximum Password Length – sets the maximum number of characters for a password.
l Maximum Password Attempts Before Reset Required – sets the maximum number of consecutive
unsuccessful login attempts before being locked out. You must send the user a password reset request
before they can attempt to log in again.
l Maximum Password Age (in days) -sets the maximum number of days a password remains valid. The
user will be prompted for a new password on a logon at the expiration date. If set to zero, the password
does not expire.
l Users Can Change Password Default – enables the user to change their password.
l Allow Password Recovery via Email – enables the user to use email to recover a forgotten password.
Yes displays the Forgot Password link on the user's login screen.
l Password Recovery Request Limit – sets the maximum number of password resets before Relativity
locks out the user. You must send the user a password reset request before they can attempt to log in
again. This value resets to zero on each successful log in.
l Maximum Password History – sets the maximum number of previous passwords that users can't use
for a new password. The default value of zero enables any previous password.
l Additional Work Factor – increases the number of encryption hashes. Relativity already provides sev-
eral built in hash levels represented by the default zero value. Changing this value to 1, 2, or 3 adds addi-
tional encryption protection but may significantly increase login time.
Note: The following non-alpha-numeric characters are not allowed: \, ", <, >, £ in passwords.
l OpenID Connect with Microsoft Azure AD - see OpenID Connect on page 91 authentication provider flows.
l SAML 2.0 provider - see SAML 2.0 provider on page 84.
Note: For help with single sign-on error messages, please see the SSO Troubleshooting console on page 106.
Admin Guide 79
l Password below
l Two-factor authentication on the next page
l Password Outside Trusted IP on the next page
3.5.1.1 Password
The password option requires the user to enter only a password for authentication. It does not require an additional
check or two-factor criterion.
To assign and to configure this option for a user:
1. After creating a new user, edit their profile (Users tab, and click their full name).
2. In the Login Method (User) section, click New.
3. In the Login Method Information pop-up window, select the password provider method from the Provider
drop-down list.
The Default Password Settings section appears.
4. Disable the Enable Two-factor Authentication toggle. For more information, see Two-factor authentication
on the next page.
5. Set the Default Password Settings.
l Can Change Password - enable to let user change the password at any point.
l Require Change Password on Next Login - enable to have user change given password.
l Maximum Password Age - enable to set number of days a password can work. Set the number of days
in the text box.
l Set Password for User - enable to create a password for the user.
6. Click Save.
7. Click Send Invitation Email.
This sends an invitation email to the user at the email address listed in their profile’s User Information section.
By default, the link in the email is valid for one week (10080 minutes).
Note: You can use the InvitationLinkLifetimeInMin instance setting to increase the default invitation link expir-
ation period.
If the email can't be sent because your system email SMTP settings are not configured properly, a warning is
displayed.
You can also use the Invite mass action on the Users tab to send invitation email to multiple users.
Admin Guide 80
3.5.1.2 Two-factor authentication
The two-factor authentication is a variation of the Password method that requires a passcode in addition to a
password.
To assign and configure this option for a user,
1. Edit their profile (Users tab, and click their full name).
2. In the Login Method (User) section, click New.
3. In the Login Method Information pop-up window, select the password provider method from the Provider
drop-down list.
The Default Password Settings section appears.
4. Enable the Enable Two-factor Authentication toggle.
5. Select the Mode, "always provide passcode" or "ignore passcode for Trusted IPs."
6. Select the Method, use an "authenticator app" or "email" address.
7. Set the preferred Default Password Settings.
8. Click Save.
For authenticator app, the user will follow the instructions on the app or enter the app's passcode. For email two-factor
authentication, the system emails a passcode to the user during logon, and it's different each time. For more
information on signing in with an authenticator app, see the Admin Guide.
Note: The link in the email is valid for 5 minutes, and only the most recently-sent email can be used. The link
expiration time is not configurable.
Note: Password reset emails are not generated for users logging in via 2FA from an untrusted IP address. To
initiate a password reset in these cases, an administrator must send a reset link from a trusted IP address.
1. After creating a new user, edit their profile (Users tab, and click their full name).
2. In the Login Method (User) section, click New.
3. In the Login Method Information section, select the password provider method from the Provider drop-down
list. The Login Method Settings section appears. You can assign only one instance from among Password
and RSA methods.
4. Select Require only for non Trusted IPs in the Two-factor Authentication section.
5. Enter the user’s email address you want to send the password to in the Email Address field. This address can
be different from the email in the user’s profile.
6. Click Save and then Back.
7. Click Send User Invitation Email.
Admin Guide 81
The second setting specifies a valid IP address or addresses for each user. This can be an individual address, a range
of addresses, or combination of either. The specified range is called the Trusted IPs. Users outside of this range or
ranges won't be able to login except by using Password authentication with the Two Factor Mode set to Outside
Trusted IPs.
To set the user Trusted IP range:
5. Click Save.
By default, no value is empty, which indicates any IP address is valid.
In case of setting the user's Trusted IP range, you can specify an individual address, a range of addresses, or a
combination of either, separate each one with a carriage return.
Addresses use the "###.###.###.###" format. The following wildcards are available for both settings:
Description Example
Asterisk (*) Matches zero or more char- 192.168.31.*. You can't use this notation with the match
acters. range of digits wildcard.
(Asterisk wildcard)
Hash (#) Matches any single digit 0-9. 192.168.31.##. You can't use this notation with the match
(Hash wildcard) range of digits wildcard.
[start-end] Matches a range of digits. 192.168.31. [0-255]. You can't use this notation with the
asterisk and/or hash wildcards.
(Match range of digits
wildcard)
16-bit mask A 16-bit number that masks 192.168.0.0/16 is the same as 192.168.0.0/255.255.0.0.
an IP address. Network address range is 192.168.0.0-192.168.255.255.
24-bit mask A 24-bit number that masks 192.168.31.0/24 is the same as 192.168.31.0/255.255.255.0.
an IP address. Network address range is 192.168.31.0 - 192.168.31.255.
25-bit mask A 25-bit number that masks 192.168.31.0/25 is the same as
an IP address. 192.168.31.0/255.255.255.128.
Network address range is 192.168.31.0 - 192.168.31.127.
Admin Guide 82
l Click Send Password Reset Email.
The link within the email is valid for 15 minutes, and only the most recently sent email can be used.
Note: You can use the PasswordResetEmailExpirationInMinutes instance setting to increase the default
reset link expiration period.
1. After creating a new user, open their profile (Click the Users tab, and then click their full name).
2. In the Login Method (User) section, click New.
3. In the Login Method Information section, select the password provider method from the Provider drop-down
list.
The Login Method Settings section appears.You can assign only one instance from among Password and
RSA methods.
4. Select Set Password to True.
The password requirements appear.
5. Enter the password in the Password field.
6. Re-enter the password in the Retype Password field.
7. Click Save and then Back.
The password information doesn't appear except when you're editing it. If a current password exists, it doesn't appear
either. Each new password overwrites the existing password.
Admin Guide 83
4. Enter the subject identifier for the authentication provider as the OpenID Connect Subject.
5. Click Save and then Back.
Note: As a service provider, Relativity supports SAML IdP-initiated single sign-on (SSO). However, it does not
support SP-initiated SSO.
Relativity uses SAML assertions (tokens) to verify the users mapped to the identity provider. SAML assertions contain
information on the identity of the individual who has logged in. Assertions also contain the identity provider issuing the
assertion, known in Relativity as the Issuer URL. Each Assertion is typically prepared for a specific receiver, known as
the Audience. Assertions protect this information by cryptography signing it. An Assertion is only valid if it is from a
known Issuer URL to the expected Audience and correctly signed.
Note: This documentation contains references to third-party software, or technologies. While efforts are made to
keep third-party references updated, the images, documentation, or guidance in this topic may not accurately rep-
resent the current behavior or user interfaces of the third-party software. For more considerations regarding third-
party software, such as copyright and ownership, see Terms of Use.
3.6.1 Considerations
l SAML assertions must be cryptographically signed for Relativity to verify their authenticity. Make sure your
SAML IdP is configured accordingly.
l You can use Relativity with any SAML 2.0-compliant IdP, such as Centrify, Okta, Microsoft Active Directory
Federation Service (ADFS), or OneLogin.
l RelativityOne only supports the RSA-SHA256 assertion signing algorithm.
l After saving the Authentication provider for the first time, the system generates the Redirect URL. Placeholder
values may need to be added to the third-party Authentication setup before obtaining this value.
Admin Guide 84
l Name—enter a user-friendly name for the authentication provider.
l Provider Type—select SAML2.
l Enabled—the provider is enabled by default, but you can disable it.
l Site URL—set the URL that users enter in the browser to access an instance of Relativity.
Authentication Provider Settings
l Audience—the unique identifier of the service provider (SP). We recommend using the same value as your
Site URL.
l Issuer URL—the unique identifier of the identity provider (IdP).
l Certificate—an x509 certificate provider by the identity provider.
l Subject Claim Type (Optional)—The attribute in the SAML subject used to validate the login. We recommend
to leave this blank.
1. In the Okta admin console, navigate to Applications and search for Relativity.
Admin Guide 85
2. Navigate to the General tab and specify these SAML settings:
l For the single sign-on URL, for enter your Relativity Instance URL. This is the URL that is used for public
access to go to your web servers.
l For Recipient URL, put in a unique identifier, such as the URL for your instance. Note this value for later.
Note: Audience URI is case-sensitive. Specifying /relativity instead of /Relativity can break your
authentication.
l For the Name ID Format you would like to use for logging in, select Email.
l For Assertion Signature, select Signed.
Admin Guide 86
3. You have now partially configured you application in Okta to set up logging in to Relativity. You must now con-
figure the SAML provider in Relativity. These Okta values can be found under the Sign on tab.
l The Audience URI (SP Entity ID, from the previous step).
l The Identity Provider Issuer (In Okta, click View Setup Instructions on the Sign On tab).
l The X.509 Certificate (also in Setup Instructions).
Admin Guide 87
Note: Single Sign On using SAML will not work until you configure the app to trust Okta as an IdP.
Admin Guide 88
5. Select SAML2 from the Provider Type drop-down menu.
6. Enter the site URL. This is the URL users enter into the browser to access this instances of Relativity.
7. Enter the Audience URI (SP Entity ID) from Okta in the Audience field.
8. Enter the Identity Provider Issuer from Okta in the Issuer URL with.
9. Enter the X.509 certificate from in Okta in the Certificate field.
10. (Optional) If you are using a specific user identifier claim that is not the default claim, enter it as the Subject
Claim Type.
11. Click Save.
Admin Guide 89
12. Note the Redirect URL on your new authentication provider.
js
You have now set up your Relativity instance to list for SAML 2.0 assertions at a given endpoint on your server (the
Redirect URL).
Next, finish setting up the SAML IdP in Okta:
You have now configured Okta to send SAML 2.0 assertions to your Relativity instance, and Relativity is set up to
verify the SAML assertions.
Note: You must also assign Okta users to the SAML application, and then map the users to SAML login method in
Relativity. When configuring the login method, you must specify the user's email in the SAML2 Subject field (if you
select Email as the application username in Okta). For more information, see Managing user authentication
methods on page 79.
ADFS
Audience Relying Party Identifier(s) https://[company name].relativity.one/Relativity
Redirect URL End-Point URL https://[company name].relativity.one/Relativity/Identity/<random
string>
Issuer URL Services Trust End-Point http://<adfs-service>/adfs/services/trust
(SAML)
SAML Subject Claim Type Name ID, E-Mail Address, UPN (Leave blank in Relativity SAML Pro-
Name vider configuration)
n/a Claim Rules Incoming, Transformation, Outgoing Claim Rules (see below)
When setting up claim rules, you must send Name ID as default claim type for Relativity. Use these guidelines:
Admin Guide 90
1. Add Send LDAP Attributes As Claims: Select Email Addresses or User-Principal-Name to E-Mail Address from
the AD store.
2. Add Pass Thru Claim for E-Mail Address or a Transforming claim.
3. Add Transforming Claim (from E-Mail Address to Name ID).
Note: 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. The following Authority URLs are already
approved and do not require review: okta.com, login.microsoft.com, login.microsoftonline.com,
login.microsoftonline.us, and login.windows.net.
Note: This documentation contains references to third-party software, or technologies. While efforts are made to
keep third-party references updated, the images, documentation, or guidance in this topic may not accurately rep-
resent the current behavior or user interfaces of the third-party software. For more considerations regarding third-
party software, such as copyright and ownership, see Terms of Use.
Admin Guide 91
l Scopes—the default value for this field is openid. The openid checkbox must be selected because it's a
required setting. However, you can also select the email or profile option. The identity provider responds with
the claims associated with the scopes that you request. In other words, the scopes translate into claims that you
can use.
l Redirect URL—After saving the new Authentication Provider RDO (Relativity Dynamic Object), it will be shown
in the settings.
l Example—<https://company.relativity.one/Relativity/Identity D7158859-3355-46FB-96D1-
78B1B0466AB1>
l Subject Claim Type—the default value for this field is sub. Enter one of the following values based on the
scopes that you set:
l If you selected only OpenID in the Scopes field, this field must be set to sub.
l If you selected OpenID and email in the Scopes field, set this field to email.
l If you selected OpenID and profile in the Scopes field, set this field to a property available from the iden-
tity provider. These properties differ for each provider.
The identity provider sends an identity token to you, which contains the claims for your selected scopes. When
you request only the openid scope, then sub is used as the claim type. It often represents a unique identifier for
the user within your system. If you are using Azure AD, then see Microsoft identity platform ID tokens for a full
list of token identifiers.
l Resource — what is being accessed by your OIDC provider
Note: This value should remain unchanged unless instructed otherwise by your IT department.
l Response Type—specifies how your provider responds to the authentication request. In this case, the
response includes a code.
Note: This value should remain unchanged unless instructed otherwise by your IT department.
l Trusted IPs— specifies a list of trusted IP addresses for a user. Authentication fails if a user attempts to log in
to Relativity from an unauthorized OP address. This list of IPs is evaluated in conjunction with the individual
user's trusted IP list.
l Alternative Issuer(s) - set this field to the issuer in your OpenID configuration if it does not match your authority
URL. Refer to your IT department for guidance on if this field needs to be set
Admin Guide 92
When a user logs in, Relativity checks to see if the client exists, then checks if the user exists. If both exist, Relativity
then checks to see if the user group exists. If all these items exist, the user can log into Relativity. Personal group and
Group claim mapping assignments are checked on every login. Users are assigned/removed to groups on every login,
based on the Group Claim Mappings. For more information, see Group claim mapping below .
To set up just-in-time provisioning on the authentication provider page, complete the fields below.
Note: Group mapping claim values must be present in the token. Just-in-time user provisioning cannot query
external endpoints (such as AzureAD's graph API) to determine group membership.
Any matching claims are then compared to the Group Claim Mappings. Claim values that match the Group Claim
Mappings determine which group to assign a user as a member. If the user claims do not match any Group Claim
Mappings, then the user is removed from that group.
Groups that users are added to outside of group claim mappings need to be administered manually.
Admin Guide 93
3.7.3.3 Personal claim group
The Personal Group feature allows for controlling permissions at the user level within Relativity. Normally,
permissions in Relativity are set on the Group object. By creating a group for every user in Relativity (a user’s personal
group), you can effectively set permissions for individual users. This is an optional feature.
Note: This documentation contains references to third-party software, or technologies. While efforts are made to
keep third-party references updated, the images, documentation, or guidance in this topic may not accurately rep-
resent the current behavior or user interfaces of the third-party software. For more considerations regarding third-
party software, such as copyright and ownership, see Terms of Use.
3.7.4.1 Pre-requisites
l To configure Okta as an OpenID Connect provider for Relativity, you, or your Okta admin, will need to set up the
Relativity app in Okta. To complete this part of the configuration, follow the steps in the Okta documentation.
During the process, select Web as the platform and OpenID Connect as the sign-on method. After completing
the steps provided by Okta and customizing the steps for Relativity, you will navigate back to Relativity.
l The Okta ‘Initiate login URI’ setting may need an HRD parameter. For more information, see Creating or editing
a federated instance.
The identity provider responds with the claims associated with the scopes that you request. In other words, the
scopes translate into claims that you can use.
Admin Guide 94
l Subject Claim Type—the default value for this field is sub. Enter one of the following values based on the
scopes that you set:
l If you selected only OpenID in the Scopes field, this field must be set to sub.
l If you selected OpenID and email in the Scopes field, set this field to email.
l If you selected OpenID and profile in the Scopes field, set this field to a property available from the iden-
tity provider. These properties differ for each provider.
The identity provider sends an identity token to you, which contains the claims for your selected scopes. When
you request only the openid scope, then sub is used as the claim type. It often represents a unique identifier for
the user within your system
Configure Okta
Once you configure the authentication provider, you'll need to assign it as a login method to your users. To complete
the configuration in Relativity, navigate to the User and Group Management > Users tab. For complete steps on
configuring an OpenID Connect login method, see OpenID Connect on page 83.
3.7.5.1 Pre-requisites
Before you begin you must have the following items completed.
1. Navigate to the primary instance and set up an OAuth2 client. You must specify Implicit as the OAuth2 Flow.
Note that initially you don't have the redirect URL value (you get it when you set up the Authentication Provider
on the secondary instance), so specify any placeholder URL instead. For more information, see OAuth2 clients
on page 99.After you save the OAuth2 client, note the generated value of the Client Id. This is required to set up
the authentication provider in the secondary instance.
Admin Guide 95
2. Navigate to the secondary instance and configure a new OpenID Connect authentication provider using the Cli-
ent Id value from the previous step. Note that the OAuth2 Flow values must also be Implicit, and the Authority
URL must point to the Relativity Identity service of the primary instance. An example of a Redirect URL is
https://mycompany.relativity.one/Relativity/Identity.
3. After you save the provider, note the generated value of the Redirect URL. It is required to complete the OAuth2
client setup in the primary instance.
4. Set up the user(s) to use the Authentication Provider as the Login Method, specifying the user's email (Relativ-
ity user ID) as the OpenID Connect Subject field value. For more information, see Managing user authen-
tication methods.
5. Navigate back to the primary instance and update the OAuth2 provider with the Redirect URL.
6. In the primary instance, set up a federated instance pointing to the secondary Relativity instance. Note the use
of the Home Realm Discovery (HRD) URL parameter to provide a single sign-on experience. The Home Realm
discovery URL is generated when the Authentication Provider is created and can be found in the Authentication
Provider Information section of the Authentication Provider page. For more information, see Federated
instances on page 107.
7. Navigate back to the secondary instance and set up a federated instance pointing to the primary Relativity
instance. Don't set up the HRD redirect for that federated instance.
8. Log out of the secondary instance.
9. Use the federated instance link to log in to the secondary instance from the primary instance.
10. Use the federated instance link in the secondary instance to return to primary instance.
Admin Guide 96
You have now configured a Relativity environment to serve as an authentication provider for another Relativity
instance.
Note: 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.
Note: This documentation contains references to third-party software, or technologies. While efforts are made to
keep third-party references updated, the images, documentation, or guidance in this topic may not accurately rep-
resent the current behavior or user interfaces of the third-party software. For more considerations regarding third-
party software, such as copyright and ownership, see Terms of Use.
Admin Guide 97
Authentication provider settings
l OAuth2 Flow—select either Implicit or Code.
l Client ID—enter the Entra ID's Application ID.
l Display on Login Screen—determines if the OpenID Connect button displays on the login page.
l Login Screen Button Text—determines the text that appears on the button displayed on the login page.
l Authority URL—enter the Authority from the trimmed OAUTH 2.0 AUTHORIZATIONENDPOINT from step 9 in
Configuring your external identity provider.
l Scopes—the default value for this field is openid. The openid checkbox must be selected because it's a
required setting. However, you can also select the email or profile option. The identity provider responds with
the claims associated with the scopes that you request. In other words, the scopes translate into claims that you
can use.
l Subject Claim Type—the default value for this field is sub. Enter one of the following values based on the
scopes that you set:
Notes: In Microsoft Entra ID, email is an optional claim and is not included in the OpenID token by default.
Consider using upn instead. Consult with your Entra ID administrator to determine which claim type is best
suited for your organization. For more information, see the Microsoft documentation on optional claims.
l If you selected only OpenID in the Scopes field, this field must be set to sub.
l If you selected OpenID and email in the Scopes field, set this field to upn.
l If you selected OpenID and profile in the Scopes field, set this field to a property available from the iden-
tity provider. These properties differ for each provider.
The identity provider sends an identity token to you, which contains the claims for your selected scopes. When
you request only the openid scope, then sub is used as the claim type. It often represents a unique identifier for
the user within your system. If you are using Entra ID, then see Microsoft identity platform ID tokens for a full list
of token identifiers.
Admin Guide 98
5. Navigate back to the Authentication Provider in Relativity.
6. Click Edit.
7. Paste the value for Client Secret with the value from step 4.
8. Click Save.
Note: This documentation contains references to third-party software, or technologies. While efforts are made to
keep third-party references updated, the images, documentation, or guidance in this topic may not accurately rep-
resent the current behavior or user interfaces of the third-party software. For more considerations regarding third-
party software, such as copyright and ownership, see Terms of Use.
OAuth2 clients can be used in conjunction with Relativity authentication providers and federated instances in different
enterprise integration scenarios, including:
Admin Guide 99
1. Open the OAuth2 Client tab.
2. Click New OAuth2 Client to create a new OAuth2 client, or click Edit next to the OAuth2 client you want to edit.
The OAuth2 Client Information form appears.
3. Complete the fields on the form. Fields in orange are required.
l Name—the descriptive name of the OAuth2 client. The name must be unique.
l Enabled—yes/no value indicating whether the client will be given access to Relativity.
l Flow Grant Type—the mechanism for acquiring an authentication token also known as OAuth2 grant
type. Relativity supports the following grant types:
l Client Credential—for applications such as background processes that may need to get an
access token for their own account, outside the context of any specific user. This grant type
requires a client secret.
l Code—for apps running on a web server. The grant type is used to obtain both access tokens and
refresh tokens and is optimized for server-side applications. The client must be capable of inter-
acting with the resource owner’s user-agent (typically a web browser) and capable of receiving
incoming requests (via redirection) from the authorization server. This grant type requires a client
secret.
Note: You can't change the flow value when editing an OAuth2 client.
Note: To obtain a refresh token, it is necessary to use an Authorization Code with a Proof Key for
Code Exchange (PKCE) flow.
l Trusted IPs - An optional feature for the OAuth2 client object. Enter each IP address on a new line, and
use CIDR notation to specify a range of IP addresses. The system checks trusted IPs whenever a token
is requested using the OAuth2 client's ID and secret. If the request comes from an IP address outside the
specified range, the system returns a 400 error with the message "invalid_client. IP address not
allowed."
4. Click Save. The form displays the new OAuth2 client with these generated field values:
l Enabled—yes/no value indicating whether the client will be given access to Relativity.
l Flow Grant Type—the mechanism for acquiring an authentication token also known as OAuth2 grant
type.
l Redirect URLs—the URLs that the user can be redirected back to after the request is authorized.
l Access Token Lifetime—the duration (in minutes) for which access tokens issued to the clients are
valid.
l IsSystem— specifies whether the OAuth2 client is part of an internal Relativity application.
l Client Credential
l Resource Owner
l Code
1. From the OAuth2 client tab, locate and open the OAuth2 client you wish to delete.
2. Click Reset Secret in the OAuth2 Client console.
3. From the confirmation dialog, click Ok. The OAuth2 client secret is reset.
1. From the OAuth2 client tab, locate and open the OAuth2 client you wish to delete.
2. Click Delete.
3. From the confirmation dialog, click Ok. The OAuth2 client is removed.
1. From the OAuth2 client tab, locate and click the OAuth2 client for which you wish to view its history.
2. Click View Audit. A dialog appears, listing all actions taken on that OAuth2 client.
3. (Optional) Using the Export to File drop-down list at the bottom of the dialog, click Go to export the following
audit history details in a .CSV file:
l User Name
l Action
l Timestamp
4. Close the dialog when finished viewing the audit.
Note: RelativityOne Connect cannot be used to connect two instances owned by the same customer (or their global
entity). In order to connect two instances owned by the same customer, please see Linking additional Relativity
instances
Note: If you don't see the RelativityOne Requests section, you are not the RelativityOne Primary Contact.
Please make sure you are logged in as the primary contact to move forward in requesting a form.
3. In the RelativityOne Request page, click the Choose Request Type drop-down menu.
4. Select RelativityOne Connect.
5. Click Next.
This opens the RelativityOne Connect Request Form.
Once submitted, Relativity can confirm the RelativityOne primary contacts email addresses and instance names.
Once confirmed, a new authentication provider option is available when updating a user's login method.
Note: To connect to more than one RelativityOne instance, you will need to submit multiple requests.
Once the request has been submitted, Relativity can confirm the RelativityOne primary contacts email addresses and
instance names. Once confirmed, a new authentication provider option is available when updating a user's login
method.
Note: The OpenID Connect subject is the user email address in the other instance.
5. Click Save.
An already existing user also needs the default password provider login method removed.
Each instance has that instance’s group and security permissions. If the users already exist from previous
engagements, no action is needed.
Note: 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.
Once clicked, you need to confirm your credentials with your SSO provider. Once confirmed, you can navigate within
the newly opened instance.
3.10.1 Considerations
l This console should not be utilized for auditing purposes.
l You must have the Edit permission on the Authentication Provider object to view the console.>
l The error log will only show the 10 most recent error messages.
3. Review the errors and make the necessary updates to resolve the issue.
4. Once the errors have been resolved, clear the error log.
You can use federated instances in combination with OAuth2 clients and authentication providers to enable single
sign-on for multiple environments in your Relativity ecosystem.
Note: Customers utilizing the same third-party OIDC provider (e.g., Okta, EntraID) in both instances can use the
Authentication provider's HRD hint to streamline the connection process, eliminating the need for manual linking.
l Instance URL – the URL address of the instance you want to create a link to. To obtain this URL, nav-
igate to the Relativity instance you want to appear in the drop-down menu. Copy and paste the URL from
that instance into this field.
You can also choose to add the Home Realm Discovery (HRD) parameter to mimic single sign-on exper-
ience inside your Relativity cluster. HRD is a redirect URL to a configured authentication provider for the
federated instance. It is supported for OpenId Connect.
Locate the Home Realm Query Hint (HRD parameter value) within the provider-specific details section
of the Authentication Provider tab.
To establish a link to a specific instance, return to that instance and input the Home Realm Query Hint
(HRD parameter value) within the designated Instance URL field.
https://mycompany.com/Relativity?HRD=<Provider Name>
Note: The authentication provider must be set up correctly for single sign-on to work. If the authen-
tication by the provider fails, the user will be presented with the login screen of the Federated Instance.
4. Click Save.
The federated instance will appear in the User drop-down menu.
You can restrict access to the federated instances you create using the padlock icon and assigning the appropriate
groups access to the instance. If you restrict access to a federated instance, it doesn't appear in the User drop-down
menu.
Note: You may want to consider using Review Center as a streamlined alternative. For more information, see the
Review Center guide.
Note: If you select a value in the Family Field, then the batch set will include family documents from that
related group that are also included in the data source.
The Batch Set Information form appears with required fields in orange.
Complete the fields to create or edit the batch set. See Fields on the next page.
3. Click Save.
4.2.2 Fields
The following fields display on the New Batch Set information form:
Note: If you are performing a multi-stage review with multiple batch sets per phase, be sure to include the
phase name in the batch set name. This helps you search for information within a specific phase.
Note: Your batch may contain fewer documents than this value if there are no more documents to batch or no
more documents with the current Batch Unit value.
Note: A common batch unit field is custodian. However, you can use any single choice, multi-choice, single
object or non-relational and non-system fixed length text field.
Note: If you select a Batch Unit Field option and a Family Field option, batches will assign documents up to
the Maximum Batch Size for the Batch Unit Field using only parent documents. Once the parent documents
have been included, the family documents are then added to the batch. For example, if you have a Max Batch
Size of 100, and choose Record Type for the Batch Unit field, up to 100 documents with unique family iden-
tifiers are added to the batch first, and then the respective family documents are added afterward. This can
cause larger batches than using the Family Field alone.
When using multiple choice fields for the Batch Unit Field, the choice values must be the same in order for them
to be grouped in a batch. If the combination of choices is unique enough for the choice values, Relativity
batches the documents into separate batch groups.
l Family Field—you can select your workspace group identifier. Documents in a family group are not split across
batches, even if their batch unit field differs.
Note: When you select a value for Family Field, the resulting number of documents within each batch may be
larger than the value for the Maximum Batch Size field. For example, if you set the maximum batch size to
100, the first 100 documents that the batch source returns puts into the first batch. After this is done, any fam-
ily members to the documents in the first batch are then included in that batch. This may result in the batch
being larger than 100. Depending on the size of your family groupings, the size of your batches may vary sig-
nificantly.
l Reviewed Field—an optional field that you can select from any yes/no, single-choice, or multi-choice field from
the drop-down menu. Based on your selection, a tally is kept of how many documents in the batch have been
reviewed. The batch set monitors the field you specify as the Reviewed field. It also increments a count for each
document in the batch that has been coded with a value for that field.
Note: With auto batching enabled, the Relativity service account runs the saved search specified as your
batch data source. The Relativity Service account is a system admin account.
l Create Batches—creates the batches based on the entered settings. Created batches display on the bottom
half of the batch set details page.
l Purge Batches—deletes any batches associated with the entire batch set.
l View Batch Summary Report—displays the Batch Summary report. This field is only enabled after you have
created batches.
l Refresh Page—refreshes the page.
Note: Previously created batches do not update to include new properties. For example, if you create batches with
a batch size of 500 and then need to lower the size, you should purge the existing batches. You can then make any
changes and recreate the batches. You will lose any existing data in the original batch set when you purge those
batches.
l Status—displays the current status of the batch: Pending, Processing, Error or Finished
l Documents to be Batched—displays the remaining documents that do not meet the minimum batch size. You
must manually create a batch for these remaining documents.
l Last Successful Run—the date and time stamp of the last successful batch run.
l Last Error Reported—the date and time stamp of the last error that occurred.
l Field: Batch
l Operator: not these conditions
l Value:
l Field: Batch::Batch Set
l Operator: any of these
l Value: select all existing batch sets
Documents included in the batch sets you select for the Batch::Batch Set field value are excluded from your search
results.
Note: If you want to run a search that excludes only certain batch sets select these conditions as the first operator.
Select none of these as the second operator. Documents belonging to more than one batch set may return in your
search results. Using this combination of search operators returns documents that belong to any batch set you don't
specify in the Batch::Batch Set value.
l Applying views to the batches tab, creating any list of batches you’d like to see. You can restrict these views.
l Securing batch sets, where you can then assign permissions to all batches in a batch set.
l Securing individual batches.
Note: Reviewers can assign batches to other reviewers with the Assign Batches permission. Reviewers without this
permission can only check out batches for themselves. By default, reviewers don't have this permission.
Note: System admins can't check out batches using the Me link.
Reviewers can check out batches one at a time but they may assign multiple batches to themselves or others as
needed. A batch may also be checked out for as long as desired. Reviewers need to check in the checked out batch
as Completed or Pending before they can check out another. A batch that has been checked in as completed can still
be checked out again.
Note: You can select the Check in as completed option even if not all of the documents have been
reviewed.
1. Under the field that you want to add a new choice, click Manage. The Manage Choices window opens.
2. Click Add Choice or Click to add a choice.
3. (Optional) Click Options to customize the choice, and then click Apply.
4. Click Apply.
Note: You can't create more than 300 choices at one time. If you attempt to create more than 300 choices at one
time, then only the first 300 choices get created.
1. From the Choice editor, click Add List of Choices. The Add List of Choices textbox appears.
2. Enter each choice on a separate line. You can also copy and paste a large list of choices, but ensure each
choice is entered on a separate line.
3. (Optional) To create families of choices, use hyphens at the beginning of each separate line. Each hyphen rep-
resents a level between parent and child choices. If a choice contains a hyphen, but there is no parent relation,
a warning will display.
4. Click Save.
1. Navigate to the Choice editor. See Accessing the Choice editor on page 117.
2. Click on the name of the choice that you want to rename.
3. Enter the new name of the choice. The new name is automatically saved.
1. Navigate to the Choice editor. See Accessing the Choice editor on page 117.
2. Hover over the name of the choice that you want to edit.
3. Click Details.
4. Modify the details of the choice. See Choice detail fields below.
5. Click Save.
1. Navigate to the Choice editor. See Accessing the Choice editor on page 117.
2. Hover over the name of the choice that you want to delete.
3. Click Delete.
You can also delete multiple choices using the Delete mass operation from the Choices tab.
To create a child choice, click the choice row and drag the choice into a preexisting choice. The preexisting choice
becomes the parent choice. A double blue bar appears under the new parent tab where the child tab is moved to.
Notes:
l You must have edit permissions for the field to reorder choices. If you don't have edit permissions for the field,
the Reorder A-Z button will not appear in the Choice editor.
l Once you alphabetize the choices you can also rearrange choices within the sort. The alphabetize button will
not automatically re-alphabetize the choices if you move choices individually.
Note: It is a suggested practice to order your choices in multiples of 10 so that it is easier to insert more choices in
your intended order in the future. If you enter choices with orders that are not in multiples of 10 and use the Sort top
level choices feature to reorder your choices, then Relativity automatically reorders all previously entered order num-
bers in multiples of 10.
Note: We recommend setting the tab order by 10's, starting with 10, then 20, 30, etc. Numbering in groups of
10 lets you later insert an item into any position without reordering all items (e.g., 10, 20, 25, 30, 40).
l Parent choice - when you create a sub-choice, you can select a parent choice under which the current choice
appears. Be aware that once you set your family of choices and tagged values, editing a parent choice causes
inconsistencies.
Note: If you need to change a parent choice, create a new choice family, mass edit the applicable doc-
uments, and then remove the old choice.
l Relativity Applications - associate an existing application in your workspace to the new choice, in order to link
to Relativity Dynamic Objects. See Building Relativity applications.See the Applications section in the Admin
guide.
l Keyboard Shortcut - designates a keyboard shortcut for the document choice you're editing or creating. You
can use the shortcut to code and edit documents in the Review Interface. You need to be in edit mode before
you can use keyboard shortcuts for choices. This setting is only available for document fields and consists of
the following checkboxes. You have to use Ctrl and/or Alt or you get an <Invalid Keyboard Shortcut> warning
next to the Key drop-down field:
l Ctrl - sets the Control key as part of the combination used to trigger the keyboard shortcut.
l Alt - sets the Alt key as part of the combination used to trigger the keyboard shortcut.
l Shift - sets the shift key as part of the combination used to trigger the keyboard shortcut.
l Key - sets the key you want to use in combination with the key specified in one or more of the check-
boxes (Ctrl, Alt, and Shift).
1. Click your name in the upper right corner of Relativity and click Home.
2. Click the Choices tab.
3. Click New Choice. If you want to edit an existing choice, click the Edit link next to the Choice name.
4. Complete the fields on the form. See Admin fields on the next page.
5. Click Save.
Note: We recommend setting the tab order by 10's, starting with 10, then 20, 30, etc. Numbering in groups of 10 lets
you later insert an item into any position without reordering all items (e.g., 10, 20, 25, 30, 40).
You can also add or edit an admin choice on the Choices tab. See Adding choices on page 120.
1. Select the Clients tab and then click New Client to create a new client, or click Edit next to the client whose
information you want to edit. The New Client form appears.
Note: If your Clients tab view list does not contain the Edit field, you can add it.
6.1.1 Fields
The following fields display on the Client Information form. Fields in orange are required.
l Name - the name of the client. The name must be between 1 and 210 characters.
l Client Number - the billing number for the client. This value must be between 1 and 50 characters.
l Status - the current status of the client. The default options are active or inactive, but you can add any status
value. Use the status value to organize and display lists of clients using Relativity views. See Views on
page 632.
To request a new client domain, you must submit a RelativityOne request via the Community site by navigating to the
Support tab and then RelativityOne requests (as detailed in the following knowledge article). Please note that the
Client Domain creation process takes 3 business days. If an Utility Server was requested, you will also be contacted
with the following information:
l The system creates a new Everyone - [Client's Name] group and adds that group to the client domain. Only
users whose client field is set to the client domain are included in the client domain everyone group. The system
also removes those users from the default Relativity Everyone group. A system admin can add any users to any
group regardless of client domain status.
Note: The Everyone - [Client's Name] group should not be assigned as the workspace administrator group
for a given workspace that is part of a Client Domain.
Note: Permissions assigned to groups override client domain isolation. If a non-client domain group has per-
missions to see a client domain's workspace or users, then those non-client domain users in the non-client
domain group can still access client domain items. Enabling client domains does not change previously con-
figured item level security settings applied to any objects within the client domain.
l The system creates a client domain admin group that permits its members to perform admin operations within
the client domain.
l The Billing statistics - RelativityOne - case rollup and Billing statistics - users reports include columns called Cli-
ent Domain Name and Client Domain Artifact ID. These columns display client name and artifact ID when you
enable client domains for a client.
Note: After enabling client domains, system administrators needing to make group or permission changes
should be extra cautious and thoroughly investigate the potential impact to client domain separation before
implementing any new group/permission changes.
Note: For a list of dashboards that provide an effective starting point for administrators to help review teams
visualize their data set, see Common commonly-used dashboards in the Admin Guide.
The page initially appears with the folder browser on the top left, the search panel on the bottom left and the item list to
the right. Within this new framework, you have multiple options for customizing your display.
You can resize, move, or collapse any panel on the page, including any widgets you create.
l To resize any panel, hover over the line separating the item list from the panel until you see the mouse pointer
change to horizontal arrows, then click and drag.
l To move, hover over the top of the panel until you see the Multi-Direction Cursor icon. Then, click and drag the
panel to the new location.
l To collapse the search panel or browser pane, click the Collapse icon. Once collapsed, click the Show
Browser Panel icon to restore the browser pane or the Show Search Panel icon to restore the search panel.
Additionally, you can drag and drop panels to rearrange on the page. Click any panel and drag it to a new location. The
other panels will automatically move to accommodate the panel you're dropping.
Note: You must have the correct workspace permissions to add, edit, or save a dashboard and to save pivot
widgets to your dashboard.
You can also export individual Pivot widgets to Excel or to PNG format from each widget's context menu. See
Exporting a Pivot widget in the Admin Guide for more information.
Note: To enable the Add Widgets button and Pivot functionality for an Relativity Dynamic Object (RDO), you must
select Enabled for the Pivot property in the Object Type Information section for the object.
1. Click the Dashboards drop-down menu in the top right corner of the screen.
Note: You can only access the drop-down if Pivot is Enabled for the given object type.
2. Click New Dashboard to save the current page configuration as a new dashboard.
3. Enter a name and an order number for the dashboard.
Note: The dashboard with the lowest order number will appear by default when you log in to Relativity.
l Pivot charts and tables—you can use Pivot to summarize data in tables or charts to visually analyze trends in
your data.
l Cluster visualizations—on the Documents tab, you can use Relativity Cluster Visualization to render your
cluster data as an interactive visual map by adding a Cluster Visualization widget. This offers you a quick over-
view of your document cluster sets and quickly drill into each cluster set to view sub-clusters and conceptually-
related clusters of documents. Please note that there may be only one cluster visualization widget per dash-
board.
l Communication Analysis—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.
Note: When you reach the maximum number of widgets allowed on a dashboard, the Add Widget button will be
grayed out and a tooltip displays when you hover over it that lets you know the reason you cannot add any additional
widgets to your dashboard. This is controlled by the MaxNumberDashboardWidgets instance setting.
1. Click the Dashboards drop-down menu in the top right corner of the screen to display the list of dashboards
available on the current tab.
2. Click Save to save the changes to the existing dashboard. Click Save As to save the page configuration as a
new dashboard, and then enter a Name and Order number.
Note: If a dashboard is part of a locked application, the option to save the dashboard is unavailable.
Note: If a dashboard is part of a locked application, the option to delete the dashboard is unavailable.
1. Click on the Edit icon next to the name of the dashboard in the Dashboard drop-down menu.
2. Enter a Name and an Order number for the dashboard. The order number controls the order in which the dash-
board displays in the list.
3. Click Save to save your changes.
Note: If a dashboard is part of a locked application, the option to edit the dashboard is unavailable.
1. Ensure the search panel is expanded. If it is hidden, click on the Show Search Panel icon in the upper-left.
2. Ensure that the Auto-run field in the search panel is enabled.
3. Click Clear All Conditions.
Note: Exporting to Excel functionality does not require Microsoft Excel to be installed (except for viewing of the
exported file).
1. On your current dashboard, click the Export button to the right of the Dashboard drop-down to export your dash-
board with the currently selected export format settings.
Alternatively, click the drop-down arrow to the right to make the following export format setting selections, and
then click the Export button at the bottom of the drop-down menu. By default, all listed items are selected, but
the individual selections that you make persist until you change them.
l Dashboard name - selecting this means the name of the dashboard will be included in the export.
l Export date and time - selecting this means the date and time of the export will be included in the
export.
l Show data worksheets - selecting this means the data for the individual widgets will be included in the
export (and you can then modify this data).
l Relativity logo - selecting this means the Relativity logo will be included in the export.
Note: If you export a scroll-able table widget, it will not be shown on the Full Dashboard worksheet tab.
3. You can modify the data on the relevant worksheet for the chart and all the charts including the Full Dashboard
worksheet update to reflect the modified data using Excel's built in chart functionality. Furthermore, the data
table is sortable and filterable—the chart will reflect the data listed in the table. You can refer to user doc-
umentation on how to use charts in Microsoft Excel for more information on modifying these charts for other pur-
poses.
Note: You cannot modify any cluster visualization using Excel, since this is just a PNG image of the visu-
alization.
l The fields described here may differ in name than what you see in your workspace.
l When adding a widget, you cannot select fields that have not been enabled for pivot on or group by; you must
manually enable those fields in order to select them. If those fields are part of a locked application, you must
unlock it in order to edit them.
l A widget will not render if the included fields do not contain any data. For example, if you attempt to create an
STR-based dashboard without having run STR on key terms, you will see the following:
l Group by Custodian
l Group by Custodian and pivot on Sort Date (Year)
l Group by Unprocessable
l Group by Track Changes
l Group by Password Protected
l Group by File Type
l Group by Has Hidden Data - this widget is collapsed in the dashboard example below.
Note: You can collapse your widgets, as seen in Has Hidden Data below. If you save your dashboard with a widget
collapsed, it will remain collapsed.
l Group by Privilege
l Group by Privilege Designation
l Group by Privilege Terms STR
l Group by Custodian
To create the Pre-Production QC dashboard, group by and pivot on the following fields:
l Group by Custodian
l Group by Responsive Designation
l Group by Privilege
l Group by Key Term STR
l Group by Has Images
l Group by Issues
Note: We recommend using your Email Threading view with this dashboard.
Note: We recommend using your Language Identification view with this dashboard.
l
Document Compare—displays the Document Compare icon. Use Document Compare to compare the
extracted text of one document to another.
Note: Document Compare is particularly useful when working with groups of near duplicates or conceptually
similar documents.
Note: This is just the location folder, not the full folder path.
l Has Images—a single choice field indicating whether a document has images.
l Has Natives—a yes/no field indicating whether a document has natives.
l Has Inline Tags—a yes/no field indicating whether a document has a right-click tag markup.
l Relativity Image Count—the number of non-production images associated with a document.
l Relativity Native Time Zone Offset—This field adjusts how header dates and times appear in the Native
Viewer for emails. If the field is blank or set to 0, the Viewer displays dates and times in Coordinated Universal
Time (UTC).
l This field only affects how header dates and times appear for email messages in the Viewer. It does not
apply to images or extracted text, and it does not modify the actual metadata fields.
l If Relativity did not process the documents, the system calculates the time zone offset based on available
metadata in the following order:
1. EmailSentOn
2. EmailReceivedOn
3. LastModified
If none of these fields exist, the Relativity Native Time Zone Offset field remains empty.
Note: Relativity does not automatically account for DST adjustments for data processed outside of
Relativity. To apply DST, use the Set Native Timezone Offset with DST script. Only Relativity admin-
istrators can deploy this script. For more information, see Set native time zone offset with DST .
l Relativity Native Type—the type of native file loaded into the system. The system assigns this value.
l Supported by Viewer—a yes/no field indicating whether the viewer supports the native document.
l System Last Modified On—the date and time at which the document was last modified.
l System Last Modified By—identifies the user who last modified the document.
l System Created On—the date and time when the document was created.
l System Created By—identifies the user who created the document.
l <Markup Set Name>—created when a user creates a markup set. Its values are:
l Blank when the document has no highlighting or redactions for the markup set
l Has Redactions when the document has redactions for the markup set.
l Has Highlights when the document has highlights for the markup set.
Note: If a highlight or redaction is created using a third-party application or script, this field may not
automatically update.
l <Production Name>—created when a user creates a production. This field stores how the document was
added to a production. It is either blank, contains Images Only, Natives Only, or Images and Natives.
l Production Alerts—a yes/no field to warn of any production execution problems
Note: You can add an Edit link to your field list view if it does not already exist.
3. Input and modify field information on the field details page. If you are creating a new field, the Field Information
section must be completed before the remaining sections will display. See Fields below.
Note: You can not change a field's type after creating the field. See Field types on page 160.
8.4 Fields
The fields object includes the following field sections:
l Field information
l Field settings
l Advanced settings
l List and dashboard settings
l Choices
Note: You can create new objects within Relativity. These dynamic objects are securable, non-doc-
ument objects within your workspace. By connecting objects to each other you can create powerful cus-
tom applications within your workspace.
l Field Type—determines the field’s functionality and presentation. For example, a Yes/No field type indicates
that the reviewer must choose a value of either yes or no to edit the field.
l Associative Object Type—an object that the single object or multiple object field type uses to create a rela-
tionship. The objects selected in the Object Type and Field Type options determine the available associative
object types.
l Available in Field Tree—places the field and its choices in the Field Tree browser.
l This field defaults to no.
l This field is only editable for Document object type fields. The field type must be one of the
following: single choice, multiple choice, single object, or multiple object.
l Available in Viewer—displays the field in the viewer. The user can then check text against the original doc-
ument or image. This setting is only editable for long text fields with a Document object type. If set to Yes, the
field is available in a drop-down menu on the Extracted Text setting in the viewer.
Note: Copies of reflected fields are not available in this drop-down menu. If you select an empty long text
field in the viewer, the viewer displays a blank page.
l Default Overlay Behavior—defines how Relativity handles multiple choice or multiple object fields when
importing a load file.
This field defaults to Merge Values and is only available for multiple choice and multiple object fields.
l Formatting—determines the field’s format and only applies to the following fields:
l Date—displays only the date.
l Date+Time—displays the date and time.
l Use Thousands Separator—if enabled, a comma displays between digits where appropriate for
decimal and whole numbers fields.
l Whole Number—none displays the value as a string of numbers. Integer displays the value with com-
mas separating each group of three digits.
l Identifier—indicates if the field is the workspace’s unique identifier with a value of yes or no. You are unable to
edit this field.
l Include in Text Index—adds the field values to the workspace’s SQL text index, making the field searchable
via keyword search.
l Maximum Length—the value entered is the maximum number of characters permitted in the field. The value is
set to 50 by default.
l "No" Display Value—determines how a "no" value displays in a list. No is the default value but you may edit it
as desired.
l Required—determines whether the user must populate the field on a layout with information in order to con-
tinue coding documents. This does not apply when loading workspace data. Fields that are required on a cod-
ing layout display with a star next to them.
l Store in Data Grid—This option allows you to store Long Text fields in Relativity Data Grid, but it's only access-
ible if you've configured a valid endpoint URL. Once available, it's enabled by default with the filter type set to
"none".
l Disabled—saves all data imported into this field to the SQL Server.
l Enabled—saves all data imported into this field to the Data Grid.
Caution: If you have existing long text fields stored in SQL, you can use the Data Grid Text Migration
Application to migrate those fields from SQL to Data Grid. For more information, see Data Grid Text
Migration application.
Note: Once you enable a field for Data Grid, you cannot disable it. The option to edit the field is unavail-
able after you save.
l "Yes" Display Value—determines how a "yes" value displays in a list. Yes is the default value but you may edit
it as desired.
Note: When storing in Data Grid, users will not be able to use bulk operations, filter on document
pages, pivot and sort, or utilize fields in layouts (including on the document panel). For more inform-
ation about storage in Data Grid, please see Processing to Data Grid
l Auto Add Choices—adds all choices associated with a single or multiple choice field to an application. This
property only applies to single and multiple choice fields.
Note: If you are changing this property from No to Yes and you did not add the field to applications in your
workspace, the choices are not added until you re-add the field to each application. The Relativity Applic-
ations property in this section lists each application to which this field is currently assigned.
l Enable HTML—indicates whether or not to allow HTML code to execute within the field.
l Enabled—executes the code when the layout displays the field.
l Disabled—displays the field as plain text.
Notes: Using allow HTML, you can configure Relativity to throw an alert when the field appears in a layout.
HTML will always display as plain text in a view. The AllowHTMLVisible instance settings table value controls
whether or not the Allow HTML value displays on the Field page.
Note: For Field Tree View, you can select any view you have rights to see. However, a warning appears
when you attempt to save the field, if the selected view is personal. If you edit the view selected as the Field
Tree View, you receive a warning when you attempt to save it as a personal view.
The Field Tree View property includes two icons:
l
edits the view by opening Conditions, step 3 of 4, in the view wizard.
l
creates a new view from Basic Information, step 1 of 4, of the view wizard.
l Field Type—the type of the catalog field to which you are mapping. This must match the type of the field you
are creating or editing.
l Keyboard Shortcut—you can define a keyboard shortcut for the document field you are editing or creating with
keyboard shortcuts. You can then use this shortcut to code and edit documents in the Review Interface. This
setting is available only for document fields.
You can use the following key options to define the shortcut trigger. You must use Ctrl, Alt, and/or Shift, and the
workspace cannot have duplicate keyboard shortcuts.
l Modifier Keys—check the desired key option to define the shortcut trigger. You must use Ctrl, Alt,
and/or Shift. The workspace cannot have duplicate keyboard shortcuts.
l Main Keys—click on the drop list and click on the desired key to use in combination with the other spe-
cified keys.
Note: You can modify the key combinations for system keyboard shortcuts if you have the Modify System
Keyboard Shortcuts security permission.
l Keywords—allows you to enter words that describe the field you are creating. There is a 50 character limit.
l Length—the length of a fixed-length text field.
l Defaults to 255 characters.
l Maximum length is 4,999 characters.
l Maximum length is 4,000 if Unicode enabled.
l Linked in List—sets the field as a hyperlink. In the example below, the Date Sent field was set to Linked: Yes.
As a result, Date Sent appears as a hyperlink in the view. Clicking the date launches the related document in
the viewer. Similarly, clicking any link in the document record also launches the document in the viewer.
l List Column Width—the width, in pixels, of the column in the view. To accept Relativity’s default, leave this
field blank.
l Notes—allows you to enter words that describe the field you are creating. There is not a character limit.
l Open to Associations—determines whether an object field can display its information on an associated object
field. Fields that are open to association are sometimes referred to as reflected fields. Reflected fields can be
re-named and exported via the Export to File mass action.
l When you open a field to association, that field’s information is viewable and editable on an associative
list found on the object with which you associate it.
l For example, you have two associated objects: Entity and Company. You want to add a field called
Address to hold addresses on the Company object and to display addresses on an Entity. To do this, cre-
ate a new field with an object type of Company and set the Open to Associations field to Yes. This cre-
ates two fields: a Company object field called Address and a Company::Address field on the Entity
object. If the generated reflected field name exceeds the maximum length of 100 characters, it is handled
as follows:
l Each field is allocated 50 characters, anything over that 50 character limit is truncated.
l The field's ArtifactID is appended to the field's name part.
l Additional space is truncated to allow room for the field's ArtifactID to become part of the new
name.
l The two field name parts are joined with "::", for example: "AAAAAAAAA BBBBBBBBB
CCCCCCCCC DDDDDDDDD EEEEEEE (1000012)::GGGGGGGGG HHHHHHHHH IIIIIIIII
JJJJJJJJJ KKKKKKK (1000013)".
l Propagation—forces a coding value to a specified group of related items. This value must be set to Yes before
you can propagate to a related item.
l Propagate To—click the Select button to access the propagation options. The available options depend on the
relational fields set for the workspace. Check the desired related items and click to move the selected items
to the right. Click Apply.
l Relational—you can make a fixed-length text field relational. A relational field is used to identify a group of
related documents, such as families, duplicates, or near duplicates. For example, MD5 Hash is commonly used
to identify duplicates. If set to Yes, identifies the field as relational. Once set to Yes, the Friendly Name, Import
Behavior, and Order fields become required in order to save the field.
Note: You can only set relational field properties on fixed-length text fields that don't exceed 450 characters.
l Relational Properties—click the Select button to access the following relational options:
l Friendly Name—a label for the relational field that users can easily understand. For example, you could
change the relational MD5 Hash field to Duplicates, since it is used to group copies of the same doc-
ument. This name displays in the Include Related Documents menu in workspaces and in the Related
Items pane.
l Import Behavior—controls how blank values are handled when importing through the Import/Export.
Depending on how your vendor processes these group identifiers, the relational field on the parent doc-
ument may be blank. Select an option to determine how blank fields are imported:
Note: When you append documents through Import/Export, with a relational field’s Import Beha-
vior set to Replace blank values with identifier, blank values are replaced on that relational
field even if it is not mapped to a load file field. The same action occurs when you import blank
values mapped to the relational value using an overlay.
l Pane Icon—select and upload an icon for display in the Related Items pane of the Review Interface.
Users can click on the icon to display a list of items grouped by this relational field. You can download the
Relativity-provided Relational Field Icons.zip, or you can upload a custom icon. Icons shouldn't exceed
16 x 16 pixels.
l Order—controls the pane icon order on the bottom of the Related Items pane. Use the following
guidelines:
l Icons with low order numbers appear to the left.
l Icons with the same order number are sorted alphanumerically.
l The order number can be any positive or negative integer. We recommend using groups of 10,
such as 10, 20, and 30, so you can easily insert a new icon without having to reorder existing ones.
You can use the View Order button to see how icons are currently ordered in the Related Items
pane. The Order Reference window displays the leftmost icon at the top of the list.
l Relational View—controls the view that appears in the Related Items pane. Shared values in this field
determine the documents the view displays. This field contains and icons you can use to edit the
selected view or create a new view.
Note: You cannot select a view that contains conditions or add/edit conditions to a view referenced by
a relational field. You also cannot make a relational view personal. This view will control the fields dis-
played and sort order.
l Relativity Applications—associates the field with a Relativity application. Click the Select button to select an
existing application. Check the desired applications and click to move the selected items to the right. Click
Apply.
This option is only available for those who have the Manage Relativity Applications permission.
l Source—the list of fields that you can use when mapping processing fields. Click the Select button to access
the available field sources, which contain the following options:
l Standard Fields—contains a collection of fields from both the Metadata Fields and Other Fields options.
l Metadata Fields—contains fields extracted from the actual file or file system.
l Other Fields—contains static, or system fields such as control number, processing set name, custodian,
and so forth.
Note: If Unicode data is loaded into a non-Unicode enabled field, then the data becomes unreadable.
Note: When using the new UI framework, Filter Type is not used except for the following scenarios: disabling
filtering on the field by selecting None, selecting List filters for Fixed Length fields, or selecting a custom pop-
up picker view for a multiple and single object fields.
Notes:
l Fields that contain a large number of items may also cause the List filter to take longer to pop-
ulate. We recommend you only select the List filter type for Single Choice and Yes/No fields. For
fields that may contain a large number of choices, you can designate a pop-up filter instead.
l Fixed Length Text fields—if the field contains more than 255 items, the List filter type you spe-
cify for the field will revert to the text box filter type and an error will be written to the Error Log
when you visit a Document list view containing the field.
l Single Choice / Single Object fields—if the field contains more than 255 items, the List filter
type you specify for the field will revert to None (disabled) and an error will be written to the Error
Log when you visit a Document list view containing the field.
l TextBox—displays a text box that a user can query for text. You can use search operators in the filter
box. See Filters in the Searching guide.
l Multi-list—displays a list for a user to select one or more fields to filter.
l Boolean—displays Boolean choices for the field. Users can select one option.
l CustomOnly (Advanced)—searches with multiple search terms and operators. When you use this filter
in a view, the operators that display are dependent upon the field type. The CustomOnly filter type is avail-
able for the following field types:
8.4.5 Choices
The Choices section contains the Choice editor, which you can use to add and edit choices for a single or multiple
choice field.
l Fixed-length text
l Long text
l Date
l Whole number
l Decimal
l Currency
l Yes/No
l Single choice
l Multiple choice
l User
l File
l Single object
l Multiple object
l The sum of all fixed-length text fields for any individual object should be no larger than 8,060 bytes. To see how
many of your 8,060 bytes remain, go to object you are checking. The control panel section displays remaining
bytes in the usage field.
l The technical limitation of a long text field is 2 GB. Relativity usually defaults to streaming only files smaller than
50 MB.
l Examples: Full text, Conversation ID, Email BCC, Email To, Source File, Title
8.5.3 Date
The date field type stores the date or date and time. Dates must be in a valid format. For example, 01/00/2000 is not
valid. Attempting to load an invalid date produces an error.
l Relativity accepts many formats, including SQL-accepted formats that match your SQL Server’s regional set-
tings. However, the date displays as mm/dd/yyyy for the US or dd/mm/yyyy for the UK. When entering a date
field, you can use the picker to choose from a calendar or enter a date directly in the field.
l Example: Email sent date, Date Created, Date Last Modified, Date Received, Date Sent.
Note: When you search on a user-created date field using a relative date, Last 7 Days for example, you may see
different results between a saved search and a search from the search panel if you are not in the same timezone as
your Relativity instance.
l This value cannot exceed 2,147,483,647. In other words, 2,147,483,648 and higher is invalid.
l Example: Page count, Number of Attachments.
8.5.5 Decimal
The decimal field type stores numeric values that may include decimals.
l With this field you can have a maximum of 15 digits before the decimal and two digits after the decimal.
l Example: Percentage, File Size.
8.5.6 Currency
The currency field type stores numeric values in a currency format. Ten digits is the maximum for this field.
l Your currency symbol is set based on Windows regional currency settings in the server hosting Relativity. The
formatting, such as decimal, commas, negative number sign, the position of currency symbol, are based on the
browser's language. When using RelativityOne, the settings of the regional server cannot be changed. They are
set to the US currency symbol.
l Example: Amount sold.
8.5.7 Yes/No
The Yes/No field type accepts one of two values. The default values are Yes and No.
Note:
l Use Single Choice fields rather than Yes/No fields when possible - creating Single Choice fields will not
impact reviews and may improve search performance. Before doing so however, check to confirm whether
your workflow can support Single Choice fields.
l If you are exporting a Yes/No field type with Import/Export or Integration Points, the values will display as
True/False in the exported files.
l You can choose multiple choices. You can also nest the choices in a hierarchy structure.
l Example: Issues, Deponent
Note: If Overlay Behavior is set to Replace Values on this field, a warning message appears stating that on import
that the current values for this field will be deleted and replaced with the values included in the load file. The Overlay
Behavior setting must be set to Merge Values in order to merge the values from the load file with the field's current
values.
8.5.10 User
The user field type contains users with rights to the current workspace. Depending on the function of the field,
Relativity filters the list of users to display only members of certain groups.
Note: A user field with a [removed] tag signifies that the user wasn't assigned to any of the workspace groups.
8.5.11 File
With the file field you can upload files for a non-document object. You can click on the Select button to choose a file to
upload or drag-and-drop the file onto this field to upload it. When you add a file field, Relativity automatically creates
file size, file icon, and text fields for the object. Once you upload a file, you can click on Pop Out icon to open the file in
the Viewer.
The text field contains the extracted text of all files uploaded to the file field. The Text Extraction Manager agent must
be running in the Relativity environment to populate the text field.
Note: If Overlay Behavior is set to Replace Values on this field, you will be prompted with a warning message on
import that the current values for this field will be deleted and replaced with the values included in the load file. The
Overlay Behavior setting must be set to Merge Values in order to merge the values from the load file with the field's
current values.
You add the Recipient Domains field on a Document object and associate it with a Domain object. By doing so:
l You used a multiple object field to create a many-to-many relationship, since you can have multiple domains,
and each recipient of an email message can have a different domain.
l Relativity automatically creates two fields when you define Multiple Object field type. The first Recipient
Domains field has a Document object type. The second Recipient Domains field represents the relationship
between the Recipient Domains object type and the Domain associative object type.
Note: The Assigned to field displays user information in the format "last name, first name." You must use
the user's email address when loading this field in Relativity. For example, you would load a user named John
Smith as johnsmith@example.com.
l Set fixed-length text fields to the minimum size needed and to no more than 400 characters.
l Store choice data in single or multiple choice fields if possible.
l Use separate objects to store repetitive content when possible.
l Set up fields as Unicode in advance because the system will have to re-index a field if you make the change fol-
lowing data load.
l Only include fields in the text index when it is truly necessary to do so.
When you code a document in a field on which propagation is enabled, the propagation function automatically codes
related documents with the same value. Click Save or Save & Next in the layout to apply the field propagation rules.
Note: Propagation works on all document object field types. Associative Object Lists do not work with propagation.
l AS000001 – AS000005
l TS000007 – TS000011
Within these families, two documents are duplicates:
l AS000003
l TS000009
Coding AS000003 as Responsive tags the family, and the duplicate, shown in blue.
Mass editing AS000002 and AS000003 as Responsive tags the family and the duplicate, shown in blue.
Mass editing AS000003 and TS000009 as Responsive tags all of the listed documents.
Note: Field categories that you create are carried over during workspace upgrades and when those cases are used
as templates. The All Fields field category will also carry over after an upgrade, though it is currently a system
default that cannot be configured by users.
Note: All Fields is a field category that is always present in Relativity but it does not display on the Field Cat-
egories tab since it cannot be edited.
Note: Ordering by 10's, starting with 10, then 20, then 30, etc. is recommended because you
can insert an item into any position later in the workspace, without the need to reorder all items.
4. Filter the field list as needed and check any desired fields.
5. Once the desired fields have been selected, click the Move selected left to right icon.
4. Click Unlink.
5. Click Unlink again in the pop-up.
The selected fields are no longer linked to the field category.
l
Show/Hide filters ( )—to display the field filters at the top of each column. This icon turns orange when you
activate a filter. Click the icon again to hide the filters. Your filter settings remain unchanged.
l
Clear all ( )—to remove the current filter settings. This option is only available after you set a filter.
The filter type determines the steps required to set the filtering criteria that it uses. See Filter types for details on filter
types and their use.
Note: When you create or edit a field, you can select its Filter Type. See Fields in the Admin guide.
After enabling filters, you are ready to enter criteria for the fields in your list.
Note: Before defining a new search filter, click the Clear All ( ) icon or the Clear All Conditions link in the
Search Conditions panel to remove any filter settings. For example, say you create a filter on the Privileged field, but
now want to search only by the Custodian field. If you do not clear the filter, Relativity filters your documents by both
the Privileged and Custodian fields, and your results may include fewer documents than you expect.
To use a filter:
1. If filtering is not enabled, do so by clicking the filter icon to display the filtering fields below the column head-
ings. The icon will change to orange.
2. Enter your filter criteria. The filter type determines how you enter the criteria and how to use operators to further
define the filter. See Filter types for details on filter types and their use.
You cannot edit the Search Conditions cards by clicking on them. However, you can clear all the conditions by clicking
the link at the bottom of the panel.
l Boolean—Yes/No fields.
l Numeric—decimal, whole number, and currency fields.
l List—single choice, single object, user, and fixed-length text fields.
l Date—date fields.
l Decimal
l Whole Number
l Currency
To use a numeric filter, click the drop-down menu and select an operator. Operators include:
l Equal to (=)
l Not equal to (!=)
l Greater than (>)
l Less than (<)
l Less than or equal to (<=)
l Greater than or equal to (>=)
Enter a numerical value in the filter text box. After you enter the value in the text box, press Enter to apply the filter. For
example, you might search for documents having a file size greater than 500000 bytes.
Here, you can adjust the operator and add conditions to further define the filter. Click Apply to set the conditions.
If there is a single filter choice you want to apply immediately, hover over the item's row and click Only when it appears
on the right side.
l (All)
l (Not Set)
l Is
l Is before
l Is before or on
l Is after
l Is after or on
l Between
For example, if you only want to view items sent before or on January 21, 2024 7 AM, do the following:
2. Use the calendar interface to select the date, January 21, 2024. You can enter the date directly into the text
boxes, or use the forward and back arrows to scroll through the calendar months.
Note: When you select the Between operator, two calendars display in the drop-down date filter, allowing you
to pick the starting and ending dates and times.
Note: Filtering on fields using the date and time format does not support using @Today. If you do not enter a
specific time, Relativity enters the default time of 12:00 AM.
4. Click Apply to set the conditions. Only items sent on or before 7 AM on January 21, 2024 appear in your doc-
ument list.
Click the Advanced ( ) link at the bottom of the calendar interface to launch the advanced filters screen. This
screen has more operators where you can add additional date and time conditions. Click Apply to set the conditions.
To find a specific list item in a large list, use the search box to enter a term. The list filters automatically as you type.
l Fixed-length Text
l Long Text
l Date
l Whole Number
l Decimal
l Currency
l Object
You can use text box filters to search on specific terms, numbers, and dates. Enter one or more terms in the filter text
box. Connect multiple terms using the following operators:
l AND
l OR
l IS SET
l IS NOT SET
l BETWEEN
l Is
l Is not
l Is set
l Is not set
l Is less than
l Is greater than
l Is like
l Is not like
l Contains
l Does not contain
To use advanced text box filtering:
1. Click inside the filter text box for a column. The Advanced link appears.
2. Click the Advanced link.
3. Choose an operator (such as is greater than.) See Fixed-length, long, or extracted text operators in the Search-
ing guide for a list of definitions of the available operators.
4. Enter a value into the query text box(such as 100.) The filter returns items where the value of the field is greater
than 100.
5. (Optional) Click Add condition to add a new filter condition. For example, you may want to also return items
where the text field contains the word privilege.
1. Click the Save Search button located at the bottom of the screen.
2. Select or enter the following required information:
l Name—enter a title for the search. The title appears in the saved searches browser.
l Owner—select Public to make the search available to all users or choose a specific user from the list.
Click Me to select your name from the list, making the search private. (You must have the appropriate
privileges to view searches.) See Controlling the visibility of saved searches in the Searching guide.
l Search Folder—click the Selectbutton to launch a pop-up window where you can save the new search
to a specific folder on the saved searches browser. Highlight the folder where you want to save the
search, and click OK to select it.
3. Add to or change the search criteria as needed. See Create and edit a saved search.
4. Click Save.
l Everyone - All users are members of the Everyone group. System admins can manage the permissions all
users have on system level views and scripts. You are unable to revoke certain permissions for the Everyone
group.
l System Administrators - Relativity system admins have rights to see every item in a Relativity environment.
System admins have full access to all admin tabs. System admins can then create and edit new clients, mat-
ters, users, groups and views, among other capabilities. System admins also have the following script and
applications-related permissions: view, run, preview, create/write, edit (unlocked scripts only), link, and import
applications.
Note: Relativity Lockbox is enabled for all RelativityOne customers. When the Relativity Lockbox feature is
enabled, Relativity system admins must also belong to a group within a workspace in addition to the System Admin-
istrators group to access and administer security within that workspace. Refer to Support if you need more inform-
ation on this feature.
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
Edit Edit
View Run Preview Write Link
(locked scripts) (unlocked scripts)
System Admin √ √ √ √ √ √
Standard User √ √ √
1. Click your name in the upper right corner of Relativity, and then click Home.
2. Click the Groups tab.
Note: If your groups list doesn't show Edit links, edit the All Groups view to display the Edit link.
4. Add or edit the fields on the group details page. See Fields for details.
5. Click Save to save the group information.
The group details page displays a list of users added to the group as well as group-accessible workspaces. For more
information, see Managing security in the Admin guide.
11.3 Fields
The groups object contains the following fields:
Group Information
l Name - the group’s name, which is a required field for creating a group.
Note: As your Relativity environment grows, arbitrary group names like "Group 1" can produce a confusing
administrative workflow. Name each group according to their purpose and permission level, such as "ACME
Co. Reviewer" and "ABC Corp. Administrators."
l Client - a required field that makes the group a child object of the chosen client.
l Group Type - an uneditable field that displays one of the following categories:
l System Admin
l System Group
l Personal
l Everyone
l Workspace Admin
l Keywords - an optional field where extra group information may be recorded.
l Notes - an optional field where extra group information may be recorded.
Note: A job is executed when you add users to a group or when you remove them from one.
1. Click your name in the upper right corner of Relativity, and click Home.
2. Click the User and Group Management tab. You can complete the following steps from either the Users or
Groups tabs:
l From the Users tab, click the name of a user and scroll down to the Groups section on the form.
l From the Groups tab, click the name of a group and scroll down to the Users section on the form.
3. To add a user to the group, click Add in the Users or Groups section depending on the tab.
Note: Relativity sends an email message notifying you when the job is completed. If an error occurs, the
email message contains a link that you can use to retry the job. You must be logged into Relativity before you
click the retry link. The Errors tab also displays the retry link.
Note: In 2025, Relativity is deprecating the (Admin) Errors tab in RelativityOne. This change is part of our effort to
transform the error-handling experience by making it easier to address job-specific errors as they occur at their
source within your workspaces. Starting in April 2025, we'll hide the Errors tab from all production instances in a
phased rollout. In July 2025, we'll permanently remove it from RelativityOne and disable the ability to read errors
through the API. For more details, see Errors tab deprecation.
6. To remove a user from a group, click Remove. Click OK on the confirmation message, and then click Close.
Note: You can preview the security of a group to determine whether or not the appropriate permissions are
granted to that group over particular workspaces. For more information about previewing group security see
Preview security.
3. Create a new client to associate the external group to and click Save.
Note: The 'client number' field can either be the 'client name' value again, or a unique identifier.
5. Enter a Group name to associate the external users to and connect it to the newly created client.
6. Add any users to this group who will need access to the workspace.
7. Next, navigate to the workspace you want to give them access to and click on Workspace Details on the right
side of the screen.
8. Select Add/Remove Groups and filter to the newly created group. Select Add, then Save.
9. Click on the newly created group and select the Copy option. After copying permissions, you can select the Pre-
view option to confirm what level of access they will have within the workspace.
10. Select the template group from which you want to assign permissions.
Note: Choices can vary depending on the workspace's template. Reviewer groups usually start with a Level
1, which grants the least permissions. More permissions are offered as the level increases. In contrast,
Admin Groups often have most or all permissions within a workspace. If you are unsure, it is recommended to
select the group with the lowest level of permissions. You can always copy a group with higher permissions
later if you need to grant more capabilities.
Note: Moving a group into a client domains may cause the group to lose previously configured permissions.
Note: When you run imaging on a specific saved search used in an imaging set, documents that don’t have the
"Add Image" permission will be skipped.
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
Note: Imaging profiles are to be used solely on the needs of your case, such as on document type or on the format
needed for production. Imaging profiles don’t correspond directly to Relativity user types, in which case there is no
single imaging profile type that is better suited for a case/project manager, reviewer, or lit support specialist than any
other.
l Basic Imaging Engine Options—provides a select number of simple settings for creating the profile.
l Native Imaging Engine Options—provides an expanded range of settings for creating a profile with Relativ-
ity’s worker manager server.
Note: When you create a new profile from scratch, no default values exist for any profile fields. If you'd like to create
a new profile with default values already in place, you can copy the Default profile provided by Relativity, give it a
unique name, and use it as a base for an imaging job.
Note: Relativity propagates native file types to imaging profiles only when the profile is created.
Note: * indicates fields that are set automatically with default settings. You can change these settings as needed.
l Imaging Method—sets the type of imaging for the profile. The imaging engine options appear for the selected
imaging method.
l Basic—uses a select number of user-specific settings to image documents using Oracle.
l Native—uses an expanded range of user-specific settings to image documents using the worker man-
ager server.
l TIFF—renders the image as a black and white TIFF file. This is recommended; this is the value in the
Default profile.
l Basic Image Size*—sets the image size for all images rendered with the basic imaging engine profile, the
default for this field is set to Original setting. The options are:
l Original setting—renders the image with the original document settings.
l Letter (8.5 in x 11 in)—renders the image in standard letter size.
l A4 (8.27 in x 11.69 in)—renders the image in A4 size.
l Legal (8.5 in x 14 in)—renders the image in legal paper size.
l Custom—sizes the image by using either or both values in the Maximum Image Width and Maximum
Image Height fields. When you enter a value in either or both of these fields, Relativity converts the doc-
ument to an image size that fits within these parameters, while maintaining the aspect ratio. If both of
these fields are empty, Relativity displays an error message indicating that you must enter a value in one
of them.
l Maximum Image Height (Inches) and Maximum Image Width (Inches) specify the largest allowable size for
the generation of custom images. Relativity converts the document to an image size that fits within these para-
meters, while maintaining the aspect ratio. Only the Custom option references these fields, requiring you to
enter a value in at least one of them.
RSMF Options
l Native Image Format*—sets the image format for files sent to the native imaging engine for the profile, the
default for this field is set to TIFF. The options are:
l JPEG—renders the image as a color JPEG file. Selecting this can possibly decrease imaging per-
formance because JPEGs have larger file sizes than TIFFs and therefore require more disk space.
l TIFF—renders the image as a black and white TIFF file. This is recommended and is the value in the
Default profile.
l Automatically detect and render color pages to JPEG*—(Overrides ‘Native Image Format’ selection of
TIFF) auto-detects and images color pages as JPEG files even if you selected TIFF as the Native Image
Format. If you select Yes, Relativity overrides the TIFF Native Image Format for color pages only. If you select
No, color pages remain as TIFFs. The default for this field is set to No.
l Maximum pages imaged per file—a native global setting for all document types that sets the maximum num-
ber of document pages that are imaged. For example, if you set this value to 50 and have a 100-page doc-
ument, Relativity only images the first 50 pages of the document. Use this option to image only the number of
pages entered in this box.
l Dithering Algorithm*—the procedure the native imaging engine uses to convert images from color to black
and white TIFFs. This setting is only used if Native Image Format is set to TIFF, the default for this field is set to
Floyd Steinberg. The algorithm options are:
l Clustered 6x6—groups pixels into clusters of 6x6.
l Clustered 8x8—groups pixels into clusters of 8x8.
l Clustered 16x16—groups pixels into clusters of 16x16.
l Dispersed 4x4—disperses pixels in a 4x4 matrix.
l Dispersed 8x8—disperses pixels in an 8x8 matrix.
l Dispersed 16x16—dispersed pixels in a 16x16 matrix.
l Floyd & Steinberg—diffuses the difference between the actual analog value and quantized digital value
of a pixel to its neighboring pixels.
l Threshold—compares each pixel value against a fixed threshold. During this process, individual pixels
in an image are marked as object pixels if their value is greater than the threshold value. If their value is
less, they're marked as background pixels. If you select this, you must provide a value between 0-255 in
the Dithering Threshold field.
l Dithering Threshold—sets the threshold against which all pixels are compared. This is required if you chose
Threshold for the Dithering Algorithm field above. You can provide any value between 0 - 255. The recom-
mended default threshold is 128. When the pixel RGB color model in an image is greater than the threshold, it's
converted to black. When less, it's converted to white.
Notes:
l For Native Image Time Zone to apply, you must select Date Sent for the Native Image Date field. If you
don't make a selection, Native Image Time Zone will not apply and defaults to the current date.
l Native Image Time Zone field only supports MSG and EML files for email.
To set the time zone value on documents in Relativity, click the drop down next to the Native Image Time Zone
field and then select a time zone field from the picker. If you don't select an option here, the time zone defaults
to Coordinated Universal Time (UTC).
To add an option to the Native Image Time Zone picker list:
1. From the Fields tab, click New Field.
2. Set these fields:
l Name—type the name of the Native Image Time Zone option that you are creating.
l Object Type—select Document.
l Field Type—select Single Object.
l Associative Object Type—select Relativity Time Zone.
3. Click Save.
l Native Image Date - select any document-level date field available in the pop-up picker as the current date
used when rendering date-related document field codes. If no selection is made here, the Native Image Date
defaults to the current date (today’s date). Microsoft Visio documents are incompatible with Native Image Date.
If this field is set set for an imaging profile with linked time and date Application Field Codes, the linked Applic-
ation Field Codes override the Native Image Date setting on the profile.
Spreadsheet Options (Native)
l Paper size/orientation*—specify a paper size and orientation for your spreadsheet, the default for this field is
set to Original setting. The options are:
l Original setting
l Letter (8.5 in x 11 in)
l Letter (11 in x 8.5 in)
l Page Order*—determines the order used to render spreadsheets when data exceeds one page, the default for
this field is set to Original setting. Options include:
l Original setting—renders a spreadsheet based on the spreadsheet's original page setting.
l Down, then over—renders a spreadsheet first from the top of the page to the bottom and then from the
left to the right.
l Over, then down—renders a spreadsheet first from the left of the page to the right and then from the top
to the bottom.
l Print Area*—override any pre-defined print area in an Excel file. When you select Ignore Print Area, Relativity
images the entire document, the default for this field is set to Ignore print area. The options are:
l Original setting—uses the original print area settings of the document.
l Ignore print area—ignores the original print area settings of the document.
l Hide and page break after _ consecutive blank rows and columns*—sets a maximum value for con-
secutive blank rows or columns. By default, the native imaging engine checks for a run of 10 blank rows or
columns and compresses them to limit the number of pages rendered for a spreadsheet. The default for this
field is set to 10.
l Show track changes in spreadsheet*—displays any modifications made to the document through the Track
Changes option in Excel, the default for this field is set to Yes. The options are:
l Yes—shows track changes.
l No—doesn't show track changes.
l Include row and column headings*—renders row and column headings (the number assigned to rows and
the letters assigned to columns). The options are:
l Original setting - uses the original row and column headings of the document.
l Yes - renders the row and column headings.
l No - doesn't render row and column headings.
l Include comments*—determines whether Relativity renders comments found in the spreadsheet, the default
for this field is set to Yes. The options are:
l Yes—renders comment found in the spreadsheet. This is the value used in the Default profile.
l No—doesn't render comments found in the spreadsheet.
l Include headers and footers*—renders headers and footers in the spreadsheet. The printing of these items
interferes with the ability of the native imaging engine to detect blank pages – for this reason, it's recommended
that you leave this set to No, the default for this field is set to Yes. The options are:
l Original setting—uses the original header and footer settings of the document.
l Yes—renders the headers and footers of the document.
l No—doesn't render the headers or footers of the document.
l Include gridlines*—renders the gridlines between rows and columns in the spreadsheet, the default for this
field is set to Yes. The options are:
l Clear formatting in empty columns—clears the formatting from entire columns that do not have con-
tent in any of their cells and whose adjacent columns are both empty. This option does not remove the
formatting from an empty cell that is a part of a column that has cells with content. With this option, the
l Text Visibility—determines the visibility of the text in a spreadsheet through the following options:
l Remove background fill colors—removes background color and ensures that any hidden text or rows
formatted to match the background color appear.
l Set text color to black—displays the font color of text as black and ensures that any hidden text
appears, such as text with a white font on a white background.
Note: If an Excel spreadsheet contains comments, those comments appear on a separate page after Relativity
renders the spreadsheet. Also, native imaging clears any filters set in a spreadsheet.
Note: Imaging email settings do not affect emails with a native file type of MHT within Processing application.
l Hidden text—renders any comments or directions added to the text of a document through the Hidden
text feature in Microsoft Word. Selecting this makes the hidden text specified in the Microsoft Word file
visible in the same manner as the normally-entered text.
Microsoft Word Options (Basic)
l Show Comments—renders any comments added to the document through the Review feature in Word.
l Show track changes—renders any markups added to the document through the Track Changes feature in
Word, the default for this field is set to No. The options are:
l Valid numerical values—numerical values fit within a designated range based on individual numerical field
requirements
l Configuration specific to format type—option selections and requirements vary based on the Native Image
Format selection
l Field dependencies—specific fields require additional field configurations to satisfy groups of settings avail-
able for native imaging, and specific fields are ignored based on the configuration of a related field
Native File Imaging profile validation only runs when using the default Native Imaging Profile Layout for new
imaging profiles.
Note: With validation rules you can only configure Zoom Level % or the set of Fit to ___ pages fields. Don't set
values for all three fields.
Note: You can't add new native file types to Relativity. For a list of native types that Relativity supports, see the
Native Types tab or Viewer-supported file types on page 692. Contact Support if you have additional questions
about supported native types.
l Unlink—removes restricted native types from the list. When you use this profile, Relativity images these doc-
uments.
Select one or more file types, and click Unlink.
l
Resize, export, filter— —resize columns, export, and filter the list of restricted native types.
These features function similarly to those available on views.
l
Export the list —creates a list of restricted native types in Excel.
Note: Application Field Codes are only configurable with native imaging.
For more information on Application Field Codes and how to link them to native imaging profiles, see Application Field
Codes.
Note: In 2025, Relativity is deprecating the (Admin) Errors tab in RelativityOne. This change is part of our effort to
transform the error-handling experience by making it easier to address job-specific errors as they occur at their
source within your workspaces. Starting in April 2025, we'll hide the Errors tab from all production instances in a
phased rollout. In July 2025, we'll permanently remove it from RelativityOne and disable the ability to read errors
through the API. For more details, see Errors tab deprecation.
1. Navigate to the Imaging tab, and then click Imaging Sets in a workspace.
2. Click New Imaging Set.
The Imaging Set Form appears.
1The 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.
12.6.3 Fields
The imaging set form contains the following fields:
l Start Time - this field will appear with the following conditions are met:
l The imaging set is in the Submitting status.
l The imaging set is in the Imaging status and the job has commenced.
l Status - the current state of the imaging job. This value depends on issues encountered during the job and will
automatically refresh to show progress. The possible values for this field are:
l Staging - you've started the job, but no documents from the imaging set have been sent to the worker
manager server yet.
l Preparing files - Relativity is preparing files to be submitted by splitting them into batches, creating data
tables and getting the files ready for the imaging job. A percentage tracker reflects the progress of this
status.
l Upload Image
l Add Image
l Delete Image
Note: You need to install the Imaging Request and Imaging Response agents in order to perform image on the fly,
run an imaging set, or execute a mass imaging operation. The maximum recommend amount of Imaging Response
agents is 8, any more can cause database issues. The standard configuration is 4, for details on installation and
activation of these agents, see Imaging.
If an image already exists for a document, you can replace it by clicking the document name and selecting Replace
images fore this document. In the menu, select the imaging profile you want to upload the new image with.
Replacing the image with a supported image type replaces the entire image not just a single page of an image. For
example, if you have a 5 page document, but you upload a JPG or TIFF file, you will have 1 image. If you upload a 5
page PDF file, then 5 images will upload.
Once you select the file in the folder, Relativity automatically begins to upload it. When the upload is successful, the
image is visible in the viewer.
If you've redacted or added highlights to an image in the viewer and then you attempt to upload a new image, you'll
receive a message informing you that you're about to remove those redactions or highlights when you replace the
image. Note that replacing an image with redactions will update the Has Redactions field for that file to No and
remove all existing redactions and markup.
If you attempt to upload an unsupported file type, you'll receive an error message.
From here, you can click Upload New Image to select a new image to upload.
l Images - Created - indicates that the logged in user generated an image in the viewer.
l Images - Deleted - indicates that the logged-in user deleted an image from the viewer.
Note: Application Field Codes are only configurable with native imaging.
Show Field Code Show Nothing Document Default Replace with Relativity Field
Microsoft Word
Date ✓* ✓ ✓ ✓
FileName ✓ ✓ ✓* ✓
NumPages ✓ ✓ ✓* ✓
Pages ✓ ✓ ✓* ✓
Time ✓* ✓ ✓ ✓
Microsoft Excel
Date ✓* ✓ ✓ ✓
File ✓* ✓ ✓ ✓
Page ✓ ✓ ✓* ✓
Show Field Code Show Nothing Document Default Replace with Relativity Field
Pages ✓ ✓ ✓* ✓
Path ✓* ✓ ✓ ✓
Time ✓* ✓ ✓ ✓
Microsoft Powerpoint
DateTime ✓* ✓ ✓ ✓
Footer ✓ ✓ ✓* ✓
Slide Number ✓ ✓ ✓* ✓
Microsoft Visio
Directory ✓* ✓ ✓ ✓
FileName ✓* ✓ ✓ ✓
Now ✓ ✓ ✓* ✓
Note: For PowerPoint, Relativity only supports field codes for headers and footers. Field codes for speaker notes
and text boxes are not supported.
If you need to add field codes beyond the 17 that come pre-loaded, Relativity provides additional field codes you can
select via a pop-up picker or enter manually. Those field codes are:
Show Field Show Noth- Document Replace with Relativ- Popup Manual
Code ing Default ity Field Picker Entry
Microsoft Word
Author ✓ ✓ ✓ ✓ ✓ ✓
Citation ✓ ✓ ✓
CreateDate ✓ ✓ ✓ ✓ ✓ ✓
Embed ✓ ✓
Link ✓ ✓
PrintDate ✓ ✓ ✓ ✓ ✓ ✓
SaveDate ✓ ✓ ✓ ✓ ✓ ✓
Microsoft Excel
Picture ✓ ✓ ✓ ✓ ✓ ✓
Tab ✓ ✓ ✓ ✓ ✓ ✓
Microsoft Visio
DocCreation ✓ ✓ ✓ ✓ ✓ ✓
Show Field Show Noth- Document Replace with Relativ- Popup Manual
Code ing Default ity Field Picker Entry
DocLastEdit ✓ ✓ ✓ ✓ ✓ ✓
DocLastPrint ✓ ✓ ✓ ✓ ✓ ✓
PageCount ✓ ✓ ✓ ✓ ✓ ✓
PageNumber ✓ ✓ ✓ ✓ ✓ ✓
Please note that Relativity currently does not support the following Microsoft Word field codes:
l AutoNum
l AutoNumLgl Time
l AutoNumOut
l Custom
l GoToButton
l IncludePicture
l MacroButton
l PageRef
l Seq
Note: When creating Application Field Code RDOs, when the option is Relativity Field, you cannot use the following
system fields: System Modified By, System Created By, or Folder Name.
12.8.4 Fields
The Application Field Code Information fields are:
l
Field Code - The field code that appears on your document set. Click to see a full list of available field
codes. See Application Field Codes on page 208 for details.
Note: You can add a field code to your imaging profile even if the field code isn't a part of the default or avail-
able lists. See Application Field Code formats on the previous page for details.
l Application - The application used to create the documents. This field automatically populates once a field
code is selected.
l Option - The way field codes render on the imaged document set.
l Select from the following options:
l Show Field Code - This option displays the field code in the imaged document.
l Show Nothing - This option hides the selected field code in the imaged document.
l Document Default - This option applies the default setting of the document to the field code in the
imaged document.
l Replace with Relativity Field - This option replaces the selected field code text with a Relativity
date, fixed-length, or whole number field value that you choose in the imaged document.
l Relativity Field - The Relativity field value to replace the selected field code text. This option is required when
Replace with Relativity Field is selected.
Once you create your Application Field Code, link the field code to the appropriate native imaging profile. This is only
required if you create a new Application Field Code that isn't linked to a native imaging profile by default. The Imaging
Profile (Field Codes) section lists the available native imaging profiles in a workspace.
To link an Application Field Code to an existing native imaging profile:
1. Click Link. The Select Items - Imaging Profile (Field Codes) popup picker opens.
2. Select the imaging profile where you want to link the Application Field Code.
3. Click Add.
4. Click Set.
Depending on the progress of the job, the following options are available on the console:
Note: Retry Errors will use the same imaging profile the documents with imaging errors were created with,
even if the imaging profile is changed.
l View Document Errors - redirects you to the Imaging Document Error tab, where the results are filtered by all
imaging errors associated with the documents in the imaging set. You can expand the results by modifying the
filters.
l View Document Warnings - redirects you to the Imaging Warnings tab, where the results are filtered by all
Imaging Warnings associated with the documents in the imaging set. You can expand the results by modifying
the filters.
l Show Errors - provides the option to view document-level errors for an imaging set run prior to September
2018. When you click this button, a pop-up displays a filterable list of documents and fields. The fields include:
l Control Number - the control number of the item in error.
l Artifact ID - the artifact ID of the item in error.
l File Type Identification (Native) - the file type of the item in error as identified by the native imaging
engine. This is only populated if the native imaging engine runs the imaging set.
l File Type Identification (Basic) - the file type of the item in error as identified by the basic imaging
engine. This value is populated when the basic engine identified the document when you import the doc-
ument into Relativity.
l Imaging Method - the method selected in the Native Types table for the identified file type in error –
Basic or Native.
Note: When you mass image, image on the fly, run an imaging set, and retry an imaging set, the list of passwords
specified in the password bank accompanies the imaging job so that password-protected files are imaged in that
job. For more information see Password Bank in the Processing User Guide.
l In the case of fatal errors, the imaging profile information remains cached until you delete the set or you delete
the job record associated with that set from the ProcessingQueue table.
l In the case of non-fatal errors, Relativity no longer caches all profile information except for the Time Zone and
Last Modified Date information.
Notes:
l The Password Bank tab appears under both the Imaging and the Processing applications and is updated in
each to reflect the most current entries are added, deleted, or edited.
l Save as PDF does not integrate with the Password bank. If you select Save as PDF when imaging a native
document that is password protected, an error occurs.
For more information see Password Bank in the Processing User Guide.
Status
What Happened What It Means
Value
Staging User clicked Image Docu- Job is in queue table and the Imaging Set is awaiting execution.
ments.
Preparing The Imaging Request Agent is Relativity is preparing files to be submitted by splitting them into
files preparing files to be submitted. batches, creating data tables and getting the files ready for the ima-
ging job. A percentage tracker reflects the progress of this status.
Submitting The Imaging Request Agent is The Imaging Request is creating the imaging job and doing neces-
submitting documents to the sary work to submit documents.
Processing and Imaging Documents are being submitted to the queue and getting ready to be
Queue. picked up for imaging. A percentage tracker reflects the progress of
this status.
Imaging All documents have been sub- Invariant workers are creating images of the documents.
mitted to Processing and Ima- The job is currently being performed in the worker manager server. A
ging Queue. percentage tracker reflects the progress of this status.
Completed Job has completed. All documents imaged successfully.
Completed Job has completed with ima- One or more documents encountered an error during imaging job.
with errors ging errors.
Error - Job Job manager encountered an Manager terminated imaging job due to exception.
Failed exception.
Stopping User clicked Stop. Processing and Imaging Queue is stopping worker jobs, and Docu-
l During the conversion process, Relativity skips documents that already have images, documents with restricted
native types, and documents with images in a pending state (that's with the Has Images field set to Yes). It
includes these items in the skipped documents count.
l If you need to delete an Imaging Set, you should only delete those with the following statuses:
l Stopped by User
l Error - Job Failed
l Completed with Errors
l Completed
To learn more about an imaging error, click the Name field for a document on the Imaging Document Error tab. The
Imaging Document Error Layout will open. Layout fields include:
You can also navigate to the Imaging Document Error Layout from the
4. Click on the Name field for a document to obtain more information about the error. The Imaging Document Error
Layout will open.
3. Select the view you just created from the View bar.
4. In the Document list, click on the Originating Imaging Document Error link for a document. The Imaging
Document Error layout will open.
1. You create a password bank that includes a list of passwords that correspond with the files you intend to image.
2. You create an imaging set with the data source that contains the encrypted documents.
3. You start imaging the documents in the imaging set by clicking Image Documents in the Imaging Set console.
4. All passwords you supplied to the password bank become synced via an agent and accompany the job as it
goes to the imaging engine.
5. The imaging engine images the files in the imaging set and refers to the passwords provided in the password
bank. It then sends the imaged files back to Relativity.
6. Once the imaging status changes to Completed, you review and release images from QC review.
7. The imaged documents become available for review in the workspace, along with all the other previously-
encrypted documents whose passwords you provided.
Note: The Password Bank works with both Native and Basic imaging.
1. Click View Document Errors in the Imaging Set console after you run an imaging set.
2. Outside of Relativity, locate the passwords designated to unlock those files.
Note: 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.
To view a list of documents that have Imaging Warnings, go to the Imaging Warnings tab. You can also add Imaging
Warning fields to a Core Reviewer layout or Document view.
l If you delete an image, the Imaging Warnings associated with the deleted image will still exist.
l If you delete a document that has associated Imaging Warnings, the warnings will no longer be visible and can-
not be searched for later.
l Relativity will not perform the warning detection process on images uploaded using the image replacement fea-
ture in the Document viewer.
l Relativity will not perform the warning detection process on images longer than 25 pages. Documents longer
than 25 pages will be marked as Cut-off Detection Not Performed in the Warning Type field.
Historic imaging warning information is not preserved. If a document with an Imaging Warning is re-imaged, the
previous Imaging Warning is deleted.
l Relativity Document Identifier - the control number of the document imaged along with a link to that doc-
ument in the Viewer.
l Imaging Warning - a description of the problem detected. Description options are:
l Possible cut-off embedded image detected.
l Possible cut-off text detected.
l Cut-off detection not performed.
l Split performed on table larger than page width.
l Possible missing or invalid Rich Text Format content detected in the email body.
l Possible invalid character coding detected.
For more information, see All imaging warnings on the next page.
l Warning Type - a predefined list of options that facilitates searching when trying to group warnings. This field
has better searching performance than a text-based field, such as Imaging Warning. Warning Types include:
l Cut-Off Text.
l Cut-Off Embedded Image.
l Cut-Off Detection Not Performed.
l Table Split.
l Missing or Invalid Rich Text Format Content.
l Character Encoding Mismatch.
l Warning Details - additional information related to the problem found, such as the page range where problems
are detected.
l Imaging Method - Basic or Native.
Note: Except for the Notes field, you cannot modify the Imaging Warning fields, and you cannot link or unlink
Imaging Warnings to documents.
Note: You can only create the Warning Type pivot in the Imaging Warnings tab. The Warning Type field is not
available for widgets on the Documents tab.
Imaging
Warning Why the warning occurred Next step
Type
Character Text in this document could be encoded in a way that may produce invalid Create a saved search
Encoding or unreadable characters when imaged. Specifically, email metadata with this warning type as a
Mismatch indicates that the message body is encoded in <format>, but part of the search condition and
body text was also encoded in <another format>. Example formats manually QC the returned
include: documents.
l utf-8
l Windows-1252
l us-ascii
Cut-Off Email that is greater than 25 pages cannot have cut-off detection per- Create a saved search
Detection formed on it. with this warning type as a
Not Per- search condition and manu-
formed ally QC the returned doc-
uments.
Cut-Off Embedded images within a table go beyond the boundaries of the page. Use different imaging pro-
Embedded file options, such as land-
Image scape, auto-fit tables, split
tables and auto-fit images.
Cut-Off Text Text within a table goes beyond the boundaries of the page. Use different imaging pro-
file options, such as land-
scape, auto-fit tables, and
split tables.
Missing or Rich Text Data within the email is possibly missing or incorrect. As a Create a saved search
Invalid Rich result, text in the email body may be missing from the image generated. with this warning type as a
Text Format search condition and manu-
Content. ally QC the returned files.
Table Split Tables that go beyond the boundaries of the page have been split and re- Create a saved search
printed on a new line. with this warning type as a
search condition and
manually QC the returned
files.
Table Split Tables that are beyond boundaries of the page could not be split. Use different Imaging
Not Com- Reasons for this include an abnormally wide first column, when there are Profile options, such as
pleted rows that span across multiple columns, or a table within a table. The landscape, auto-fit tables,
and split tables.
exact page where the table begins will be reported.
This screen shot shows an imaged email where the Split tables to fit page width field was set to Yes on the imaging
profile.
Selecting the Split tables to fit page width field will slow down your imaging time. As a result, you may want to image
documents without the field set to Yes first and then re-image all of the documents that acquire an Imaging Warning.
To re-image documents that have an imaging warning:
1. Create a saved search that brings back documents with Imaging Warnings.
l Select Imaging Warning from the Add Condition drop-down menu. A pop-up window will open.
l Select these conditions from the Operator.
l Click Apply.
For more information, see the Admin Guide.
2. Delete the images in documents that have Imaging Warnings.
l Filter on the saved search you just created.
l Select Delete from Mass Operations.
l Select Delete only images from selected documents.
l Click Delete.
3. Create a Native Imaging Profile, and in the Email Options tab, set the Split tables to fit page width field to Yes.
For more information, see the Admin Guide.
12.13 QC Review
Using QC Review you can 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.
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.
Note: QC Review of Imaging Sets that contain large volumes of documents can be optimized with Random
Sampling. See Sampling on page 540
5. Click OK.
Note: The ImageQCOnByDefault instance setting value makes this checkbox default to checked. See the
Instance setting guide.
All images in that Imaging Set are only viewable by users whose groups have the permission to View Images Hidden
for QC Review. Apply this permission to any group from the Workspace Details tab.
4. Click OK.
If the documents in the Imaging Set you want held for QC Review already have images:
l Image QC Status - this choice field defines whether or not the image for the document is Hidden for QC. The
value is null if it is not hidden.
l Imaging Set - this field displays the most recent Imaging Set associated with that document. If the document's
image originates from outside of Relativity or with Image on the fly functionality, this field is null.
To cancel imaging jobs, select one or more jobs, and click Cancel Imaging Job. You can only cancel jobs that are in
a Status of 'Imaging.' Requests to cancel during 'Submitting' will be ignored.
Note: To change the priority of a job where Customer lockbox is enabled, you must be in a permission group
having access to the workspace where the job originated, along with the System Administrator's group. For more
information, see Customer lockbox.
l Clustered 6x6
l Clustered 8x8
l Clustered 16x16
l Dispersed 4x4
l Dispersed 8x8
l Dispersed 16x16
l Floyd & Steinberg
l Threshold
Clustered 8x8 25 KB
Clustered 16x16 23 KB
Dispersed 4x4 24 KB
Dispersed 8x8 24 KB
Dispersed 16x16 24 KB
Threshold 127 22 KB
Threshold 215 22 KB
Threshold 255 22 KB
4. Click Save.
12.16.2 Generating a complete list of native types and their respective imaging
engines
Use the following steps to generate a .CSV file that lists all native types and their imaging methods, categories,
restriction status, and native download prevention status:
Note: Microsoft
Project 2016 is
not supported
OneNote ONE √ √
OpenOffice ODC, ODS, ODT, ODP, XPS √ √
Note:
Supported file types differ slightly in processing, imaging, and the viewer. See Supported file types for imaging and
Viewer-supported file types for details specific to those features.
13.1 Security
In the Security section, you can manage group permissions and generate a group permissions report.
1. Click Edit in the Message of the Day section. The button is in the upper right corner of the section.
3. Select the Will Display checkbox to activate the message for users when they log into Relativity.
4. Select the Allow Users to Dismiss checkbox to allow users to hide the message.
l If you enable this setting, users will see a checkbox in the message stating Do not show me this mes-
sage next time. Users will not see the message again, including when they log back in to Relativity,
unless it is changed to a new one.
l If you disable this setting, users will see the message after 8 hours of inactivity.
5. Click Save.
Within the legend, you can sort, filter, Export to Excel, and print. You can print by right-clicking and choosing the
browser's print option.
The Keyboard Shortcuts Legend includes the following sortable columns:
l Keyboard Shortcut - the key combination used to execute the shortcut during document review.
l Action - the action that results from using the keyboard shortcut.
l Viewer Mode - the type of Viewer for which each shortcut is available. You can use most of the system cat-
egory shortcuts in all viewer modes.
l Category - the shortcut type. Below, the legend displays only those shortcuts designated by the System and
the browser. This column also lists all field and choice shortcuts that your system admin configured via field and
choice properties.
l For Mac users, keyboard shortcuts marked with Ctrl map over to the Command key.
l Keyboard shortcuts are active when:
l Keyboard shortcuts are enabled.
l Focus is in the Review Interface.
l The Viewer is either docked or undocked while the browser only has one tab open.
l If the shortcut overlaps with a Windows shortcut, both shortcuts are triggered. For example, if a program
installed on a user’s computer uses the Ctrl + Alt + R shortcut, clicking Ctrl + Alt + R triggers that action
regardless of whether a user is in any of Relativity's supported browsers.
l Keyboard shortcuts aren't triggered when:
l Keyboard shortcuts are disabled.
l Focus is not in the Review Interface.
l The Viewer is undocked or in standalone mode, and the browser has more than one tab open.
l When the numbers 0-9 are used as shortcuts, they only fire when you press these digits in the main section of
the keyboard. The shortcut doesn't fire if you press those digits found in the keypad.
Note: You can also edit an existing Document field in this manner. See Fields on page 147.
2. Click the Edit icon in the row of the choice you would like to edit.
3. Click the Select button next to the Keyboard Shortcut field.
4. Select the desired key for the Modifier Key(s) field.
5. Choose the desired key from the Main Key drop-down menu.
6. Click Apply.
If this shortcut is valid, you receive a message saying <Valid Keyboard Shortcut>
7. Click Save.
8. Navigate to the Documents tab and open a document.
9. Click on the Viewer Settings menu in the upper-right and select the Keyboard Shortcut Legend option.
10. Edit any layout and add a field that contains the choice that you assigned a keyboard shortcut to.
11. Using your keyboard, verify that the keyboard shortcut is working by holding down and pressing the assigned
keys.
l Owner drop-down—determines which users can view the layout. Select from the following options:
l Public—all users can see the layout. This is the default selection.
l Specific User—limits the visibility of the layout to the selected user in the drop-down.
l Me—limits visibility to the logged in user.
Note: System admins can view layouts and other securable items that users have made private.
l Object Type—the object type that the layout uses to modify or code. For example, select Document as the
object type if you were creating a layout for coding documents.
l
Note: The Document layout is the only layout that contains the Enable Copy From Previous field. See
Copy from Previous on page 270
.
l Name—the name of the layout. There is a 50-character limit for this field.
l Order—the number that represents the position of the layout in relation to the other layouts. The lower the num-
ber, the higher the position on the list. Layout order can be any positive or negative integer, but you can't use
decimals.
l View Order—click to open up a pop-up window displaying the order of existing views.
l Overwrite Protection—prevents a user from saving changes to an item that another process has modified
since the user opened or edited the layout. By default, this field is set to Disabled.
l You can edit this field only when the instance setting AllowChangesToOverwriteProtection is set to
True in the instance setting table in SQL. By default, this value is False. Contact Relativity Support if you
would like to edit this instance setting in your environment.
Other
Note: If you have entered a coding decision and have not saved it before selecting a new layout, a pop-up will
display. Click Cancel to go back and save the coding decision before changing layouts or click OK to discard
the coding decision and proceed to the new layout.
l Edit Layout Information: [Layout Name]—click this link to navigate back to edit mode for the layout you are
currently updating. See Creating and editing layouts on page 256.
l Category—contains fields on the layout. See Adding and editing categories on page 269.
l Layout group—consists of one or more categories or object lists in a tabular format. See Creating and editing
a layout group on the next page.
l Properties—depending on the selected item in the layout, that item's properties appear here. See Field prop-
erties on page 268 or Object list properties on page 264.
l Add Category/Add Object List drop-down—use these buttons to add a category or an object list to the layout.
l Add Category—adds a new category to the layout. See Adding and editing categories on page 269.
l Add Object List—adds a new object list to the layout. See Adding and editing an object list on page 263.
l Fields—drag and drop available fields onto the layout category or object list. See Adding fields and text on
page 264.
1. From the layout builder, click and drag a category/object list over another category/object list, then let go of your
cursor click. A plus sign appears to the right of the category that you're dragging the other category onto.
To delete a category/object list, click next to the item. If the category/object list contains fields, a warning appears
before deletion.
To move a category/object list outside of a layout group, click and drag that item out of the group and place anywhere
on the layout.
Note: From the Properties section, click to collapse the properties or click to expand an item's properties.
1. Click the Manage link on a single choice or multiple choice field on the layout. The Choice editor modal opens.
2. Click Add Choice,Add Many Choices, or Click to add a choice.
3. Enter a name for the choice or many choices.
4. (Optional) Click Details to further customize the choice.
5. Modify the details of the choice.
6. Click Close.
New choices appear at the bottom of the list of choices. New choices also appear in the Choices tab and Field forms.
Note: If you have edit permissions, you can reorder the choice.
Note: 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.
1. From the Layout Options console, click the Add Category drop-down > Add Object List. A new Object List
appears in the layout builder and its corresponding properties appear in the Layout Options console. To edit an
existing object list, click the object list.
2. Make changes to the properties as applicable. See Object list properties on the next page.
3. Click Save or Save and Close.
To delete an object list, click next to the item. If the object list contains fields, a warning appears before deletion.
To move an object list, click and drag the item to anywhere on the layout.
Note: From the Properties section, click to collapse the properties or click to expand an item's properties.
l Object - displays available object types (child or associative). Your selection determines the type of objects that
appear in the list. If there are no available linked objects, a warning appears.
l View - displays views available for the selected child or associative object.
l Link View - determines which fields are available when clicking the Link button to link to an existing object to
the current layout's object.
l Links Point to Popup - creates a hyperlink that displays object details in a pop-up. Select Yes to create the
link or No if you do not want the link available.
l Friendly Name - re-name the object list to a more user-friendly name.
l Field - displays the name of the field that is added. You can select any available workspace field. You can add a
specific field only once to the layout.
l Display Type - controls how the field appears on the layout. The field type determines the available display
options:
l Fixed length - text appears as text.
l Whole number - appears as an integer.
l Date - appears as a date.
l Yes/no - has three values - blank, yes, or no. This field can be displayed as a drop-down menu, check-
box, or radio button list.
l Long text - appears as text.
Note: If a field with long text is selected and it contains enough text, the long text field may affect the
display of other fields in the layout that are beneath it.
l Rich text - appears as text with bold and italics. This option is only available if the field has the Allow
HTML property set to Yes.
Note: The Sanitizer object controls whether HTML attributes are sanitized and how specific HTML
content is sanitized from fields on page render. You can modify the sanitizer object to add HTML alerts
and links. We recommend not modifying the default setting.
label and a box containing the current field values. Reviewers click , which displays a filterable
list of field choices. Filtering can be applied to pop-up picker views to find choices. For more information
on the pop-up picker, see Pop-ups on the layout.
Note: If a coding layout becomes long and cumbersome, change the field display from checkbox list to
pop-up picker. This unclutters the layout by effectively hiding the field's choices and presenting them
only if necessary. Displaying a large number of choices with check boxes, drop-down menus, or radio
buttons on a layout can also slow performance. The display type automatically flips to a pop-up picker
if the number of choices exceeds the configurable choice display limit.
l Repeat Columns controls how single and multiple-choice lists appear on a layout. When you select this option
for a multiple-choice field, choices are ordered left to right, and top to bottom.
l Single Column Display: Enter 0, 1, or leave the option blank.
l Multiple Column Display: Enter any value higher than 1 to set the number of columns. A value of 2 res-
ults in a two column display.
l
Custom label is used to display your own text instead of the field name. Click button to enter your custom
label.
To remove a field from a category, click next to the field. The layout builder moves that field back to the Fields list
for future use.
Note: The option Allow Copy from Previous is disabled for fields that have their Read-Only option set to Yes, as
well as for system and relational fields such as MD5 HASH. See Copy from Previous on page 270.
Note: If a field with long text is selected and it contains enough text, the long text field may affect the display
of other fields in the layout that are beneath it.
l Rich text - appears as text with bold and italics. This option is only available if the field has the Allow
HTML property set to Yes.
l Single-choice list - appears as a drop-down menu or radio button.
l Decimal - appears as a decimal.
l Currency - appears as currency.
l Multiple-choice - list can appear as a checkbox list or pop-up picker. A pop-up picker displays the field label
and a box containing the current field values. Reviewers click , which displays a filterable list of field
choices. Filtering can be applied to pop-up picker views to find choices. For more information on the pop-up
picker, see Pop-ups on the layout.
Note: If a coding layout becomes long and cumbersome, change the field display from checkbox list to pop-
up picker. This unclutters the layout by effectively hiding the field's choices and presenting them only if
necessary. Displaying a large number of choices with check boxes, drop-down menus, or radio buttons on a
layout can also slow performance. The display type automatically flips to a pop-up picker if the number of
choices exceeds the configurable choice display limit.
l Show Name Column displays the field name as label when you select this checkbox. Clear the checkbox to
hide the label.
click to open the rich text editor. See Using the rich text editor on page 272. If you enter rich text, the mes-
sage Rich text added appears.
1. From the Layout Options console, click Add Category. A new Default Category appears in the layout builder
and its corresponding properties appear in the Layout Options console. To edit an existing category, click the
category.
2. Make changes to the properties as applicable. See Category properties below.
3. Click Save or Save and Close.
l Name - the name of the category. This name appears as a section header in the layout.
l Contextual Help - add contextual help text to the layout to further guide users as they are interacting with the
fields in this category.
l
Click to load a web-based rich text editor where you can enter and edit rich text contextual help.
See Using the rich text editor on page 272. If you enter rich text, the message Rich text added appears.
l
Contextual Help appears as in the layout. Users can click this icon to display the contextual help mes-
sage.
l Collapsible - Determines whether the category can be collapsed or not in a layout. If Yes is selected, the cat-
egory can be collapsed by the user. If No is selected, the category cannot be collapsed by the user even if Col-
lapsed By Default is set to Yes.
l Collapsed By Default - Determines whether the category is collapsed when each document is loaded in the
Viewer or not. If Collapsible is set to Yes and Yes is selected for this option, the category will be collapsed by
default whenever a document is opened in the Viewer. If No is selected, the category will be expanded
whenever a document is opened in the Viewer.
1. Navigate to the Layouts, click the layout on which you want to enable Copy from Previous.
2. Click Edit.
4. Ensure that all applicable fields on the layout have the option Allow Copy from Previous set to Yes. If those
fields are set to No and you want their values to be copied during review, set the Allow Copy from Previous
option to Yes. If you need to remove the Copy from Previous option from a layout click Disable Copy from Pre-
vious. This button only becomes available after you add the toolbar to a layout.
l
Previous icon - displays to the left of any fields that were previously saved. The copyable coding values
assigned to this document are applied to current document, when the reviewer clicks the Copy button.
Relativity displays next to fields with values that you can copy from the previous document. After you copy the
value into the field, this icon is replaced with . The icon redisplays next to a copied field that you have modified.
To use Copy from Previous:
1. When you start a review session, code the values for the first document and click Save & Next. This enables
the Copy option on the document layout. The Previous field is updated with the document identifier of this first
document.
2. Click Copy when you want to copy the coding values of the designated fields from the previously-saved doc-
ument to the current one. After Relativity populates the layout with these coding values, you can continue to
modify them.
3. Click the Save & Next button to save your changes, and continue the review process.
l If you click Save or Cancel, the layout appears as read-only and the Copy is disabled. You can click Edit
to restart the review. You must then code the first document, and click Save & Next before the Copy but-
ton is enabled. Whenever you leave Edit mode or select a different layout, you need to repeat this pro-
cess.
l
In the layout, the Previous icon displays to the left of the field that you previously saved.
Note: The default keyboard shortcut for the Copy from Previous button is Alt + Shift + Z. However,
your workspace may be configured with a custom keyboard shortcut. Contact your system admin for
additional information.
l Supports both inline and pop-up display type for a more seamless experience. See Adding fields and text on
page 264.
l You can configure the maximum text values for long text fields using the instance setting Max-
imumNumberOfCharactersSupportedByLongText in the Instance setting guide.
The rich text editor is available in several circumstances:
l Long Text field—the Enable HTML field option is enabled on a long text field which is added to a layout. See
Enable HTML in Field information on page 149.
Note: The Sanitizer object controls whether HTML attributes are sanitized and how specific HTML content is
sanitized from fields on page render. You can modify the sanitizer object to add HTML alerts and links. We
recommend not modifying the default setting.
- change the font type. Arial is the default font type. You can configure the default font
using the instance setting, RichTextEditorFontDefault. See RichTextEditorFontDefault in the Instance setting
guide.
l
—changes selected text background highlight color.
l
—bolds selected text.
l
—italicizes selected text.
l
—underlines selected text.
l
- customize the space between each line of text.
l
—insert hyperlink. Here, you can specify the URL, link text, and whether the link opens in a new tab.
l Relativity requires HTTPS links only. Links need to follow the following format: start with https://, and can
include forward slashes, periods, and alphanumeric characters. For example, <a href-
f=”https://www.relativity.com/customers/” >Relativity Customers</a>.
l To add a link, you must be in the Legal Hold admin group, or a group that has view permission for the
Object security permission InstanceSettings. For more information, see the Admin guide.
l To add a link, you must update the DomainNameWhiteListUrls instance setting. It's a semicolon-delim-
ited list of allowed domains. For example, "google.com;mozilla.org".
—insert an image from a URL. You can re-size the image in the text editor.
Note: RelativityOne requires HTTPS links only. Links will need to follow the following format: start with
https://, and can include forward slashes, periods, and alphanumeric characters. Example: <img src-
c="https://i.imgur.com/m1TEWWW.png" />.
—insert a table.
Note: Copying and pasting into the rich text editor only works when copying from MS Word, Chrome, and Firefox.
This is currently not possible for Internet Explorer 11.
4. Click Save.
Note: The Create Search from List button has been deprecated. To create a search from a list, create a new saved
search that includes the desired list as a condition.
1. Click the object's tab in your workspace. For example, if the name of the object type for which you saved a list of
items is Media, click the Media tab.
2. Click the Create View icon.
3. Type a name for the new view in the Name field.
4. Verify Object Type is set to the object type for which you saved a list.
5. Click Next.
6. Add the fields you want to include in your view to the Selected Fields box.
7. Click Next.
Note: For more information on creating a view, see Creating a view with field categories on page 634.
1. Navigate to Home.
2. Click the Relativity Script Library tab.
To add library scripts to your Script tab in a workspace for your users to run, refer to the Relativity Admin Guide.
Caution: Changes to SQL fields executed by Relativity Scripts do not produce Audit logs.
Script Description
Analytics billable Allows a partner to assess the billable size of a potential Analytics index submission.
estimate
Billing statistics - Reports on peak billable data for all cases in a Relativity environment; this can be used in envir-
case rollup onments where the auto-emailed statistics feature is not possible.
Billing statistics - Reports on all users who have had access to the case at any time during the month.
users
Case permission Reports on all users, workspaces, groups, and each group's permissions in a Relativity envir-
audit onment.
Choice field Selects a specified number of sample documents across categories chosen by the user, ensur-
stratified sampling ing that each category is represented equally.
Create Cluster Creates job entries in the EDDS database to upgrade Analytics clusters for CAAT 3.17.2.
Upgrade Jobs
Globally administer Forcibly assigns a keyboard shortcut to a specific system function; this script runs against all
keyboard shortcuts workspaces.
Monitor Cluster Checks and reports the status of all Analytics cluster upgrade jobs recorded in the EDDS data-
Upgrade Jobs base.
Lockbox report 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.
Lockbox Bypass The Lockbox Bypass Report script provides audit history of changes to the Lockbox instance
report setting, by whom, and when.
Populate parent to Populate parent to child is a workspace-level script propagates the Document ID of the parent
child document to any children of that document.
Processing Provides a report of processed data sizes per processing set and user in all workspaces in the
statistics environment and a summary of all processed data in all workspaces in the environment.
Propagate sent Sets all email families' documents to the same sent date as their parent documents in a case.
date to family
documents
Report sample- Generates reports for the deprecated sample-based learning feature.
based statistics
Reviewer statistics Reports 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.
Script Description
Australian Renumbers your Relativity documents and Host/Family fields into a standard Prefix, Box, and
Document ID Document format.
Get database Displays size and location information for all database files in a specific workspace. Use the
size following SQL command to run this script:
exec sp_helpdb <databaseName>
17.1.2 Inputs
1. Create a saved search that returns the documents you would like to index. No special fields are required.
2. Navigate to the Scripts tab.
17.1.3 Results
The following fields are returned:
l Document Total
l Documents with Natives
l Documents with Images
l Documents with Text Only
l Total Billable Size in GB
Note: This script is not included by default in the Relativity Script Library. To request this script, contact Relativity
Support.
Perform the following steps to install Australian Document ID to Relativity’s Application Library:
The Billing Statistics - Case Rollup script is a billing script that reports on peak billable data for all cases in a Relativity
environment. The peak billable data is the highest value within the range of a single month. This script can be used in
environments where the auto-emailed statistics feature is not possible. The results of this script will only update after
an off-hours agent runs.
Note: You must run this script in Admin mode and not from within a workspace. Otherwise, you will receive a
warning and the script will not complete.
Note: Billing Statistics - Case Rollup stores data for 13 months by default to ensure high performance. If you would
like to store this data for a longer period of time, edit the BillingDataRetentionPeriodInMonths instance setting
from its minimum value of 13 months to your desired value.
Refer to the Billing FAQs in the Relativity Community for more detailed information:
17.3.1 Inputs
After clicking Run on the Script console, enter values for the following fields:
17.3.2 Results
After you run the script, the Billing Statistics – Case Rollup report is displayed for the specified month and year. In this
table, the term peak refers to the highest value within the range of a single month.
File categorization is as follows:
Column Definition
Account The name designated as the account name.
Activity Status Reflects whether a workspace was Active or Inactive in a specific month. This
determination is based solely on a single document view within the workspace
during that month. No other actions within the workspace (e.g., adding/deleting
documents, user activity) affect its activity status.
Note: Data for the timeframe of June to August 2023 may be inaccurate due
to a field being temporarily disabled.
Archive Status Indicates a status of Archived if an ARM workspace restore is in progress. Other-
wise the status is Online.
AuditRecordCount The total number of audit records stored in Data Grid per workspace. We will
deprecate this field starting in April 2025, and queries by month will return a
value of 0 from April onwards.
AuditSize The total size of audits in GB for the workspace. If the workspace does not have
the Audit application installed, this calculation will be blank. We will deprecate
this field starting in April 2025, and queries by month will return a value of 0 from
April onwards.
CA Image Documents Number of documents with images and without natives run through a Analytics
Index or Structured Analytics Set for the first time during the reported month.
CA Native Documents Number of Native documents that were indexed with Content Analyst for first
time, during the reported month.
CA Native Size Size in GB of all Native documents indexed with Content Analyst for first time,
during the reported month.
Note: Customers cannot directly control the size of LDF within the Relativity
infrastructure. This aspect is classified as an infrastructure detail, and
Relativity does not assure its reduction. The size of LDF can be
influenced by database modifications aimed at optimizing performance.
Matter Artifact ID Unique artifact ID of the matter (through client) associated with the workspace.
If the workspace is deleted, no value is reported.
Matter Name The name of the matter associated with the workspace. If the workspace is
deleted, no value is reported.
MDF Size The peak database primary data file (MDF) size of the workspace in GB.
Note: If your MDF is split into multiple NDFs, the sum of all NDF sizes is
returned.
Note: Customers cannot directly control the size of MDF within the Relativity
infrastructure. This aspect is classified as an infrastructure detail, and
Relativity does not assure its reduction. The size of MDF can be
influenced by database modifications aimed at optimizing performance.
Name The instance name and the workspace name; if the workspace name is obfus-
cated, it is replaced by the workspace identifier.
Native File Size The peak size in GB of native and transcript files in the workspace that have not
been imported using Integration Points with file pointers. This value is taken
This script is a billing script that reports on all users who had their Relativity access enabled, and belonged to a group
which was assigned to a workspace during a specific month. The data is taken as a snap shot daily when the Billing
Agent runs. This script can be run at any time from Home.
Note: Billing Statistics - Case Rollup stores data for 13 months by default to ensure high performance. If you would
like to store this data for a longer period of time, edit the BillingDataRetentionPeriodInMonths instance setting
from its minimum value of 13 months to your desired value.
17.4.1 Inputs
After clicking Run on the Script console, enter values for the following inputs:
17.4.2 Results
After you run the script, the Billing Statistics - Users report displays.
The report includes the following columns:
Column Definition
Case The name given to the workspace in Relativity.
Name
Case Arti- The unique Artifact ID associated with the workspace specific to that environment.
fact ID
Usage ID The usage ID given to the workspace. This is a unique workspace and month identifier which combines
Instance, Case Artifact ID, Year, and Month.
Case User The unique identifier for that workspace, user, and month which combines Usage ID and User Artifact
ID ID.
User Arti- The unique system-level Artifact ID associated with the user.
fact ID
Relativity The user's name as entered in the Relativity workspace.
Case User
Name
Original The original e-mail address of the user if changed during the month.
Email
Address
l If you plan to sample documents across clusters, you must create the clusters first. For more information, see
Clustering in the Analytics guide.
l You can use any single-choice or multiple-choice field to define the categories for the script.
l When used on a multiple choice field with parent and child choices, this script only considers the child choices.
In a cluster visualization, these are represented as the outermost ring of clusters.
17.5.2 Inputs
1. Before running the script, create a Yes/No field to track which documents have been selected by the script. If
you use a previously created Yes/No field, the script will overwrite any existing values.
2. Create a saved search which includes documents from all categories you want to sample. If you are sampling
from a specific set of clusters, make sure only the desired clusters are selected when creating your saved
search.
3. Navigate to the Scripts tab.
4. Select the Choice Field Stratified Sampling script. If the script is not present in the workspace's Script tab, you
must add it.
5. Click Run.
6. In the pop-up window, fill out the following fields:
1. Choice to sample from - select the choice field containing the categories you want to sample.
2. Saved Search - select the saved search created in step 2.
3. Number from each choice - enter the number of documents you want to sample from each category.
4. Is Sampled Field (Yes/No) - select the Yes/No field created in step 1.
7. Click Run.
17.5.3 Results
Once run, this script updates the Yes/No field to Yes for the sampled documents. To view all sampled documents, go
to the Document List view and search for a Yes value in that field. You can then code the documents or create a saved
search to set them aside for later.
Note: 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.
17.6.2 Inputs
Before running the script, perform the following tasks:
l Run and produce a production. For more information, see Production console.
Before running the script, ensure you create the following Document fields in the workspace:
l Begin Bates
l End Bates
l (Optional) Begin Bates Attachment
l (Optional) End Bates Attachment
l (Optional) Batch Size (Default 10000)
Running the script populates these fields on the Document table.
17.6.3 Results
This script updates and stores the Bates fields you create on the Document table so you may continue using previous
production workflows.
17.9.1 Category
System Functionality
17.9.3 Inputs
Use the following steps to run the script Globally Administer Keyboard Shortcuts:
Note: If you later want to modify this keyboard shortcut, you need to rerun the script with the new settings.
You cannot rollback the changes.
17.9.4 Results
In the Results section, you can review the list of workspaces updated with the new keyboard shortcut combination. A
list of parameters used by the script to perform the update appears. To download a list of workspaces with the updated
shortcut, click the Go button next to the Export to File option.
17.10.2 Inputs
Before running the script, complete the following inputs:
17.10.3 Results
Once this script has been run, the Sent Date field will be updated so all family documents in a case have the same
value as their parent document. The parent must be the record with the lowest ArtifactID.
Note: This script ignores records where the field assigned to Date Propagated field is set to Yes. As a result, this
script will only affect documents where this field is empty or set to No.
The RelativityOne Billing Statistics - RelativityOne - Case Rollup reports peak data sizes for all cases in a
RelativityOne environment, including metrics related to Repository and Cold Storage Workspaces.
The peak data sizes represent the highest recorded sizes for any given Workspace within a single month. This is not in
line with how Relativity bills. For detailed insights into your specific billing, please use the Cost Explorer.
Note the following:
l You must run this script in Admin mode and not from within a workspace. Otherwise, you will receive a warning
and the script will not complete.
l This script can be used in environments where the auto-emailed statistics feature is not possible.
l The results of this script will only update after an off-hours Billing Agent runs.
For more details on billing, see the Understanding Cost in RelativityOne knowledge base article on the Relativity
Community.
Note: Billing Statistics - Case Rollup stores data for 13 months by default to ensure high performance. If you would
like to store this data for a longer period of time, edit the BillingDataRetentionPeriodInMonths instance setting
from its minimum value of 13 months to your desired value.
1. Log in to the Relativity Community and save the Billing Statistics - RelativityOne Case Rollup (filename: Relativ-
ity_BS-R1_Case_Rollup.xml) file locally.
2. Navigate to the Relativity Script Library tab and click, New Relativity Script.
3. Copy the contents of the downloaded script to create a new entry and click Save.
4. Once the script is saved, it will be readily available for use in your environment.
17.11.2 Inputs
After clicking Run on the Script console, enter values for the following fields:
17.11.3 Results
After you run the script, the Billing Statistics – Case Rollup report is displayed for the specified month and year. In this
table, the term peak refers to the highest value within the range of a single month.
File categorization is as follows:
Column Definition
Account The name designated as the account name.
Activity Status Reflects whether a workspace was Active or Inactive in a specific month. This
determination is based solely on a single document view within the workspace
during that month. No other actions within the workspace (e.g., adding/deleting
documents, user activity) affect its activity status.
Note: Data for the timeframe of June to August 2023 may be inaccurate due
to a field being temporarily disabled.
Archive Status Indicates a status of Archived if an ARM workspace restore is in progress. Other-
wise the status is Online.
Note: Customers cannot directly control the size of LDF within the Relativity
infrastructure. This aspect is classified as an infrastructure detail, and Relativ-
ity does not assure its reduction. The size of LDF can be influenced by
database modifications aimed at optimizing performance.
Linked Image File Size GB Size in GB of all linked Image documents. This includes TIFF files and PDFs
classified as image
Linked Native File Size GB Size in GB of all linked Native and transcript documents.
Linked Production File Size GB Size in GB of all linked Production documents. This includes stamped TIFF,
produced PDF, and produced redacted native files.
Linked Total Billable File Size GB The billable size in GB of all linked files in the workspace. Linked Total Billable
File Size is reporting on the size of linked natives, images and productions.
Matter Artifact ID Unique artifact ID of the matter (through client) associated with the workspace.
If the workspace is deleted, no value is reported.
Matter Name The name of the matter associated with the workspace. If the workspace is
deleted, no value is reported.
MDF Size The peak database primary data file (MDF) size of the workspace in GB.
Note: If your MDF is split into multiple NDFs, the sum of all NDF sizes is
returned.
Note: Customers cannot directly control the size of MDF within the Relativity
infrastructure. This aspect is classified as an infrastructure detail, and Relativ-
ity does not assure its reduction. The size of MDF can be influenced by
database modifications aimed at optimizing performance.
Name The instance name and the workspace name; if the workspace name is obfus-
cated, it is replaced by the workspace identifier.
Native File Size The peak size in GB of native and transcript files in the workspace that have not
been imported using Integration Points with file pointers. This value is taken
from the peak of Total Billable File Size field in GB.
Peak Status The peak value of the Workspace Status field in a given month. If any work-
space was active during the reported month, the status is Active; otherwise, it is
Inactive.
Prior CA Image Documents Number of documents with images and without natives run through a Analytics
Index or Structured Analytics Set for the first time during the prior month.
Prior CA Native Documents Number of Native documents that were indexed with Content Analyst for first
time, during the prior month.
Prior CA Native Size GB Size of all Native documents indexed with Content Analyst for first time, during
the prior month.
Prior CA Text Only Documents Number of documents without an image or native that were run through a Ana-
lytics Index or Structured Analytics Set for the first time during the prior month.
Prior CA Total Documents Total number of all documents run through a Content Analyst Index for the first
time, during the prior month.
l Project Summary—this provides a consolidated set of quality metrics from the entire project so that you can
see the state of the project based on the last round completed. It includes manually coded documents, project
categorization results, project overturn results, and control set statistics.
l Overturn Summary—this provides a high-level view of a project’s overturn percentages and tallies from round
to round. The accompanying table gives even greater detail, including a breakdown of responsive and non-
responsive overturn rates.
l Round Summary—this report is split into two graphs. The first graph provides a categorization breakdown of
each category per round, allowing you to track categorization results as the project progressed. The second
17.12.2 Inputs
1. Navigate to the Scripts tab.
2. Select the Report Sample-Based Statistics script. If the script is not present in the workspace's Script tab, you
must add it.
3. Click Run.
4. In the pop-up window, fill out:
1. Project—select the legacy project you want the report based on.
2. Report Type—select the type of report.
5. Click Run.
6. Click Accept on the pop-up confirmation.
This script may take a few minutes to process.
17.12.3 Results
After the script finishes, a custom URL will appear in the Script Output pane. To view the report, copy and paste the
URL into a new browser tab.
This report can be exported into a variety of formats using the drop-down menu in the upper right corner.
l Reviewer Statistics - use this script to generate a report that lists the system admins.
l Reviewer Statistics - No System Administrators - use this script to generate a report that does not include
system admins.
Note: Ensure that users running this script have both the Relativity Script Object Security > View permission
enabled and View All Audits checked in the Admin Operations section of Other Settings.
17.13.1 Inputs
Enter the following field information:
l Reviewer Time Zone - The reviewer time zone for which you wish to report on.
l Start Date - the start date for which you wish to report on.
l End Date - the end date for which you wish the report on.
l Include Additional Action - set this field to add statistics for Mass Edits and Propagation.
l Downtime threshold (minutes) - this field helps to calculate the Total Usage Time metric and determines
whether two audits belong to the same group of action. The default value for this field is 60 minutes. If the time
difference between the two actions is less than the Downtime threshold, that time will be included to add up to
the Total Usage metric; if it's greater than the Downtime threshold, only two minutes will count for these two
actions (one minute for each action).
Note: If the Audit application is installed in your workspace, the script pulls audit data from Elasticsearch.
17.13.2 Results
Once you run this script, the Reviewer Statistics report displays.
Note: By default, the following columns are not included in the output. To include these columns, in the Include
Additional Action drop-down list, select Mass Edits and Propagation.
Propagations
Distinct Propagations
Propagations Per Hour
Propagations Per Day
Distinct Propagations Per Hour
Distinct Propagations Per Day
Column Definition
17.14.2 Inputs
Note: Before running this script, you must create a Yes/No field to act as the Duplicate Indicator.
l Duplicate Indicator - the Yes/No field that determines whether documents are duplicates.
l Relational Field - the field that shows document relationship (such as MD5 Hash).
l Document Sort Field - the sort order field for duplicate documents. For example, if MD5 Hash is specified as
the Relational Field and Control Number as the Document Sort Field, the document with the lowest Control
Number will be flagged as original; the other documents with the same MD5 Hash field value will be flagged as
duplicates.
17.14.3 Results
When you run this script, all documents that are duplicates are marked Yes and all documents that are original are
marked No.
17.16.2 Inputs
Before running the script, create a decimal field to store the script's native file size output. You can map to this field in
the script. Be sure to add the field to your views to see the results.
17.16.3 Results
Once run, this script updates the Native File Size field with the file size for any document in the workspace. Note that
there could be a mix of file size values in bytes and kilobytes.
17.17.2 Inputs
Before running the script:
l Run a production
Also, ensure that the Attachment relational field is set in the production settings for the following multi-object fields:
Note: You can still run this script after running a production if the Attachment relational field wasn’t set on the
production.
17.17.3 Results
Once run, this script updates:
l The BegAttach field with the beginning bates of the family group
l The EndAttach field with the end bates of the family group
If you want to combine the attachment bates range data into one field for a singular range, run the Copy to Legacy
Document Fields script, then mass replace those fields into the document object fields. See Copy to Legacy
Document Fields in the Admin Guide.
Note: The script will not work on long text fields stored in data grid. You must disable the Stored in Data Grid option
when creating the long text field.
Note: For workflows where you need to run this script on a document that had a previously populated folder path,
the Set Relativity Folder Path field may not populate fields on one workspace. For more information and a solution,
see Set Relativity Folder Path Field not populating fields on one workspace.
17.18.2 Inputs
By default, this script will only update documents that do not have an existing folder path. To update the folder path of
documents with existing folder paths, ensure the following are in place before running the script:
Note: If you want to able to search the original folder path after running the script, save the original folder path
in a separate field before you clear the existing folder path.
17.18.3 Results
Once the script has run, it reports on each distinct folder path in the case, returning the number of documents per path,
and the execution time of the script. It also updates the Folder Path field with the Relativity folder path of that
document.
A table with the following is returned:
Column Definition
17.19.1 Inputs
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.
Note: If two people edit a markup at the same time, an error occurs.
18.1 Highlights
When you create a highlight, a colored box appears in the area you select, just like using a highlighter.
18.2 Redactions
A redaction hides text on a page. In Relativity, you can create several different types of redactions:
1. Click the Redaction Mode icon and select Inverse Redact from the drop-down menu.
2. Draw the inverse redaction boxes across the sections of the page you do not want to redact.
A blue cast indicates where you will add the black redaction, and the white box indicates the area that is not
redacted. You can move or re-size the white box using the controls. You can also highlight text that is not redac-
ted.
1. Click the Redaction Modeicon and select Mass Redact from the drop-down menu.
The Mass Redact Options pop-up appears.
2. Select the type of redaction to apply. You can select from the following:
1. You can use any of the following methods to select markups for deletion:
l Left-click and drag the selection box over the markups you wish to delete.
l Hold down on Ctrl on your keyboard, and left-click on each markup you wish to delete.
l Right-click on a markup after selecting any other markups you would like to delete.
2. Select Delete from the right-click menu.
The Delete Markups modal displays.
3. Verify that you wish to delete the number of markups displayed in the modal and click the Delete X Markups
button.
The selected markups are deleted.
Note: If you have a full-page redaction applied to an image, then you apply an additional full-page redaction, the
most recently applied full-page redaction appears on top. If you then delete the second redaction, the first full-page
redaction persists.
1. Choose the desired markup set from the drop-down list in the bottom-left corner of the Viewer.
2. Right-click the redaction and select the default redaction text from the markup set.
Note: The only proper way to secure the text behind a redaction is to the produce the document that contains the
redacted text. If a group has View rights only to a markup set (not Edit or Delete rights) and a reviewer in that group
loads a document in the Viewer because they have no other way to view that document, they can actually see the
text behind the redaction.
While viewing a document, you can change markup sets in the drop-down menu and see different highlights and
redactions in the document. Multiple reviewers can redact the same document at the same time using different
markup sets.
In the Viewer, you can locate markups in a document using the Markup Navigation pane. To open this pane, click the
Markup Sets icon in the lower left corner of the Viewer. The Markup Navigation pane displays a list of all redactions
and highlights that reviewers created in the document, as well as references to their page numbers and parent markup
sets.
You can click anywhere on the markup row to jump to the page where the markup occurs. In addition, Relativity
updates the active markup set to the one associated with your row selection in the Markup Navigation pane.
Note: Before you apply markup to a document, note that the Native Time Zone Offset field controls the date and
time that displays on redacted and highlighted images. You may want to review and adjust the UTC value to avoid
placing incorrect time designations on documents you intend to produce.
19.1 Permissions
The following permissions are needed to use each part of markup sets:
19.3 Fields
Markup sets contain the following fields:
Note: We recommend ordering markup sets by groups of 10, such as 10, 20, 30, and so on. Using this
numbering scheme you can easily insert another markup set without having to reorder the existing
ones.
l Redaction text - enter the words or phrases that you want to set as textbox redaction options. To set multiple
options, enter each term on a separate line.
Note: When copying a Markup Set, any existing associated redactions on documents are also copied to the
new Markup Set.
Notes:
l Some mass operations like Edit, Replace, and Delete can temporarily lock down the document table while
executing. In a workspace with a large number of records and users, the table may be locked for an extended
period of time and prevent users from performing standard edits. In such cases, we recommend carrying out
mass operations at night or an off-peak time.
l You can't use mass operations on Data Grid-enabled fields.
l Copy—gives group members the rights to copy securable objects such as views and layouts.
l Delete—group members can mass-delete documents. Mass delete also requires the rights to delete doc-
uments.
l Edit—gives group members the rights to use their layouts to simultaneously edit document field values for mul-
tiple documents.
l Export—gives group members the rights to export audit data via Audit.
l Export to File—gives group members the right to export the contents of a view to a .csv, .xls or .dat file.
l Image—group members can simultaneously send image requests for multiple native files.
l Move—gives group members the right to simultaneously move documents from one or more folders to one tar-
get folder. Mass Move also requires add and delete document rights.
l Merge—gives group members the rights to select and merge multiple entities into a single entity when using
name normalization in Analytics.
l PDF Actions—gives group members the ability to download, create, store, or number PDFs. For more inform-
ation, see Mass PDF permissions
l Print Image—gives group members the right to simultaneously print images from multiple documents.
l Produce—gives group members the right to simultaneously add multiple documents to a production set.
l Replace—group members can perform a replace operation on multiple documents. Examples include:
l Copying the contents of one text field to another.
l Adding a set string to the beginning or end of an existing field.
l Merging the values of a source field with the values of a target field.
l Process Transcript—group members can process imported transcripts for viewing in Relativity.
l Send To Case Map—group members can send multiple documents to CaseMap.
l Tally/Sum/Average—group members can tally, sum and average the values of any numeric fields. This action
is recorded under the document history.
l Custom mass operations—may appear in this list. They include mass operations that you added to Relativity
or that are available in applications currently installed in your environment.
Note: Users with permissions for the Queue Management tab in the Tab Visibility section of the Admin Security con-
sole automatically gain access to the Mass Operation Jobs tab.
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.
The Mass Operation Jobs page contains the following fields:
l Start Time—the date and time at which the mass operation was started.
l Artifact Type—the object on which the mass operation was run. For example, if you started a mass Edit job on
any number of items from the Document list in your workspace, this will display Document.
l Artifact Count—the number of artifacts returned from the job.
Note: As long as users have the listed security permissions, they do not need view permissions to the work-
spaces or the production jobs to use Cancel Production Job.
l Click Ok.
For more information about the Production queue, see Production queue.
Note: To perform mass operations on an object type, ensure that the 'Use Relativity Forms' setting is enabled for
that specific object type.
3. Select the layout and fields. There are three options for multiple-choice field values, known as a tri-state check
box:
l Blank removes the value from any of the selected documents.
l Shaded leaves any values on the selected documents as-is.
Note: When mass editing Yes/No fields, the shaded check box sets the value to null.
1. Click Check to create a list of items to add to the field or click Uncheck to create a list of items to remove from
the field. Items not selected remain unchanged. Clicking either Check or Uncheck opens the Available Items
window.
2. From the Available Items window, you can move choices and objects into the Selected Items list. Select the
check box next to the desired selection, and move it to the right panel. This builds a list in the bottom window of
selected items. To remove something from this list, select it and move it to the left panel.
3. Click Apply to proceed with the action to Check or Uncheck the items from the field. Clicking Cancel stops any
action.
4. Once values have been set, a Clear link displays next to the Check and/or Un-Check buttons. You can then
clear the set values without returning to the Items to Check window to remove them. You can add a new choice
to a multi-choice field using the Add link.
5. Click Save to apply your updates and redisplay the item list. If the item list loads slowly, and you cancel the
request, your updates to the documents remain saved.
Note: When you attempt to mass edit documents in the Related Items pane while there are unsaved changes
in the current layout, Relativity displays a message indicating that your changes will be lost. If you continue,
the coding values in the layout are updated to match those selected for the mass edit.
l From the mass operations bar on the document list, choose whether to copy All searchable items, Checked
items, or These items in the current returned set.
l Select Copy in the drop-down menu.
The Copy window displays.
1. Click Ok to copy the items.
l From the mass operations bar on the document list, choose whether to move All searchable items, Checked
items or These items in the current returned set.
l Select Move in the drop-down menu.
The mass move select folder form displays.
l Select the target location and click OK. Note that all documents move to the target directory. The subdirectory
structure of the source folder is maintained.
Note: Mass delete is a permanent action, so ensure you double-check your selections before proceeding, as
this operation cannot be undone. Additionally, Mass operations are not supported for Data Grid-enabled fields.
Deleting documents that were published through Processing has two key effects:
l Marking deleting: The deleted documents get flagged as “Yes” in the “Processing Deletion” field on the Dis-
covered Files page. This helps track which documents no longer exist after being published.
l Recalculating deduplication and publishing new primaries: Relativity automatically analyzes the remain-
ing data to identify duplicates and adjust its understanding of the primary documents. If applicable, new primary
documents may be published to replace the deleted ones. This ensures an exact data representation and
avoids issues with missing information. For more details on this behavior and its implications, refer to the doc-
umentation section on Post-publish delete.
To mass delete documents after publishing, follow the steps in the Processing topic, Post-publish delete > Running a
post-publish delete.
20.8.1.1 Considerations
Deleting Documents:
l >Full deletion: By default, this removes everything - documents, duplicates, and associated files. You can
choose to preserve the document record by keeping it in place and only deleting images or native files.
l Force delete: When performing a full deletion, this permanently removes the selected data. For image and nat-
ive file deletions, you can disable force delete as immediate or permanent removal might be necessary.
l Create audit snapshot: Enable this option to create an extra audit record for every deleted document, helping
you track changes and keep a detailed history.
1. Navigate to the tab for the object that you want to delete.
2. Select Checked items or All items in the current returned set.
3. Select Delete. The Delete Details form prompts you to confirm the deletion.
l
Note: Depending on your access level, you may see a warning on the Delete Details Form when deleting cer-
tain objects. This means that removing these objects will also automatically delete their associated objects
(like child items) and unlink related objects (like associative links).
4. Click Delete to delete the object and its children, as well as unlink associative objects. This message displays
when you have the security permission Delete Object Dependencies listed in the Admin Operations section of
the Security page.
5. (Optional) To view a report showing affected objects, click View Dependencies. When the current object
doesn't have any children or associative objects, the View Dependencies toggle is turned off.
To improve mass delete performance when deleting large numbers of documents, turn snapshot auditing off. See
Enabling or disabling snapshot auditing on delete below.
l Even with "snapshot audit" turned off, the system meticulously tracks every field change for every document,
creating a detailed record. So, even when you delete a document, its audit trail remains preserved, capturing all
alterations made before its deletion. This effectively meets the need to document coding decisions on deleted
documents, as they were finalized and registered before the document's removal.
l While enabling "snapshot audit" offers valuable historical documentation, it comes at a cost: a noticeably larger
audit table and potentially sluggish mass deletions. This occurs because the system meticulously captures
every deleted document, replicating its entirety. This can be resource-intensive and delay your deletion tasks.
PreDeleteHandlers Custom code that runs before Can slow down the Mass deletion process
deleting a document
Note: Users with permissions for the Queue Management tab in the Tab Visibility section of the Admin Security con-
sole automatically gain access to the Mass Operation Jobs tab.
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.
The Mass Operation Jobs page contains the following fields:
l Workspace—the name of the workspace in which the mass operation was started.
l Mass Operation Type—the specific mass operation that was kicked off. This could include any job for which
there is not a dedicated queue, such as:
l Edit
l Replace
l Move
l Status—the current state of the job. This will display one of the following:
l Idle—the job has not yet been picked up by an agent and is not yet in progress.
l Percent complete—the job is in progress at the displayed percentage of completeness. During this
time, you can click Cancel to cancel the job.
l Completed—the job has completed without errors.
l Canceled—the job has been canceled.
l Action—any mass operation that is in progress and displays a completion percentage is also eligible to be can-
celed. To cancel a mass operation, click Cancel on the job in the Action column. To confirm the cancellation,
click Cancel job. The mass operation remains in progress until you confirm its cancellation, which means it is
possible for the job to complete before you are able to completely cancel it. If you want to return to the jobs page
and allow the job to proceed, click Go back.
l Start Time—the date and time at which the mass operation was started.
l Artifact Type—the object on which the mass operation was run. For example, if you started a mass Edit job on
any number of items from the Document list in your workspace, this will display Document.
l Artifact Count—the number of artifacts returned from the job.
1. From the mass operations bar on the document list, choose whether to replace text in Checked items or All
items in the current returned set.
2. Select Replace in the drop-down menu.
l Insert at Beginning - adds the new value to the beginning of the field. A delimiter option appears.
Enter a character to separate the existing and prepended values.
l Search For - use to search (and thus replace) only selected text in the field instead of the entire
field. A new text option displays, where you can enter the text you want to replace.
l Update With - determines what is applied to the field.
l Text - adds text to the field.
Note: The mass image operation is disabled if the Imaging application isn't installed.
l From the mass operations bar on the document list, choose whether to image Checked items or All items in
the current returned set.
Note: The maximum number of documents you can select at one time for the mass image action is 10,000
documents. If the number of documents selected exceeds this value, a warning appears and prevents the job
from running. If you want to image more than 10,000 documents, create and run an imaging set.
Note: If any of the documents you selected to image is of a type that is included in the Restricted Native Types
object on the imaging profile you selected for the mass image job, that document can't be imaged and you receive a
corresponding error message.
20.12 Tally/sum/average
You can use the tally/sum/average operation to tally, sum, or average the values of 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's
recorded under the document history.
Considerations
l You can only use tally/sum/average on fixed-length text, choice, user, and number fields.
l You can't use mass operations on Data Grid-enabled fields.
l Tally/Sum/Average calculates the mean of a column without counting null as 0. When a column contains null
values, the operation yields a different result from an average calculated by summing the column and dividing
1. Choose whether to tally/sum/average Checked items or All items in the current returned set
2. Select Tally/Sum/Average in the drop-down menu. The Tally/Sum/Average pop-up displays with options for
the following fields:
l Field - used as the basis of the calculation. For example, you could select a custodian field if you want a
tally of these entries.
l Function - the option performed on the field:
l Tally - lists a count for each item type in the specified fields of all selected documents or objects.
l Sum - adds the values in the specified numeric fields of all selected documents or objects.
l Average - calculates mean value of the specified numeric fields for all selected documents or
objects.
The result of a tally is similar to a summary report; it outlines the values of a field and the count for each. The
tally runs across the entire section, but only reports the top 100,000 values. After your results appear, you can
perform the following actions:
l Filter the results.
l Clear All filter text.
l Browse through the results using the blue arrows.
l Sort the results.
l Export results to an external file.
20.13.1 Considerations
l Mass exports do not guarantee any sort order in the exported data, nor does mass export to file necessarily
save data in the same order as it is displayed in the interface.
l The Mass export to file option displays in the mass operations bar on the Views, Tabs, and Relativity Scripts
Library tabs.
l You cannot use mass operations on Data Grid-enabled fields.
1. Select the records you want to export from the view. Do not select any records if you would like to export all of
them.
2. Select Export to File in the drop-down menu.
The Exporting form displays.
3. Select values for the fields on the Exporting Documents form. See Fields below.
4. Click Run to export the file or Cancel to cancel the export.
20.13.3 Fields
l Format
l Excel spreadsheet via HTML (.xls) creates an Excel file. Fields are placed into separate cells in the .xls
file. Fields are placed into separate cells in the .xls file.
l Comma Separated Values (.csv) creates a comma delimited text file. Fields are separated by semi-
colons. Fields are separated by semicolons in the .csv file.
l Concordance DAT format (.dat) creates a DAT text file with the standard concordance delimiters. Fields
are separated by semicolons in the .dat file.
Note: The names of exported files include the word export, the date (YYYYMMDD), the time
(HHMMSS in UTC), and a file extension. For example, the name of an exported file might be export_
20131119_16073.xls.
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.
A sample use case for this mass operation involves updating the folder path for documents loaded into the wrong
folder on a workspace. For example, you may have inadvertently selected file path as the folder path when importing
documents via Import/Export.
In addition, the move to folder path mass operation provides you with the ability to move multiple documents to
different folders simultaneously. Unlike the mass move operation, where you can only select a single folder when
moving documents. For more information, see Mass move on page 325.
1. The Document Utilities application requires Relativity 9.4 or above of Relativity. Confirm that you are running
Relativity 9.4 or above in your environment.
2. Log in to the Relativity Community (https://community.relativity.com/s/files), and search on Document Utilities.
When the search results appear, locate the Relativity.DocumentUtilities.rap in the Files section.
Note: You need to register to access the Relativity Community if you don't currently have an account. You
also must have an Admin Contact account type in the Relativity Community to download applications. If you
don't currently have this account type, contact an Admin Contact in your organization, who can then request
that Customer Support assign this account type to you. For more information, contact Customer Support via
the Community site.
l Mass operations - Under the Mass Operations section of the Other Settings Tab in Workspace Security, you
need permissions to the following:
l Separate nested folders in the path with forward slashes (/) or backward slashes (\).
l Don't use a slash as the initial character in your folder path. A final slash isn't required in the folder path.
l Don’t use these special characters (/ \ : ? " * < > |) in your folder names. If your folder names include these char-
acters, Relativity strips them out, except for back and forward slashes used as delimiters. For example, a path
with folders named Custodians|<>/Revie\wed/Ja*?ne would become Custodians/Reviewed/Jane.
l Folder paths may include Unicode characters.
l Folder paths may include the workspace name, but it isn't required. For example, if you have a document with a
destination path of <WorkspaceName>\Custodian and another one with the path of Custodian, this mass oper-
ation moves both documents to the Custodian folder under the workspace root.
l Perform a test on a small sample set of documents before moving a large number of them.
l Execute only one move to folder path mass operation at a time.
Use these steps to move documents to a new folder:
Note: To stop the mass operation, click Cancel. The mass operation finishes moving the current batch of doc-
uments before it stops. Relativity then displays a message indicating the percent of documents that were
moved.
7. Optionally, refresh the page to see the newly created folders. See the following screen shot for an example of a
l
Folder Path Field - click to select the field that you populated with the destination folder path. See Move
to folder path on page 334.
l Delimiter - select forward slash (/) or back slash (\) as the delimiter for any nested folders.
l Move documents with empty folder path - select this checkbox if you want to move documents with empty
folder path fields to the location specified in the Empty folder path placeholder option. If you don't select this
checkbox, Relativity doesn't move documents with empty folder path fields.
l Empty folder path placeholder - enter the name of a folder where you want to move documents that don't
have a destination specified in their folder path field. If the path contains subfolders, separate the folders with
l If a folder path contains consecutive empty directories, Relativity consolidates them into a single dir-
ectory, so that MyFolder\\ \\\MySubfolder becomes MyFolder\[BLANK]\MySubfolder when the name
in this field is [BLANK].
l If a folder path contains two consecutive delimiters separated by a space, Relativity sets the name of the
newly created folder to blank.
l Delete empty folders - select this checkbox to delete any folders within the entire workspace that are empty
after you move the documents. Relativity doesn't delete empty folders when they have dependencies.
Note: If an error occurs during the deletion of empty folders, Relativity stops this process and displays an
error message. It also logs any errors on the Error tab.
l Action - creates a new list or replace the contents of an existing list. Select one of the following options:
l Create new list - creates a new list with the list name specified in the Name field.
l Replace existing list - replaces an existing list with the currently selected objects. Select an exist-
ing list from the Select Item - List window.
l Name - stores the name of a new list. Type the new list name.
6. Click Save.
20.16.1 Considerations
l The mass PDF operation support jobs up to 10,000 documents or 1,000,000 images.
l You cannot use mass operations on Data Grid-enabled fields.
l The PDF application is not available in workspaces created from the RelativityOne ECA Template or in work-
spaces where the Repository Workspace application is installed.
l The PDF application needs to be manually installed on any workspace that was restored using ARM.
l If you are having problems running a PDF job, verify that you have both the PDF Manager and PDF Worker
agents are running and enabled. You can check this on the Agent tab.
l System administrators can configure the PDF Actions permission for individual users or groups by restricting
download, create, store, and numbering operations.
l The PDF permission within "Tab Visibility" settings manages access to the PDF and PDF Profile tabs.
l The PDF Profile permission within "Object Security" settings controls access and operations over the
PDF Profile object.
In order to PDF production images, the user group needs View rights to “Production Data Source.”
Note: System administrators with the correct permissions setup for Save as PDF are unable to test this in Preview
Security mode. This is done to prevent downloading documents that haven't been authorized.
Note: The settings defined in the PDF profile do not apply to the following actions from the PDF Mass Operations:
Count and Delete.
l Creating PDF below—Select “Creating PDF” to display options associated with the “Store” and “Download”
action from the PDF Mass Operation. When selecting this option, the Select Identifier option will enable you to
stamp your PDFs with the content of a single field in a single location: bottom, top, left, right, center.
l Branding PDF on page 346—Select “Branding PDF” to display options associated with the “Brand” action
from the PDF Mass Operation. Select this option to add different branding fields on any of the available loc-
ations: bottom, top, left, right, center. To apply Branding PDF to a PDF, you need to first create your stored
PDFs and then run the Mass PDF operation to add the new branding.
l Relativity PDF—Select this option to create a PDF profile that will generate PDFs using Relativity’s proprietary
PDF engine.
l Native Application PDF—Select this option to create a PDF profile that will generate PDFs using the Native
applications. This is equivalent to how imaging works in Relativity. Basic imaging is equal to relativity PDF and
native imaging is equal to native application PDF.
l Paper Size—select the size for both the PDFs that you create to download and the PDFs you store in Relativity.
The paper size option only applies when the source file type of the PDF job is natives. The paper sizes available
are: Letter, Legal, A5, A4, A3, and original. The original option will maintain both the original paper size and ori-
entation of each page on the native file. The Letter, Legal, A5, A4, and A3 options will create a PDF with portrait
orientation in the selected paper size.
l Burn Native Redactions—indicates that you want to include redacted natives as part of the PDF job. Toggling
this field on makes the Native Options Markup Set field required below.
l Native Options Markup Set—this field is only visible if you selected to Burn Native Redactions above. It indic-
ates which markup set is used to apply native redactions to the documents you are about to convert to PDF.
Select the desired markup set from the drop-down.
Image Source Files Options
The options on this tab are available when the “File Type” selected in the Mass PDF operation is “Original Images.”
l Make Text Searchable—select this option to translate images of text, such as scanned and redacted doc-
uments, into actual searchable text characters in the resulting PDF.
Note: This function applies only to Original Image and Produced Image file types.
l OCR Profile—select the OCR profile to be used to translate images of text into actual searchable text char-
acters.
l Include highlights—select this option to include persistent highlights in the resulting PDFs. This option applies
only when converting original images to PDF, and is only for highlights which are associated with a markup set.
You will be required to specify the markup set profile to use.
l Include redactions—select this option to include redactions in the resulting PDFs. This option applies only
when converting original images to PDF, and is only for redactions which are associated with a markup set. You
will be required to specify the markup set profile to use.
l Include Slip Sheet—select this option to include a slip sheet on the first page of the generated PDF. Available
options are: Blank Page, identifier only, and coding layouts.
Microsoft Word Options
When converting native file types that are MS Word Documents into PDFs using Relativity PDF Engine, the following
options can be configured in the PDF Profile:
l Show Track Changes—if the native MS Word document has track changes, this option will include those track
changes in the resulting PDF.
l Show Comments—if the native MS Word document has comments, this option will include those comments in
the resulting PDF.
Microsoft PowerPoint Options
When converting native file types that are MS PowerPoint Documents into PDFs using the Relativity PDF Engine, the
following options can be configure in the PDF Profile:
l Show Speaker Notes—if the native MS PowerPoint document has track speaker notes, this option will include
those speaker notes in the resulting PDF.
l Show Presentation Comments—if the native MS PowerPoint document has Presentation Comments, this
option will include those comments in the resulting PDF.
Placeholder Options
Select Never, Always, or For Errors/Unsupported File Types when assigning a PDF placeholder for a document
during PDF Rendering.
Note: The PDF profile supports the following options available in the selected Imaging Profile: Email files, Word
files, PowerPoint files and Excel files. Options selected on the Imaging profiled related to HTML files are not
supported when by the PDF profile.
Then, you can select it from the Native Imaging Profile drop-down menu.
Branding options
Note: If you are creating PDFs to open in the Viewer, it is important to note that the Viewer displays PDF text by
mapping the character codes to Unicode in most cases. To check whether PDF text has been properly encoded and
will display correctly in the Viewer, copy the text in the original PDF file and paste it into another application like
Microsoft Word or Notepad. If the pasted text does not display correctly, the PDF is not properly encoded. If the pas-
ted text displays correctly in another application but not in the Viewer, contact Support for assistance.
1. From the mass operations bar on the document list, select either Checked items or All items in the current
returned set.
2. Select PDF in the mass operations drop-down menu. The PDF options window displays.
Notes:
l The settings available depend on the file type selected. Natives, original images, or produced images.
For example, production options are available if you select Produced Images. Likewise, if you are
going to save all your documents in a single PDF, then there are no options on how to name the indi-
vidual PDF.
l When saving your PDF as a zip or PDF portfolio you can choose to name your individual PDFs using
just the control number or the control number plus a field.
l You also have the option to decide whether to include a numbering prefix on the file name. In the past
that prefix was always added.
Action
l Download—download your PDFs. When selecting multiple documents, a toggle option is available to
"Combine PDFs by Document Family." Once selected and downloaded, users will receive a single com-
bined PDF for documents that share the same ID for the chosen relational field.
Note: This option is available only when you select Individual PDFs in a Zip under the PDF Option
setting.
l Store—creates a PDF from the native or imaged version of the documents. Those PDFs will be stored in
Relativity and can be reviewed using Relativity's PDF Viewer.
l Brand—sequentially numbers documents with a structured Document ID and stamps the Document ID
on each page of a PDF. Only profiles that have branding options set can be leveraged for this action.
Note: Selecting the Brand option when using a PDF profile that has Level Numbering configured
could conflict with the control number.
l Count—calculates and updates the PDF Page Count field when document page counts need to be
updated in the database. This only works for counting rendered PDF documents.
l Delete—deletes the stored PDFs associated with the selected natives.
Note: If you import PDF Images and the PDF Page Count is not set, you cannot brand the documents.
You must run the Count action beforehand to make sure the field is populated.
File Types
l Natives—saves the native of the documents.
l Original Images—saves the imaged versions of the documents.
l Produced Images—saves the produced versions of the documents.
l Stored PDF—saves the PDFs that are currently stored in Relativity and can be reviewed using Relativ-
ity's PDF Viewer. Single file Stored PDFs will be downloaded as a Zip file.
PDF Options
l Individual PDFs In A Zip—saves resulting PDFs as a zipped file.
l Single PDF—creates one PDF with all documents.
Note: When you Mass Save as PDF a group of documents, the documents retain their sort order
based on the order in which they appear within your document list.
Naming Options
This option defines the name of the individual PDFs created when documents are saved as Individual PDFs In
A Zip or PDF Portfolio. The zip file or the portfolio file itself that contains the PDF files is always named result.
[extension].
l Control Number—choose this option to name the PDFs after the control number of the original doc-
ument.
l Control Number And Field—this option appends value of a field to the original control number name.
When using this option, the resulting name of the document is [control number]_[field value].
l Field—choose this option to name the PDFs after a field value.
l Append File Type—appends native, image, or production at the end of the file name based on the type
of documents used to create the PDF.
l Prefix Sequential Number—this option appends a numeric prefix based on the sort order in which they
appear within your document list. For example, 01_FirstDocument.pdf.
Note: If the length of file name is longer than 251 characters, the system will use the first 251 char-
acters.
Production Options
l Include original images for documents that haven’t been produced—if a document has not been
produced, you can check this option to create PDFs from the images associated with that document
instead.
l Modify Production Order—select which produced version of the document to include in the PDF set.
l The save job first looks at the production set at the top of the list. If the document is included in this
production that version is saved. If not, the save job checks if the document is in the next pro-
duction. Only one production per document is saved.
l The list includes only the productions related to the documents selected, those productions are sor-
ted by recent to oldest. For example, if there are 8000 productions in your workspace, but the
selected documents are produced across only 100 productions, the list will show only those 100
productions.
PDF Profile Options
The PDF Profile section displays the selected profile and all the corresponding values set on that profile.
For details, see PDF profile on page 340.
4. Once you have applied all the desired settings, click Download, Store, or Delete, depending on the action you
specified at the top of the layout. The system submits your PDF job. Once completed, the browser automatically
downloads the resulting file. You also receive a confirmation email with a link to your PDFs to download.
Note: Ensure you have a set of password banks uploaded to your workspace.
Documents that have been password encrypted and/or have a .pfx certificate can successfully undergo download
and/or store PDF operations as long as the passwords and certificates in the password bank are correct. Only native
file types that are downloaded or stored are supported.
Select the checkbox option to Decrypt password protected documents. When you select this checkbox, a warning will
appear, providing best practices and cautioning about potential performance issues if those practices are not followed.
Note: Using a PDF profile with the Native Application Engine may result in slow performance. The operation's
speed depends on the size of the password bank (more than 100 entries) and the position of correct passwords
within the bank (if the correct password is the last one). This can lead to slow performance, potentially taking several
hours and possibly timing out.
If the job completes with errors, you have the option to download a .csv file with the list of errors. For example, if
you try to create a PDF for a native file that is password protected, or if you try to create a PDF from images and
a document doesn't have images, those PDFs will not be created and those documents are included in the .csv
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
l From the mass operations bar on the document list, choose whether to convert Checked items or All items in
the current returned set.
l Select Convert in the drop-down menu.
l Complete the fields on the Convert Documents layout.
l Natives
l Yes - converts any natives
l No - doesn't convert natives
l Images
l Yes - converts any images in the documents
l No - doesn't convert images in the documents
l Productions If the selected documents are contained in a production set, the production set(s) appears
here.
l None - this option appears if there are no production sets containing the selected documents.
l Re-convert if previously converted - select this checkbox to convert selected documents, regardless if
they've already been converted. The newly converted documents are stored in the cache.
l Click Run to convert the documents. Once you click Run, you are unable to cancel the convert job.
Note: Converting a large number of documents can deplete the available disk space on the file server.
Note: As long as you have the listed security permissions, you do not need view permissions to the work-
spaces or the production jobs to use Retry Production Job.
4. Click Ok.
Note: After the application is installed, review the workspace permissions and remove the Set Long Text Field Size
permission for the groups that should not have access to the mass operation.
1. Create a decimal field for saving the extracted text size. For more information, see Fields on page 147.
2. From the mass operations bar on the document list, choose whether to select Checked items or All items in
the current returned set.
Note: The set long text size mass operation permits the user to edit documents even if they have read-only
permissions.
3. Select Set long text field size in the mass operations drop-down menu.
The Set LongText Size form displays.
4. Select a source field to calculate long text size. The drop-down menu includes all long text fields you have per-
missions to see.
5. Select a decimal field to store the calculated long text size. The drop-down menu includes all decimal fields you
have permissions to see.
6. Click Run to apply your changes.
Note: The mass operation stores the size of the text, in kilobytes, in the decimal field.
If any of the users can't be invited, they are listed in the dialog. The reasons may include:
l The user you are inviting doesn't have a valid login method. To correct this, assign the user a login
method.
l You don't have edit permissions to the user(s) that you are inviting. Make sure you have edit permissions
to the users.
l
Client is the matter’s associated client. Click to select from all available clients.
Note: If your client list is too large, click Show Filters to quickly narrow the list by any available field cri-
teria. Items in the client list are set by a system view. Therefore, it is possible to only see a subset of
items.
Note: Client domains are targeted for the above use case only and it is important to consider all the limitations
outlined in Client domain limitations and considerations.
Implementing client domains requires an additional license from Relativity ODA LLC. Each client domain license is
unique, and client domains can have different terms encoded on their license keys. The license for a client domain is
unrelated to any other license for Relativity (e.g., number of seats). Client domain licenses are not transferable from
one client to another. To request a new client domain, you must submit a RelativityOne request via the Community site
as detailed in the following knowledge article.
l Permissions - the root object of a client domain is the client object in the administrative workspace. By default,
groups associated with a given client only have permission to perform actions on users, groups, matters, and
workspaces associated with that client, unless a system administrator has given special permission across cli-
ent domain boundaries. Additionally, each client domain has an associated group known as the client admin-
istrator group. By default, members of this group can create administrative objects (users, groups, matters, and
workspaces) associated with the client. This group does not have permission to interact with or view objects of
these types associated with other clients.
l Credentials - many services in RelativityOne, such as HTML5 conversion and RelativityOne Staging Explorer,
utilize custom credentials to access resources on the client domain’s behalf. For example, a credential stored in
RelativityOne is used by the conversion service to access the Relativity file repository in a secure manner.
l Utility Server - each RelativityOne tenant can have a Utility Server, which accesses the file share for each cli-
ent domain. In addition, a dedicated Utility Server may be requested for a client domain within the tenant.
Please note that there is a maximum of 11 client domain utility servers allowed per Relativity instance.>
Notes: We only allow the creation of 10 Client Domain Utility servers. Any client domain created after the first
ten Client Domains are out of the scope for Utility Servers. There is security around the Client Domain's UVM
file servers that limit this from working. Only the first 10 created Client Domains can have a UVM, and then
none thereafter. This is true even if some of the first 10 created do not have a utility server, we still cannot cre-
ate a utility server for the ones past the initial 10.
To request a new client domain, you must submit a RelativityOne request via the Community site by navigating to the
Support tab and then RelativityOne requests (as detailed in the following knowledge article). Please note that the
Client Domain creation process takes 3 business days. If an Utility Server was requested, you will also be contacted
with the following information:
l The system creates a new Everyone - [Client's Name] group and adds that group to the client domain. Only
users whose client field is set to the client domain are included in the client domain everyone group. The system
also removes those users from the default Relativity Everyone group. A system admin can add any users to any
group regardless of client domain status.
Note: The Everyone - [Client's Name] group should not be assigned as the workspace administrator group
for a given workspace that is part of a Client Domain.
l The system creates a unique copy of all resource pools associated with any workspaces under the client
domain.
Note: Permissions assigned to groups override client domain isolation. If a non-client domain group has per-
missions to see a client domain's workspace or users, then those non-client domain users in the non-client
domain group can still access client domain items. Enabling client domains does not change previously con-
figured item level security settings applied to any objects within the client domain.
l The system creates a client domain admin group that permits its members to perform admin operations within
the client domain.
l The Billing statistics - RelativityOne - case rollup and Billing statistics - users reports include columns called Cli-
ent Domain Name and Client Domain Artifact ID. These columns display client name and artifact ID when you
enable client domains for a client.
Note: After enabling client domains, system administrators needing to make group or permission changes
should be extra cautious and thoroughly investigate the potential impact to client domain separation before
implementing any new group/permission changes.
Once client domains functionality is enabled for the client, you must assign a client domain admin.
Note: Client Domain specific views can be used and configured to enable Client Domain admin-
istrators to configure and view their own users more easily. Ensure you have properly reviewed and
tested all relevant permissions before doing so.
Caution: Do not change Client Domain Admin Permissions in any way, unless instructed by the Relativ-
ity Support team. This will allow a user to view other user groups in the instance. If you have changed these
permissions, contact Relativity Customer Support to have the permissions reset to their original con-
figuration.
l If a system admin assigns additional permissions for other Admin objects to a client domain admin (such as,
Queues), the client domain admin may be able to see information for other client domains.
l System Administrators should be aware of the following behavior to prevent unintentionally providing users with
access to data outside their domain: If you add a user who is already a member of a domain admin group to
another group that holds the Relativity Script system permission, the user will gain access to all users and
groups across the entire Relativity instance. Once the user is removed from the new group, access will be
restricted again to users and groups associated with their specific client.
l When importing a Client Domain Admin using the Relativity User Import Application, the application auto-
matically includes the new user in the Everyone group by default. This action can disrupt the Client Domain
security settings in your Relativity instance. To address this issue, follow these steps: remove the user from the
Everyone group and assign them to the client-specific Everyone group. Achieve this by temporarily switching
the user to any client not linked to a domain, and then back to the desired domain client.
l You can grant workspace admins within the client domain permission to edit security settings for groups within
the client domain, but they can't edit permissions on groups outside of the client domain.
l Workspace Admin and Client Domain Admin permissions are not copied from the workspace template when a
new workspace is created. They are taken from the Sys Admin permissions.
The following table provides a breakdown of the default instance permissions for a client domain admin:
l Client Domain Administrators do not have access to the Errors tab, which may impact their workflows.
Note: In 2025, Relativity is deprecating the (Admin) Errors tab in RelativityOne. This change is part of our effort to
transform the error-handling experience by making it easier to address job-specific errors as they occur at their
source within your workspaces. Starting in April 2025, we'll hide the Errors tab from all production instances in a
phased rollout. In July 2025, we'll permanently remove it from RelativityOne and disable the ability to read errors
through the API. For more details, see Errors tab deprecation.
l UVM (Utility Virtual Machine) is not available for RelativityOne Government clients.
l Multi-tiered client domains - an enabled Client Domain cannot have their own sub/child client domains.
l Cost Explorer isn’t accessible within a Client Domain.
l Unique logos or URLs per client domain.
l Customer-managed keys (CMK)
l Self-provisioning / enabling of client domains requires a request to Relativity Customer Support.
The following items are features and operations that are have limitations in client domains or can only be used or
performed by top-level system admins or a Relativity staff resource.
Note: If a feature, capability, or operation isn't listed, then there are no limitations on them when using client
domains. For example, Relativity Legal Hold isn't listed and has full functionality when operating client domains.
Client
System
Item Limitation domain
admin
admin
l ARM
l Workspaces on page 709
l Adding or removing users from a client domain on page 630
l Adding or removing groups from a client domain on page 188
l Adding or removing matters from a client domain on page 359
1. Defining a production or saved search that contains the documents you want to OCR. See Creating a saved
search in the Searching guide or Creating and editing a production set.
Notes: All documents, including native files, must be imaged before using OCR.
2. Creating an OCR profile. See Creating and editing an OCR profile below.
3. Creating an OCR set that references your OCR profile. See Creating and editing an OCR set on page 371.
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.
Note: See OCR on redacted production documents for information on running OCR on redacted production
documents.
Notes:
Special considerations when using Arabic as a recognition language:
l When Arabic is selected as a recognition language in the OCR profile, English and non-English Latin-alpha-
bet languages are also recognized by default by the OCR engine. Thus, it is not necessary to include them as
additional languages in the OCR profile. In these cases, the recognition of text on images that contain Arabic
and Non-English languages that also use the Latin alphabet may be less accurate. Accents and other char-
acters not used in English may be misidentified.
l Running OCR with an OCR profile that combines Arabic with other languages is not supported. This con-
figuration may lead to OCR Image Errors. As a result, you may not be able to recognize any text from the
image, regardless of whether there was an actual recognizable text in the image.
l Name - the name of the OCR set. The following characters are not allowed: <,>,:,",/,\,|,?,*
l Preprocess Images - enhances the images to get rid of distortions before OCRing. If you set this to Yes, pre-
processing occurs before the OCR engine attempts to recognize characters. This improves the accuracy of the
results while significantly slowing down job completion. Setting preprocess images to Yes also arranges for any
or all of the following sub-processes:
l To improve visibility, resolution enhancement increases pixel density to 1.5 to 2 times of that of the ori-
ginal image.
l Text line straightening removes the distortion that occurs when capturing curved book pages.
l Removing parallax distortion assists in situations in which the camera is not perpendicular to the page
and the image is flawed as a result; for best results, the image should contain at least six lines of justified
text.
l Deskewing corrects documents that became slanted during scanning.
l Auto-Rotate Images - makes the OCR engine detect page positioning, and then reposition the page accord-
ingly. This can potentially impact the accuracy of OCR results. The rotated image is not saved back to Relativity
in rotated position.
Note: The auto-rotate images function requires the preprocess images option to be selected for it to take
effect, even if the auto-rotate setting is set to "true." The OCR engine will only rotate the image if both pre-
process and auto-rotate options are enabled.
l
Languages - the language(s) you want the OCR engine to recognize while running the job. Click to
choose from a list of languages. If the saved search or production you plan to use as your document set con-
tains multiple languages, you may want to select more than one from this list. See the Supported languages
matrix on the Documentation site.
Note: If the saved search or production you use contains multiple languages and you only select one lan-
guage from the list, the OCR uses the individual characters of the selected language to OCR all the text.
l Accuracy - determines the desired accuracy of your OCR results and the speed with which you want the job
completed. This drop-down menu contains three options:
l High (Slowest Speed) - runs the OCR job with the highest accuracy and the slowest speed.
l Medium (Average Speed) - runs the OCR job with medium accuracy and average speed.
Note: If an OCR job is not extracting text from redactions as expected and is instead displaying a blank space
where text should be, change the Accuracy field from High to Low. In addition, if there are no images in the
set that need rotating, turn off the Auto-Rotate Images option. Making these adjustments should improve data
extraction.
l On Partial Error - determines the behavior when the OCR engine encounters an error on an image:
l Leave Empty - records no results if an error is encountered in a document; even images without errors
are excluded from being written. For example, if one document contains five images and one of the
images errors, no results are written for that document.
l Write Partial Results - records all successfully OCRed text while excluding text from errored images.
With this option you can see potentially relevant text that would not be visible if you chose to leave the res-
ults of documents containing errored images empty. This option runs the risk of excluding potentially rel-
evant text.
l Image Timeout (Seconds) - determines the maximum number of seconds per image before the OCR engine
times out. If the job doesn't complete in this amount of time, it errors on that image. The default value is 60
seconds.
If you'd like to further distinguish the profile, click the Other tab and enter information in the Keywords and/or Notes
fields.
l Status - view where the OCR set is in the process of running. When you save the set, this field shows a value of
Staging until you click the Run button in the OCR Set Console. The following statuses occur after you click Run
in the console:
l Pending - awaiting pickup by the OCR Job Manager Agent
l Building
l Waiting - awaiting work by an OCR Job Worker Agent
l In progress - OCR Job Worker Agents are recognizing images
l Assembling text - The final remaining Documents are getting their text assembled
l Finalizing
l Completed (if no errors occurred)
l If errors occurs or the job is canceled for any reason, the following statuses are possible:
l Failure
l Completed with errors (can be retried)
l Stopping
l Stopped
l Image Completion - view the count of images completed in the OCR set, the number of images with errors,
and the number of images left to be OCRed. Any errors appear in red.
l Document Completion - view the count of documents completed in the OCR set, the number of documents
with errors, and the number of documents left to have text assembled. Once documents are completed, it is pos-
sible to view their OCR'd text. Any errors appear in red.
lLast Run Error - view the last job error that occurred in the running of the OCR set.
OCR settings
l OCR Profile - select the OCR Profile that contains the parameters you want to run when you execute the OCR
Set.
Click to bring up the OCR Profile Picker on OCR Set view, which lists Profiles that have already been cre-
ated in the OCR Profiles tab.
l Destination Field - specifies the field where you want the OCR text to reside after you run the OCR. This
includes Data Grid-enabled long text fields and the extracted text field.
l Saved Search - if you're OCRing documents using a saved search, select the saved search containing the
appropriate set of documents you plan to OCR.
Choosing a saved search only OCRs the original image. If a document on the selected saved search does not
have an associated image, that document won't be OCRed. Likewise, the OCR engine will not account for
redactions added to the image unless there are redactions on the image itself.
l Production - if you're OCRing documents using a production set, select the production set containing the doc-
uments you plan to OCR.
Click to open the Production Picker on OCR Set view, which displays all production sets with a status of
Produced that you have access to. The engine OCRs all burned-in redactions, branding, headers and footers,
and text. All documents with images in the production are OCRed, not only those with redactions. This includes
placeholders.
l Only OCR Production Documents Containing Redactions - you can OCR only produced documents with
redactions. You can set this to Yes only if you selected a production set in the production field for the OCR Docu-
ment Set. However, this setting doesn't check the selected production to see if there are images with redactions
before running the OCR set. By default, this is set to No.
Note: The OCR engine does not support OCRing content that represents handwritten text.
Object Permission
OCR Set View
OCR Profile View
Production View
Saved Search View
OCR Set Tab View
Note: These permissions are strictly for running the Set, i.e. if the OCR Set is already set up. A user needs the Add
permissions on OCR Set and OCR Profile to create a new one.
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
When you save an OCR set, the OCR Set console appears that you use to run the OCR job.
l OCR Documents - starts the OCR job. This processes all images in the selected data source or production.
If a user stops the job, it completes with errors, or it fails. Click OCR Documents to start the job again. If there
are documents in the Document (OCR Results) section of the OCR Set Layout form, these aren't immediately
cleared when the OCR Documents button is clicked on the console. These are only cleared when the job goes
into processing, which is reflected in the Status when you click the Refresh Page link.
Note: Only existing images are OCRed when you click OCR Documents. Images that are currently being
loaded will NOT be OCRed if those images are added after you click OCR Documents. Changes made to an
OCR profile that's referenced by an OCR set aren't reflected until you click OCR Documents on that set.
l Stop OCR - terminates the running OCR job. This button enables after you click OCR Documents. When you
stop a job, the text that was already OCRed is not saved, and you can't resume the job from the point it stopped.
You have to click OCR Documents to begin the job over again.
l Retry Errors - attempts to re-run a job with errors.
Note: If an OCR set is in a status of Completed with errors and the data source is modified (i.e. the OCR
set is updated from a Saved Search to a Production Set), the OCR set will reset to a status of Ready to run
and cannot be retried.
Retry is only possible when an OCR set is in Completed with errors. Retrying an OCR set attempts to run
those images or documents in the OCR set that previously resulted in errors. Only errored images or doc-
uments are processed when the system tries to resolve errors.
l Refresh Page - updates the Status, Image Completion, and Document Completion fields while the set is run-
ning. Clicking this button reloads the page and may reflect different values in those fields depending on what
happened during the OCR job.
Once the OCR job completes, the Document (OCR Results) section of the OCR Set Layout form displays all
documents successfully OCRed. The fields in this view are Control Number and File Icon.
In addition, it's possible to see Image OCR Errors or Document OCR Text Import Errors in the same tabbed display as
Document (OCR Results).
These errors can be exported.
Note: Only the first 1000 image errors and first 1000 document errors are shown. These errors cannot be filtered.
l Document Artifact ID
l Document Identifier
l Page Number
l Message
Document OCR Text Import Errors shows
l Document Artifact ID
l Document Identifier
l Message
1. Create an OCR profile with your preferred settings. You must have an OCR profile before you can save an OCR
Set.
2. Create a long text field to hold your OCR results. You can't OCR directly into the Extracted Text field.
3. Create an OCR Set.
4. Point the OCR Set to the completed Production. If you only want to OCR redacted documents for the pro-
duction, select Yes next to Only OCR Production Documents Containing Redactions.
5. Click Save on the OCR Set.
6. On the OCR console, click OCR Documents to start the job.
7. When the OCR job is complete, the text becomes ready to export.
Note: Relativity does not support Pivot On or Group By for Long Text fields due to the performance impact.
However, you can create a Pivot on any Relativity field that is enabled for Group By or Pivot On even if that field
doesn't appear in the current view.
Note: You can't create or edit pivot profiles unless you have the required permissions.
Note: Only fields that have been Pivot-enabled will be available to select in this form.
l Name—the name of the profile. You may want the name to reflect fields on which you pivoted.
l Object Type—click Select and choose the object type you would like this profile to appear under.
l Display—select which of the three possible Pivot display types you want to be used to represent
your profile in the item list:
l Pivot Grid—designates the grid as part of the profile display.
l Pivot Chart—designates the chart as part of the profile display.
l Group By—click Select and choose the field you want to act as your Group By value in your profile. Only
fields that are Pivot-enabled on the Field page are available in this list.
Note: We do not recommend selecting long text fields with the Group By field due to the performance
impact. For more information, see Pivot.
l Group By Date—choose a method for providing the date values for the Group By field:
l Date—displays the date with day, month, and year.
l Year—displays only a year value.
l YearMonth—displays the year and month values.
l Week—displays week values.
l TwoWeeks—displays every two weeks values.
l Pivot On—click Select and choose the Pivot On field in this profile. Only fields that are Pivot-enabled on
the Field page are available in this list.
Note: We do not recommend selecting long text fields with the Group By field due to the performance
impact. For more information, see Pivot.
l Pivot On Date—provides the same dates for the Pivot On field as found above on Group By, with the
addition of the following:
l Month—displays only a month value. This option is only available in Pivot On if your Group By
field is also a date.
l Page Size—determines the number of sets per page in a pivot chart or graph. Depending on the display
specifications you set, you may want to enter a low value.
4. Complete the fields on the Chart Options section.
l Chart Type—determines what kind of chart is used to represent the profile in the item list:
l Show Grand Total—toggles the display of grand total in the pivot chart. This value can help add
context, but may throw off the scale of the pivot chart and reduce readability.
l Show Legend—toggles the display of the Pivot Chart legend. This information can often be intu-
ited from looking at the chart. If not, it can be added.
l Show Blank Values—toggles the display of blank values in the chart.
l Show Labels—toggles the value count labels on pivot charts.
l Rotate Labels—rotates the group by labels at a 45 degree angle. This can help readability in
fields with many values.
l Stagger Labels—another option to improve readability of group by values. Stagger labels varies
the horizontal position of the labels to improve readability.
l Show Sub-Chart—toggles the display of sub-chart in bar chart, stacked bar chart, and line chart.
5. Click Save.
The Pivot menu displays options to run reports on pivot-enabled fields in views and saved searches.
1. Click Add Widget, and then select Pivot from the drop-down menu.
2. Select the desired chart type by clicking on its thumbnail.
3. Perform one of the following to define settings for your Pivot widget:
Note: If you would like to select a Group by (X) or Pivot On (Y) field that does not have the Enable By option
enabled, click on either Group by (X) or Pivot On (Y), hover your cursor over desired field in the list, and
click the Enable icon on the right side of the row. Click Yes to allow the field to be used in pivots and select
that option for either Group by (X) or Pivot On (Y).
a. Select an existing Pivot profile from the Template drop-down menu. The Group By (X) and Pivot On (Y)
fields populate with the settings defined by that Pivot profile.
Note: If Every Week or Every Two Weeks is selected, the results are displayed from Sunday
through Saturday.
Note: Click the value name in the legend to toggle it on and off.
l Edit Pivot - Displays the Pivot Settings window in which you can edit the Pivot settings.
l Save Pivot Profile - Displays the Pivot Profile window in which you can replace or create a new profile.
l To replace the selected Pivot profile with the current settings, leave the default name in the Profile Name
field and select Replace existing profile.
l To create a new Pivot profile with the current settings, enter a new name in the Profile Name field and
select Create new profile.
l Pause Pivot - Select to freeze the content in this pivot so that the information displayed is not affected by
searching or filtering the document list. When a pivot is frozen, a paused message displays in the widget to help
you track its status. You can unfreeze a pivot by clicking the Resume Pivot button in the widget. Once a widget
l Bar Chart
l Pie Chart (available when you select only a Group By (X) value)
l Stacked Bar Chart (available when you select both a Group By (X) and Pivot On (Y) value)
l Line Chart
l Table
24.2.3.3 Export
From the Export section on the Pivot options pane, you can export the Pivot to one of the following formats:
l Export PNG - exports the chart as a PNG image file and automatically downloads it locally.
l Export XLSX - exports the chart as a Microsoft Excel Document where you can modify and configure the chart
using Excel's built in chart functionality.
24.2.3.4 Options
From the Options section on the Pivot options pane, select the checkboxes to display blank values, show grand total,
display the chart horizontally or vertically (for bar and stacked bar charts), choose whether to display the legend.
l Export PNG - exports the widget as a PNG image file and automatically downloads it locally.
l Export XLSX - exports the widget as a Microsoft Excel Document where you can modify and configure the
chart using Excel's built in chart functionality
Note: Exporting to Excel functionality does not require Microsoft Excel to be installed (except for viewing of
the exported file).
To export a widget:
1. Click the Toggle widget menu icon at the top right of the relevant widget to display the options pane.
2. Select Export PNG or Export XLSX.
The generated filed is automatically downloaded locally to your computer.
3. Open the file on your computer to view the result.
4. If you exported the widget to Microsoft Excel, you may use Excel's built in chart functionality to edit the chart and
its data as needed.
Note: Please note that you cannot modify cluster visualization widget data in Excel.
Note: If you want to export all the widgets on your dashboard to an Excel file, refer to Exporting a dashboard in the
Admin Guide.
To clear the filter, click Clear All Conditions in the Search Panel.
When a filter is applied, the hide filter icon appears in the heading of the column.
System admins can control which highlight sets different users see when working within a document. See Workspace
security on page 573 Workspace security in the Admin guide.
Persistent highlight sets are independent of markup sets. See Markup sets on page 315 Markup sets in the Admin
guide.
Click the next to a persistent highlight set to expand it and show the list of terms from that set found in the
document. By default, all persistent highlight sets are enabled in the Viewer, and terms found in a document are
selected in the Persistent Highlight Sets pane and highlighted in the document. Click a persistent highlight set's name
or the icon to hide all term highlights from the set in the Viewer. When a persistent highlight set's icon is and the
terms appear partially transparent in the Persistent Highlight Sets pane, the term highlights for the set are hidden in
the Viewer.
Note: The Show terms with zero hits option does not support highlight fields that are based on search term reports.
While the persistent highlight set displays in the Persistent Highlight Sets pane, the highlight field terms do not dis-
play unless there is at least one search hit regardless of whether Show terms with zero hits option is enabled or dis-
abled.
You can use the Next/Previous icons to cycle through the hits for either the persistent highlight set or the highlighted
term. Regardless of where you are in a document, when you click the Next icon for the first time, you will be taken to
the first highlight in the document for that persistent highlight set or term. Even if you have moved past it while
browsing the document.
Clicking the Next/Previous icons also emphasizes the actively navigated highlight with an orange glow to help you
track which one is active.
The number of terms and hits is listed to the left of the persistent highlight set's name. It is possible to have many
highlight sets enabled but no highlights appear in a document.
Selections made in the Persistent Highlight Sets pane persist throughout a user's session in Relativity. This includes
any of the following changes related to the Persistent Highlight Sets pane in the Viewer:
To perform either a dtSearch or Keyword search in the Your recent searches section:
1. Optionally, click on the Persistent Highlighting icon to expand the Persistent Highlight Sets pane.
2. Click the + Add Term button.
3. Enter the desired dtSearch or Keyword search terms in the textbox.
4. Click the Confirm icon or press Enter on your keyboard.
The Your recent searches section updates with the number of matches and any matches are highlighted in yel-
low in the current document.
Optionally, you can select a search in the Your recent searches section and use the Next/Previous icons to cycle
through the matches. Regardless of where you are in a document, when you click the Next icon for the first time,
you will be taken to the first highlight in the document for that persistent highlight set or term. Even if you have moved
past it while browsing the document.
To navigate between terms highlighted on a document in the Viewer, use the Go to Previous Highlight and Go
Note: Beginning in Relativity 11.3.1, the auto-contrast feature has been added to color-coding persistent highlights.
This feature automatically determines the text color based off the background color you select to ensure readability
no matter which colors are selected. For example, if the background color is closer to black, the text will
automatically be white or if the background color is closer to white, the text will automatically be black.
Note: The opacity level of the highlights for proximity searching and inactive terms can be adjusted by editing the
value of the ViewerHighlightStyleDefault instance setting.
l Any changes made to a persistent highlight set tree in the panel when the Viewer is undocked, such as terms
selected or unselected, will display when the Viewer is docked again.
l A synced standalone Viewer will not display changes made to a persistent highlight set, such as terms selected
or unselected, in the pane of the main Viewer. However, Persistent Highlight Sets pane settings remain the
same in the standalone Viewer as the reviewer goes from doc-to-doc.
l The Persistent Highlight Sets pane maintains its current state when you swap Viewer panes.
l The Persistent Highlight Sets pane in the Extracted Text Viewer and Native Viewer are independent of each
other. A change made to the pane in the Extracted Text Viewer is not automatically reflected when the reviewer
switches to the Native Viewer and back.
l Advanced persistent highlighting, available when using a search term report as a highlight field source, is only
available in the Native and Extracted Text Viewer. See Using the highlight fields source on page 403.
See the Viewer documentation in the Admin Guide.
l Privilege Terms
l Specific Issue Terms, unique terms
You can visually group related terms by assigning a different highlight color to the terms in each highlight set.
When multiple highlight sets include the same term the colors used in each set will mix together. For example, if a
highlight set includes the term "apple" highlighted in blue and another highlight set includes the term "apple"
highlighted in red, the highlight color will combine and display as purple in the Viewer. This only applies if both
highlight sets are active for the same term.
Clicking on the light bulb icon for a persistent highlight set enables or disables highlighting for the entire set. The
icon indicates a persistent highlight set is enabled in the Persistent Highlight Sets pane. The icon indicates a
persistent highlight set is disabled in the Persistent Highlight Sets pane. When disabling a persistent highlight set in
the Viewer, terms included in the set aren't highlighted in documents until the set is enabled again.
Clicking a check box activates or deactivates highlighting for an individual term.
Security is another way to control persistent highlight sets. System admins can use object-level security to display only
the persistent highlights sets necessary for users to complete their reviews. Limiting the visibility of persistent highlight
sets also provides a cleaner interface for reviewers. See Relativity object security on page 604 for more information.
Note: 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 on page 403.
4. Click Save.
Note: Verify that reviewers are not actively reviewing documents when creating persistent highlight sets. Creating
persistent highlight sets while reviewers are actively reviewing documents can cause errors.
25.4.1 Fields
Persistent highlight sets include the following fields.
l Name- the descriptive name under which you want this set to appear in the Viewer and item list.
l Order -the order in which you want this set to appear.
l Source - determines the area the set draws from when designating characters to be highlighted and displayed
in the Viewer. There are two options:
Note: If your search terms report is run against a dtSearch index with a customized alphabet file, the hits on
the STR may not match the highlights rendered in the Viewer. Depending on how the alphabet file has been
customized, you may see fewer highlight hits rendered in the Review Interface.
l Terms - enter terms you wish to highlight and select the color code to distinguish them in the Viewer. See Enter-
ing highlight terms below.
Highlights are rendered at full opacity (using the original highlight color) when they are active. When they are not
active, they will be rendered in a lighter shade of the original highlight color.
Note: The opacity level of the highlights can be adjusted by editing the value of the ViewerHighlightStyleDefault
instance setting.
Note: Default has different implications for text and background. The default background color is white and the
default text color is black.
l Enter a term that you want highlighted and press Enter. You can enter multiple terms but each one must be on
a separate line.
l Enter terms for persistent highlighting exactly as they appear in the document. Don't use quotation marks and
connectors.
Note: Quotation marks are not compatible with persistent highlighting with terms as a source, which auto-
matically searches for an exact phrase. Quotation marks are compatible when using highlight fields as a
source however. Using highlight fields as a source can result in slower document loading speeds.
l Keep lists simple. Do not use punctuation, special characters, or operators. Do not use dtSearch syntax when
entering a list of terms as the source for the set. You may use dtSearch index terms in a search terms report,
then use Fields as the Persistent Highlight Source instead to support highlights for dtSearch syntax.
l AND or OR operators are not used in keyword searching. If used, Relativity looks for the exact phrase
including AND or OR. For example, you entered these search terms: Apple AND Banana. Relativity high-
lights the entire phrase apple and banana in the document. Separate occurrences of apple, and occur-
rences of banana, are not highlighted.
l Persistent highlight set terms do support wildcards. You can view highlighted terms that contain an *
(asterisk) character, including a wildcard in the middle of a term. For example:
l term* matches and highlights any word that starts with term with zero or more following characters.
l *term matches and highlights any word that ends with term with zero or more preceding char-
acters.
l *term* matches and highlights any word that has term in it with zero or more preceding or following
characters.
Note: Persistent highlights generated by a search terms report don't automatically update after you load new data
into a workspace. To incorporate the text from new documents, perform either a full or incremental build on the
dtSearch Index, then a full or incremental build on the search terms report.
To select a Highlight Field, check the field’s box, click right arrow to move it the right section. Once all of the desired
fields have been selected, click Apply. The field appears on the layout.
Note: We recommend selecting a search terms report or the Domains field as your highlight fields source.
When using a Search Terms Report as the highlight fields source, the number of terms that Relativity searches for will
vary among different records. Relativity only looks for the terms listed in the Search Terms Report for that document.
l Persistent highlight does understand proximity searching. If you enter the phrase Relativity w/5 software
as a search term, the search term report uses a dtSearch to find and tag all documents that meet the cri-
teria. When viewed in the Viewer, the persistent highlighting functions as a dtSearch.
l Persistent highlights does understand the stemming character (~). If you enter the term apply~ as a
search term, the search term report finds and tags all documents with the word apply, or any document
that stems from apply; including applied, applies, application, and so on. When looking at the document
in the Viewer, the persistent highlight functions as a dtSearch. See Search terms reports on page 551 for
information on supported syntax.
l Any operator in quotes will be treated as literal by the Viewer search. For example, stemming “~” and wild-
card “*” operators. However, dtSearch will treat stemming and wild card operators in quotes not as literal,
but as the operator itself. For example, "run~” in the Viewer will find the exact phrase “run~” and "run~” in
dtSearch will return hits for run, runner, running, etc.
l Do not use "AND" or "OR" connectors. Persistent highlighting looks for the exact phrase, trade and complete,
instead of the word, trade, and the word, complete.
l Use the dtSearch Dictionary to identify variations of a term instead of using wildcards.
l Identify which terms should be in the highlight set and which terms are not necessary.
l You may want to avoid highlighting terms with high word counts.
Note: To highlight terms using objects, create a fixed-length text field for your object called Highlight Colors. You
can enter color-coding in this field using the format: [highlight color];[text color].
l Proximity searching logic can be used with Highlight Fields. If you enter the phrase "Relativity w/5 soft-
ware" as a search term, the search term report uses a dtSearch to find and tag all documents that meet
the criteria. When viewed in the Viewer, the persistent highlighting functions as a dtSearch. See Search
terms reports on page 551 for information.
l Stemming, including the stemming character (~), can also be used with Highlight Fields. If you enter the
term "apply~" as a search term, the search term report finds and tags all documents with the word apply,
or any document that stems from apply; including applied, applies, application, and so on. When looking
at the document in the Viewer, the persistent highlight functions as a dtSearch. See Search terms reports
on page 551 for information.
l In Search Terms Reports, you can the Dictionary Search function to identify search terms using stemming or
fuzziness. Copy the list of terms returned in this search. Paste them in the Add Terms box on the Search Terms
Report form. Doing this enhances your search term list, while avoiding errors caused by special characters.
l Use the dtSearch Dictionary to identify variations of a term instead of using wildcards.
l Identify which terms should be in the highlight set and which terms are not necessary.
l You may want to avoid highlighting terms with high word counts.
Save as PDF
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 Single Save as PDF.
Mass PDF
Mass PDF is a mass operation you can run from the mass operations bar in the case workspace interface. With Mass
PDF you can save a group of documents and customize the way the documents render when you save or print them.
After you download the .zip file of the PDFs, you can then print the group of PDFs to your designated printing location.
For more information, see Mass Save as PDF.
1. Upgrade to the latest Relativity product update - Upgrading to the latest Relativity update automatically
upgrades production to the latest version.
2. Upgrade production only - Download the newly released RAP file from the Relativity Community and import it
into the Application Library.
1. Navigate to Tabs.
2. Select New Tab.
3. Enter Production Information as the name for the tab.
4. Select Object as the tab type.
Note: The name of a production can be changed at any point in the production process.
5. Add or edit the fields in the following sections as necessary. Required fields are orange.
l Basic Settings below
l Numbering on page 416
l Branding on page 423
l Sorting on page 425
l Post Production on page 426
l Other on page 427
6. Save the additions or updates.
Note: If you imported a production, the page numbering is set by the imported Opticon file. Any markup set
selection, branding, or other settings on the Production Set form are not applied to the imported production.
The images produce exactly as they were imported.
l Scale Branding Font for Viewer- (required) scales up the branding text size to be consistent with Relativity
7.5 behavior for optimal viewing of images in the Viewer when set to Yes. Set this field to No to use the default
font scaling when printing images. This field is read-only after you run a production set.
l Branding Font - (required) the font type that will be use on the branded text.
l Branding Font Size- (required) the font size for branding added to a page. The font type is Arial.
l Placeholder Image Format - (required) brands the Placeholder image as the file type selected. This field is set
to TIFF by default, but users have the option to brand placeholder images as JPEG files too.
Note: Click on the tool tip icon next to Basic Settings for more information on the image file types (see image
below).
27.5.4 Numbering
On the Production Set form, you can define multiple options that control how numbering is applied to images in your
production.
Relativity provides the following numbering types for productions:
Note: Continue from Previous will not work for productions using original image numbering, existing pro-
duction numbering, or document field numbering.
Relativity automatically populates the Start number field with the value that displays for the Next doc number.
l Number of digits for document numbering - (required) determines how many digits the Bates number con-
tains. The range of available values is between 1 and 10. By default, this option is set to 7 characters.
l Attachment relational field - selects a relational field indicating a family group such as group identifier.
l Preview - displays sample text illustrating how the Bates number appears in the images.
Note: Relativity does not support the combined length of the Prefix and Suffix exceeding 255 characters when
using Page level numbering.
Note: Continue from Previous will not work for productions using original image numbering, existing pro-
duction numbering, or document field numbering.
Relativity automatically populates the Start number field with the value that displays for the Next doc number.
l Number of digits for document numbering - (required) determines how many digits the document number
contains. The range of available values is between 1 and 10. By default, this option is set to 7 characters.
l Include page numbers - (required) adds a unique page number after the document number on each page in a
document, when it is set to Yes. By default, this option is set to No.
Note: If you export a production with document level numbering as single-page TIFF, and it does not include
page numbering, Relativity automatically adds page numbers to identify each page uniquely.
Note: The combined length of the Prefix and Suffix cannot exceed 255 characters when using Document level num-
bering.
l Attachment relational field - selects a relational field indicating a family group such as group identifier.
The following table provides several original image numbering scenarios:
Notes:
l When creating a production set with Existing production numbering, you cannot add documents not con-
tained in the existing set, change page counts, or change whether or not a document previously produced as
native only is produced with a placeholder. You can, however, replace a document produced as a image with
a placeholder as long as it’s a single page document.
l When you choose a production set with more documents than the existing set, Relativity generates a warning
to inform you that it auto-removed the extra documents. If the new production set has a subset of documents
contain in the existing set, the new production set will generate without any warnings.
The following required fields appear when you select the Existing production numbering choice:
l Production Set - (required) Select the production set containing the numbers you'd like to use for the set you're
creating. Only completed production sets are available to select from this drop-down list.
l Merge Existing Set - (required) When you merge a new production with an existing production, the new pro-
duction images replace the images in the previously existing production. The new production still exists for
export. Relativity updates the Has Redaction field in the Production Information record in cases where redac-
tions were added or removed. From the viewer, if you compare the existing production and the new production,
Note: If you have an existing production set with document level numbering, no page-level markers, and the
existing production is migrated into the environment, you cannot merge the productions together with existing
production numbering.
If one production references an already produced production in the Production Set field, you cannot delete the
referenced production. You can resolve the error by referencing an existing production or modifying the parameters of
the production to eliminate the reference to the deleted production.
l There are any documents in the production set you're creating that weren't included in the existing production
set. You must remove these documents from the new production in order to run it.
l The page counts of the documents in the production set you're creating differs from the page counts in the exist-
ing production set.
l If documents in a production set are also in the production restriction for that production, you must remove the
documents from either the production set or the production restriction.
l You attempt to perform any action on a production set while it is merging with another.
Document field numbering
Select the Document field numbering choice if you'd like to use any fixed-length text field on the Document object
for your numbering. Reflective fields are not available for this numbering option.
You may want to select this option if, for example, if you import a set of documents into Relativity and want to maintain
the original numbering of the documents. For example, you could choose control number as the field and produce
documents using the control number as the bates field.
l Numbering Field - (required) select the field you'd like to use for numbering from this drop-down list. Only
fixed-length text fields are available to select from this drop-down list.
Note: The content of the numbering field, prefix, and suffix cannot exceed 255 characters.
l Include page numbers - (required) adds a unique page number after the document number on each page in a
document, when it is set to Yes. By default, this option is set to No.
Note: If you export a production with document level numbering as single-page TIFF, and it does not include
page numbering, Relativity automatically adds page numbers to identify each page uniquely.
l Document Page Separator - (required) displays when you select the Include page number option. The
following separators are available:
l _ (underscore, selected by default)
l - (hyphen)
l . (period)
l Number of digits for page numbering - (required) determines how many digits the page number con-
tains. The range of available values is between 1 and 6. By default, this option is set to 4 characters.
l Start numbering on second page - (required) determines where the document level numbering
begins.
27.5.5 Branding
In the Branding section of the production set form, you can set branding options for headers and footers. You can
position headers and footers to the left, center, and right on the images in your production.
Note: If you experience slowness viewing this page, reduce the instance setting ChoiceLimitForUI until the drop-
downs become popup pickers. Changing this instance setting affects all workspaces in an environment.
Select a Type for each header or footer position where you want information branded in the image.
The following Types are available:
l Production Bates Number - displays the Bates number associated with each document page.
l Production Number - displays the document number associated with each page. (Available for Document
level numbering and Original image numbering only)
l Field - uses the value in the selected document field for branding on each image created for a document.
Note: Relativity restricts the following field types from branding for document images in a production: user,
multiple object, and reflective field types.
l Free Text - uses any combination of text, tokens, and carriage returns that you define. However, Relativity
doesn't support multi-reflected, multi-object, relational, file, user, and system fields for branding. You can use
carriage returns to position the header or the footer closer to the top and bottom margins respectively. Use
tokens to include field data as follows:
Note: If you enter a field ID that represents a field that doesn't exist or is not a document field you cannot pro-
duce the production.
In the above example, SSHACKLET_0000112 is the Document ID, 0 is the page ID, and 5b419b77-
abe4-4ed6-a68a-197f99390895 is the hash value.
l Document Identifier + Page Number - uses the document identifier with the page number appended to it.
This option sets the first page number to 1 even when the document contains only a single page. The following
pages are numbered incrementally. In addition, the page number is padded with up to four digits as illustrated
below.
Note: Depending on the settings for the header and footer, Relativity prevents the image from being cut off by
adding approximately five extra pixels to its edges.
l Advanced Formatting - uses any 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
Beginning in January 2019, branding text wraps by default if the content of two adjacent footers or headers are likely to
overlap with each other. If you copy a production made prior January 2019, the branding on the new production may
look different than the original production, especially if the original production had additional spacing or new lines to
prevent the stamps from overlapping. To keep text from wrapping by default across your entire Relativity instance,
contact Support.
27.5.6 Sorting
In Sorting, you can select a field that determines how your production is sorted. Note that you can sort a production set
by more than one field at a time. You can also use a descending or ascending sort order. By default, the sort order is
Artifact ID, which is the load order of the documents. When you perform a sort, family groups are not kept together.
The sorting applies to all data sources added to the production set. Sorting is only applicable when
Production Numbering is set to the following:
Note: If you experience slowness viewing this page, reduce the instance setting ChoiceLimitForUI until the drop-
downs become popup pickers. Changing this instance setting affects all workspaces in an environment.
Note: If you would like to keep family group together in sort order, you must set Field 1/5 to Family Group following
with other sorting criteria.
Once a production is completed, information stored from the production is copied to the following fields as configured.
Note: Create dedicated Fixed-Length Text fields for this operation or select fields with the purpose of having bates
populated. Selecting one of the template fields may result in production failure.
27.5.8 Other
The Other section displays additional fields added to the form after the production set was saved:
l Restriction override by - displays the name of the user who clicked the Override and Continue button when
running the production without removing conflicts. This user must have the Override Production Restrictions
permission.
l Restriction override on - lists the date and time when the production restrictions were overridden.
l Edit - re-displays the production set form so you can update values in the fields. See Creating and editing a pro-
duction set on page 414.
l Delete - removes the production set from Relativity. When you delete a production, the production is imme-
diately removed from the Production sets tab. However, you may still see the Bates numbers from the pro-
duction in the Documents tab. Relativity deletes the Bates numbers, the production data source, and any other
remaining production information during off hours.
If you don't want to lose the previously recorded Bates numbers, run the Assign Legacy Document Bates Fields
script from the Relativity Script Library. After you click Delete, a confirmation message displays with the
Note: When deleting a production the production images are deleted, not the original images.
l Back - redirects you to the item list on the Production Sets tab
l Edit Permissions - displays a security page where you can set user permissions on a production set. You can
edit rights only on the current production set. By default, the Production Set tab is secured according to the work-
space-level rights. See the Admin guide for more information on setting permissions on objects.
l View Audit - displays the history for the production.
The Production Set details options view also shows Production Status Information, Basic Settings, Numbering,
Branding, Sorting, Other, and the Production Data Source. Once the production is run, you can also view the First and
Last Bates Values associated with the production.
l Create multiple redaction sets by defining different markups. See Markups on page 307.
l Use each markup to redact the same document.
l Create a production and select a specific markup.
When you select the markup, it controls the redactions branded during production, so you can track multiple redaction
sets on the same document, and generate different productions.
Note: If you add a field to a conditional statement incorrectly, you can still save and run the production set, but the
branding will not generate an error and will produce incorrect results.
Note: The example in this section does not demonstrate everything that you can do with the production object.
As shown in the screen shot below, you can combine free-form text with productions objects.
Name in Advanced
Name Data type Description Formatting drop-
down list
ArtifactId int The ArtifactId of the document in the production. Artifact Id
HasRedactions bool If set, the current document contains redactions on at Document Has
least one page. Redactions
HasPlaceholder bool If set, the current document is a placeholder. Has Placeholder
BeginBates string The first bates number in this document. Begin Bates
EndBates string The last bates number in this document. End Bates
BeginBatesAttachment string The first attachment bates number in this document. Begin Bates Attach-
ment
EndBatesAttachment string The last attachment bates number in this document. End Bates Attach-
ment
Notes:
l These values are in string format as done in
object manager.
l Custom Placeholders also supports these
field types.
l Reflected fields are not supported.
l case FieldType.Date
l case FieldType.Decimal
l case FieldType.FixedLengthText
l case FieldType.WholeNumber
l case FieldType.YesNo
l case FieldType.SingleChoice
l case FieldType.MultipleChoice
Example of Advanced Formatting with the document object
Note: The example in this section does not demonstrate everything that you can do with the document object.
As shown in the screen shot below, you can create conditional statements with the document object.
Note: The example in this section does not demonstrate everything that you can do with the page object.
As shown in the screen shot below, you can use page objects in conditional statements.
{% if context.Document.Page.PageNumber == 1 %}
Only brand this text on page 1.
{% endif %}
{% if context.Document.Page.PageNumber > 1 %}
Brand Bates number on every page after page 1:
{{context.Document.Page.BatesNumber}}
{% endif %}
The document in the screen shot below is branded per the commands in the screen shot above. The free-form text
from the first conditional statement is only printed on the first page. The free-form text from the second conditional
statement is only printed on the second page.
l Brand the free-text, Production Name, and Page Number on every page.
Production Name: {{context.ProductionName}}
Page # {{context.Document.Page.PageNumber}}
l Brand the free-text on pages that have redactions.
{% if context.Document.Page.HasRedactions%}
THIS PAGE CONTAINS REDACTIONS
{% endif %}
l Brand the free-text on pages that have a specific page number.
{% if context.Document.Page.PageNumber == 1 %}
This text will be branded only on page 1
{% endif %}
l Brand the Bates Number on every page after page number 1.
{% if context.Document.Page.PageNumber > 1 %}
{{context.Document.Page.BatesNumber}}
{% endif %}
Note: 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.
Note: The PDF option is for rendered PDFs i.e., natives which were converted to PDFs and stored.
8. Select a Document Source from the available saved searches to use as a data source for the production.
Note: You must create public saved searches in order for your searches to populate another Relativity user's
Available Items list.
l Use Image Placeholder—a single-choice field to add image placeholders to the data source. Docu-
ments without images receive a placeholder (slip-sheet) in their place. The placeholder receives the
same branding as the rest of the produced images. This option is only available if you produce images.
l When No Image Exists—inserts a placeholder only when no image exists for a document.
l Always Use Image Placeholder—always inserts an image placeholder even when an image
exists for a document.
l Never Use Image Placeholder—this is the default option. Never inserts an image placeholder for
any document.
l
Placeholder—the placeholder used for the data source. Click to view a list of available place-
holders from your placeholder library. Click Add to add a placeholder on-the-fly. This field automatically
appears when you select Always Use Image Placeholder or When No Image Exists.
l Burn Redactions—indicates that redactions are applied to the documents when this field is enabled.
Toggle On to apply redactions to documents. Toggle Off to not apply redactions. If you select to burn nat-
ive redactions with the Burn Native Redactions field, this automatically displays a value of No.
l Burn Native Redactions—toggle on to include redacted natives as part of the production set. This auto-
matically sets to No if you've enabled the Burn PDF Redactions field. Toggling this field on makes the
Markup Set and Native Redaction Text Field settings required below.
l Burn PDF Redactions—toggle on to include redacted PDFs as part of the production set. This auto-
matically sets to No if you've enabled the Burn Native Redactions field. Toggling this field on makes the
Markup Set and Native Redaction Text Field settings required.
l Burn PDF Branding—toggle on to brand PDFs during Production with the configured settings. This field
automatically appears when you select PDF as a Production Type.
l Markup Set—indicates which markup set is used to apply standard or native redactions to the pro-
duction images. This field is only visible if you toggled on burn redactions or native redactions.
l Native Redaction Text Field—select the field you want to use when burning native redactions. This
field is only visible if you enabled the Burn Native Redactions field.
Note: There is an expected delay between a Production Set being marked as completed, and the des-
ignated Native Redaction Text field being populated.
27.7 Placeholders
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 Placeholder library automatically includes a default
image placeholder.
Note: When creating a template workspace using production, Relativity automatically copies Placeholders.
Note: It's recommended image placeholders image size should be 2,550 pixels by 3,300 pixels at 300 DPI.
Note: If you add a large amount of text or upload large images to your custom placeholders there can be an
increase in the staging and producing time of your productions.
Note: You can only use the date, decimal, fixed-length text, whole number, yes/no, single and
multiple choice fields as a token for your placeholder. You must have permissions to the doc-
ument fields to use them as a token for your placeholder.
5. Click Save.
l Preview Production - displays a sample image showing how the branding is applied to documents in the pro-
duction.
l Stage Production - takes a snapshot of the data sources for the production. For more information, see Stage a
production.
l Stage and Run Production - takes a snapshot of the data sources and then automatically begins producing
the staged documents. For more information, see Stage and run a production.
l Cancel - stops the stage and run job.
l Cancel Staging - cancels a staging production. This is a dynamic button that appears once you click Stage Pro-
duction.
l View Documents - displays a list of all documents included in the production set. You can use the drop-down
list in the upper right corner to toggle between viewing produced documents and the individual pages of the doc-
uments. For more information, see View documents.
Note: You must have View Production and View Data Source permissions to view the list of documents
included in the production set. The list of documents filters out documents you don't have access to.
l Check for Conflicts - determines whether the production set includes any documents that conflict with another
pre-determined set of documents.For more information, see Check for production conflicts.
l Run Production - proceeds with the production of staged documents. If documents with conflicts have not
been removed from the production set, the Production Restrictions appears. Running a production auto-
matically creates a saved search. If you're a system admin, you can resolve the message using the following
options:
l Override and Continue - proceeds with the production without removing the conflicts based on the Over-
ride Production Restrictions permission.
l Cancel - stops the production from running.
For more information, see Run a production.
l Cancel Production - cancels a running production. This is a dynamic button that appears when you click Run
Production.
l Rerun Errored Documents - proceeds with the production of previously errored documents after you make
corrections. To ensure quality record processing, this button is not active until the production is complete. If any
documents in the production set resulted in alerts, click the Rerun Errored Documents button to rerun these
documents.
l Rerun Errored Post Production - retries the Post Production steps that errored. The button is only active
when any of the Post Production steps completed with an error.
l View Branding Errors - displays a pop-up with all documents and Branding error messages per document.
You can click on a document within the pop-up to open the document and determine the cause of the error. This
button only appears if branding errors occur during a production run.
l View Production Errors and Warnings - displays a pop-up that lists the validation and production error mes-
sages and warning that occurred.
l Copy To Legacy Document Fields - launches the script window to update Bates fields you create on the
Document table with the Bates numbering information stored in the Production Information RDO of a production
you select. For more information, see Copy To Legacy Document fields in the admin guide.
When an error occurs, click View Production Errors and Warnings on the Production console to open the Error
Starting Production pop-up. The Error Staging Production pop-up lists the errors that occurred.
Conflicts occur when the data sources have documents that are also in the saved search selected in the Production
Restriction field.
If a staging error occurs, address the error and then click Stage and Run Production.
Validation
During validation, Relativity performs a conflict check and data source validation. After validation finishes, production
begins.
When a validation error occurs, click View Production Errors and Warnings on the Production console to open the
Error Starting Production pop-up. The Error Staging Production pop-up lists the errors that occurred.
Production
During production, Relativity produces the staged documents. After production finishes, branding begins.
If a production error occurs, click View Production Errors and Warnings on the Production console to see why the
error occurred. After addressing the error, click Run Production on the Production console.
Branding
During branding, Relativity applies redactions and the specified header and footer to the images. Once this step
finishes, your production job is complete.
To resolve branding errors:
1. Click View Branding Errors on the Production console to open the Branding Errors pop-up.
Post Production
This step is only available on the Production Set Console if Post Production was enabled during Production Set
creation. During this step Relativity automates frequent production tasks.
l Total Documents Count - lists the number of documents found during staging.
l Total Images Count - lists the number of images found during staging.
l Documents With Images - lists the number of documents that include images found during staging
l Documents With Natives - lists the number of documents that include native files found during staging.
l Begin Bates—lists the Bates number of the first document in the production set.
l End Bates—lists the Bates number of the last document in the production set.
l Total Docs—lists the number of documents included in the production set.
l Total Images—lists the number of images included in the production set.
l Docs With Images—lists the number of documents that include images included in the production set.
l Docs With Natives—lists the number of documents that include natives included in the production set.
l Docs With PDFs—lists the number of documents that include stored PDFs in the production set.
l Docs With Placeholders—lists the number of documents that include placeholders included in the production
set.
l Documents With Redactions—lists the number of documents that include redacted images and redacted nat-
ives included in the production set.
l Total Documents Count - lists the number of documents found during staging.
l Total Images Count - lists the number of images found during staging.
l Documents With Images - lists the number of documents that include images found during staging
l Documents With Natives - lists the number of documents that include native files found during staging.
l Documents With Placeholders - lists the number of documents that include Placeholders found during sta-
ging.
Note: You must have permissions to the documents included in a production to remove production restrictions.
When you click Check for Conflicts, a Production Restrictions warning may appear if a saved search is being used to
restrict productions.
l Remove Conflicts - deletes documents identified as conflicts from the production set (based on the Production
Restrictions setting). If all the documents are conflicts, they are removed from the production set.
Note: To view a list of documents removed from the production, navigate to the History tab, and filter on the
Production - Remove Document action.
l Cancel - stops the conflict check and displays the production page.
l Cleaning Existing Files - deletes placeholder files (slip sheets) and any produced image files from a prior run
production, if necessary.
l Creating Placeholder Images - creates placeholder images based on the production data source.
Note: In the viewer, you can view the produced images by selecting the Production mode. You can view the images
exactly as they were produced.
l Begin Bates—lists the Bates number of the first document in the production set.
l End Bates—lists the Bates number of the last document in the production set.
l Total Docs—lists the number of documents included in the production set.
l Total Images—lists the number of images included in the production set.
l Docs With Images—lists the number of documents that include images included in the production set.
l Docs With Natives—lists the number of documents that include natives included in the production set.
l Docs With PDFs—lists the number of documents that include stored PDFs in the production set.
l Docs With Placeholders—lists the number of documents that include placeholders included in the production
set.
l Documents With Redactions—lists the number of documents that include redacted images and redacted nat-
ives included in the production set.
When an error occurs, click View Production Errors and Warnings on the Production console to open the Error
Starting Production pop-up. The Error Staging Production pop-up lists the errors that occurred.
Conflicts occur when the data sources have documents that are also in the saved search selected in the Production
Restriction field.
Conflicts occur when the data sources have documents that are also in the saved search selected in the Production
Restriction field.
Restrictions pop-up.
3. Click Run Production on the Production console.
Override the conflict Keep the documents in the production set that are also in
the saved search selected in the Production Restriction
field.
To override the conflict:
1. Click Run Production on the Production console.
The Production Warnings pop-up will open.
2. Click Override and Continue on the Production
Warnings pop-up. The production job will continue
without removing the conflict documents.
Modify the production Modify the Production Restriction field so none of the
restriction documents in the production restriction saved search are
also in the production set. For information on modifying a
production restriction, see Adding and editing production
restrictions.
After modifying the production restriction, click Stage
and Run Production on the Production console.
1. Click View Branding Errors on the Production console to open the Branding Errors pop-up.
27.11 Re-production
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.
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.
Re-production jobs are stored as regular productions in the system and are not deleted after they are complete. If you
want to export just the documents that were modified, use Import/Export to export the re-production job.
l The re-production feature only works with productions that have been run in Relativity. It will not work with out-
side productions that have been loaded in.
l You can re-produce documents from multiple production sets with a single mass operation. However, you can
only apply one re-production type at a time. Relativity recommends using saved searches to group documents
that need the same type of re-production. See Re-production types on page 459.
l Replace produced images with place- l Replace a document that was produced as a placeholder
holder (I-P) below with another placeholder.
l Replace placeholder with images (P-I) l Replace a document that was produced as native only with
on the next page produced images or a placeholder.
l Re-produce documents (same number l Re-produce the same document as images but with a dif-
of pages) (I-I) on page 462 ferent number of images.
While you can re-produce documents from multiple production sets with a single mass operation, you can only apply
one re-production type at a time. For example, if you want to re-produce 100 documents, and you want to replace 60
with produced images and replace 40 with a placeholder, you would need to run two mass operations.
If none of the documents selected meet the re-production type you choose, when you move to the next step you will
receive this error: “No productions match the re-production criteria. Please verify all selected documents are included
in a production and match the original production type of the re-production options.” For example, you will receive this
error if you selected five documents that were produced only as Natives and if you selected "Replace produced
images with placeholder" as the Re-production type. To resolve the error, exit the module and remove the documents
that do not meet the selected re-production type criteria from the group of documents you selected for re-production.
To avoid this error, Relativity recommends using saved searches to group documents that need the same type of re-
production.
Note: The documents must already be imaged before you run the mass operation, or an error will occur with the
mass operation.
Note: The documents that you are using to replace the documents in the production must be the same number of
pages as the documents in the production that you are replacing.
l Include Natives - a boolean field. Select Yes to include the natives of the documents you selected for re-pro-
duction. Set this field to No if you only want to include a placeholder for the documents. This option overrides
the option on the original production. If the document was originally produced with natives, but the user does not
select "Include Natives", the document will be merged to the original production with no natives.
l Burn redactions - a boolean field. Select Yes to apply redactions to the documents you selected for re-pro-
duction. Set this field to No if you do not want redactions applied to the documents.
l Select Markup Set - indicates which markup set is used to apply redactions to the production images.
Doc A was
produced as
images in
Prod_2
Doc B was
produced as
placeholder in
Prod_2
Doc A was Replace Prod_1 Prod_1 | 1 out of the total of Doc A is re-pro-
produced as Placeholders 2 documents selected will duced in Prod_1
placeholder in with images Note: Prod_2 is not displayed be modify in this pro-
Prod_1 because Doc A and Doc B duction.
were not produced as
placeholder in Prod_2.
Doc A was
produced as
images in
Prod_2
Doc B was
produced as
images in
Prod_2
Note: If you are modifying multiple productions at the time, the options that you select on this step will apply
to all the productions you are modifying, including the placeholder selected in this step, burn redactions, and
the options of whether the documents will be produced with natives.
5. Click Next.
6. Select the productions that you want modify.
Note: Only productions associated with the selected documents and options display. Productions with a
status different to “Produced” or Productions that used Existing numbering will not be available here.
7. Click Re-produce.
Note: Do not close the Re-produce Documents module until the Confirmation checkmark appears. Once the
Confirmation checkmark appears, the re-production sets have been created and added to the Production
queue.
l Click Click here in the Re-produce Documents module. This will take you to the Re-production view. See Re-
production views on the next page.
l Re-productions - a view that lists every re-production jobs. Fields in the view include:
l Name - the name of the re-production job.
l Status - the status of the re-production job.
l First Bates Value - the first bates number in the production.
l Last Bates Value - the last bates number in the production.
l Prefix - the characters added to the beginning of each Bates number.
l Production Set - the name of and link to the original production set.
l Original Productions - a view that lists every production set that have been modified by a re-production job.
Fields in the view include:
l Name - the name of the original production.
l Status - the status of the production job.
l First Bates Value - the first bates number in the production.
l Last Bates Value - the last bates number in the production.
Note: Branding agents scale automatically in RelativityOne based on the total size of all jobs in queue. All agents
will be assigned to the highest priority Production, one at a time.
To change the priority of a job, click the Change Priority button at the bottom of the view. Enter a new integer value in
the Priority field, and then click Update. Only one job runs at a time, the lower numbered job runs first and the higher
numbered job runs last.
Note: Any change to the priority of a job in the branding queue also changes its priority in the production queue.
l Workspace - the workspace that contains the production set receiving branding
l Production Name - the production set receiving branding
l Artifact ID - the unique identifier for the production set
l Images Remaining - the number of images that require branding
l Status - the current stage of the branding job
l Priority - the order in which the branding job is run. Relativity completes branding jobs by priority. The default
value is 100.
l Submitted By - the user who initiated the job. You can use this information to prioritize branding jobs by user.
Note: During a production job, Relativity sends a job to the branding queue for the stamping of redactions, headers,
or other modifications. Any change to the priority of a job in the production queue changes its priority in the branding
queue.
Note: As long as you have the listed security permissions, you do not need view permissions to the work-
spaces or the production jobs to use Retry Production Job.
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
4. Click Ok.
Note: As long as users have the listed security permissions, they do not need view permissions to the work-
spaces or the production jobs to use Cancel Production Job.
l Click Ok.
l Workspace - the workspace that contains the production set used for a job.
l Production Name - the production set used for the job.
l Artifact ID - the unique identifier for the production set.
l Status - the current stage of the production job.
l Apply markups manually to the documents. To learn more, visit Manual markups with spreadsheet files,
Manual markups with PDF files, and Redacting PDF annotations and attachments.
l Search for terms in spreadsheet files and apply markups to them. To learn more, visit Using Find and
Redact.
l Apply markups automatically using project automation. To learn more, visit Automated spreadsheet
markup project, Automated spreadsheet propagation project, Automated PDF markup project, Auto-
mated image markup project, and Automated image template project.
3. Review the markups to ensure quality control before production. To learn more, visit Reviewing markups to
ensure accuracy.
4. Create a saved search of marked-up documents to assist you in producing them. To learn more, visit Searching
for documents with Redact fields.
Note: All Redact permissions, including Redact mass operations, are granted to system and workspace admin-
istrators upon the initial workspace install. After installation, it is up to the system and workspace administrators to
grant additional Redact permissions to user groups per workspace.
While occasionally files can be become corrupted and not work in Redact, the following file types are supported:
l .pdf—any standard
l .csv
l .xls—Excel 97 - 2003 workbook.
l .xlsb—Excel binary workbook.
l .xlsx—Office Open XML spreadsheet, ML workbook or template file, with or without macros.
l .xlsm—Excel macro-enabled workbook.
l .xltx—Excel template.
l .xltm—Excel macro-enabled template.
l .xlam—An Excel macro-enabled add-In file that’s used to add new functions to Excel.
28.6 Permissions
Redact has permissions that you can give users that determine the actions they can take using this feature. To
understand what permissions do and what permissions you may want to assign to users, read thelist of all Redact
permissions below and then groups of permissions that you may want to assign to allow a user to perform specific
types of workflows. You can navigate to these sections by using the links below:
l Native PDF Redactions—users will not see PDF markup projects or Redact Markup Navigator features in the
Viewer for native PDFs without this permission. Additionally, users will not be able to automatically or manually
apply markups on native PDF documents.
l Native Excel Redactions—users will not see spreadsheet markup projects or spreadsheet propagation pro-
jects without this permission. Additionally, users will not see Redact Markup Navigator features in the Viewer for
native spreadsheet documents without this permission. They will also not be able to automatically or manually
apply markups on native spreadsheet documents.
l Image Redactions—users will not see the image markup project or image template projects without this per-
mission. Additionally users will not see Redact cards in the Viewer for images without this permission. They will
also not be able to apply redactions and/or highlights on the Document object.
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
l Create and run spreadsheet markup projects and automated spreadsheet propagation projects.
l Manually apply markups to native spreadsheet documents in the Viewer.
l QC markups that were applied automatically by Redact projects.
l Edit the redaction text that has been applied to native spreadsheet documents.
l Create and run production preparation projects for native PDF documents.
Assign them the following permissions:
l Create and run image markup projects and image template projects.
l Manually apply markups to imaged documents in the Viewer.
l QC markups that were applied automatically by Redact projects.
l Edit the redaction text that has been applied to native imaged documents.
l Create and run production preparation projects for imaged documents.
Assign them the following permissions:
l Redact permissions
l Image Redactions
l Place/Edit Manual Redaction
l Place/Edit Manual Highlight
l View Quality Control Panel
l Accept/Reject Quality Control Entries
l Input Custom Redaction Text
l Redact Produced Document
l Document object permissions
l Redact Document
l Highlight Document
l Redact Produced Document—this permission is required to see the corresponding field when creating and
running a production preparation project
l Redact Redacted File—this permission is assumed, and removing this permission does not impact a user's
access to Redact. All RDOs have a corresponding permission by default
l Convert Spreadsheet Markups—view and use the Convert Spreadsheet Markups mass operation. To learn
more, visit Convert Spreadsheet Markups.
l Delete Native Markups—view and use the Delete Native Markups mass operation.
l Prepare Excel Content—view and use the Prepare Excel Content mass operation.
l Upload/Add/Delete Image—a user should be granted these permissions if they are redacting images outside
of Relativity.
l Replace Document—a user should be granted this permission if they are redacting native documents outside
of Relativity. This permission allows users to replace native documents.
l Create PDF—a user should be granted this permission if they have a workflow to redact a PDF of a native doc-
ument.
l Local Access (Download, Copy Text)—a user should be granted this permission if they want to download the
native document, redact the copied native document, and then re-upload that document to Relativity.
28.7.3.1 Considerations
l If you apply a markup to a cell where the text overflows into empty neighboring cells, just as in the native applic-
ation, the markup does not overflow into empty neighboring cells. However, when the document is produced
and the markup is burned in, the text from the original cell no longer overflows and is completely hidden by the
markup.
l Due to a limitation in the Excel file format, a cell cannot contain more than 32,000 characters. If you try to apply
a text redaction to a cell and it already contains 32,000 characters, the redaction may not be applied and you
will see a notification about the character limit.
28.7.6 Fields
The following sections and fields display while creating a spreadsheet project:
l Redact all headers and footers — select to replace the content in each header and footer with the default
redaction text.
l Redact all Excel objects — select to apply a black redaction on all objects in the Excel documents included in
this project. Excel objects include: WordArt, SmartArt, and embedded documents (email and Powerpoint),
images equations, text-boxes, and shapes.
Note: Selecting this option does not cause markups to be applied on charts. You can apply redactions to
charts manually. To learn more, visit Manual markups with spreadsheet files.
l Redact all Comments — select and choose one of the following options to apply markups to comments in
Excel documents:
l Remove comments — select to remove any comments on spreadsheet files.
l Remove comment text — select to replace comments with either [Redacted] or the text you enter in
the box below this option.
l Fallback text—If you select redact options that are not valid and the project finds a match in a document, the
text entered in this field will be used instead. For example, attempting to apply a black redaction to a .csv file is
invalid and so the text entered in this field is applied as a redaction instead.
l Ignore certain rows or columns — select this option to prevent markups from being applied to specified rows
or columns. This option can be used to ensure headers and footers display in Excel documents. Once this
option is selected, the rows and columns to be excluded from markup section displays underneath. Enter the
rows or columns separated by commas that should not have markups applied.
Rules section
The Rules section is optional and these fields determine how the spreadsheet project will apply markups once it is run.
After completing the fields in this section, a new group of fields will appear below it so that you can create multiple
Note: If you are uploading a .csv file, this section should be left blank. To learn more, visit Creating a spreadsheet
markup project using .csv rules.
Note: Highlights are not compatible with .csv files. If you select either highlight option and run a project, it will
result in errors and markups will not be applied to terms that match this rule.
l Markup Reason — enter a description of why the markup for this rule will be applied to make it easy to track
when reviewing markups using the Redact Navigation card.
l Markup Scope — determines the markup behavior when the project matches content in a document with a
rule. Select one of the following options:
l Character - places the markup on each cell where the entered characters match or on any non-cell char-
acter matches. This option can be used to redact information that is not a word such as an email handle
or a social security number. Inverse redactions are not compatible with character markups. Markups
applied using this option are not compatible with Convert Spreadsheet Markups.
l Word — places the markup only on the exact matched text inside each cell that fits this rule. This option
is only available if Redaction is selected.
l Cell — places the markup on each cell that matches this rule. All of the content in the cell where a match
is made will be covered by the markup.
l Row — places the markup on the entire row where a cell matches this rule.
l Column—places the markup on the entire column where a cell matches this rule.
l Sheet — places a markup on the entire sheet where a cell matches this rule. If a match is found in the
sheet name and not any other cells in the sheet, only the sheet name will receive a markup.
l Include Sheet name & content — this option only displays when Sheet is selected. Select this
option to apply a markup to both the sheet name and the sheet when a match is found. If this
option is not selected and a match is found in the sheet name and not any other cells in the sheet,
only the sheet name will receive a markup.
l Markup SubType — select the style of markup you would like to place for this rule. The options available in this
drop-down menu are determined by the Redaction/Highlight/Inverse/Inverse Highlight toggle.
Note: Certain fields and file formats only support Text redactions. If you select a Markup SubType other than
Text, and the project applies markups to a location that only supports Text redactions, those redactions will
be changed to show the project's specified Fallback text. Areas where this applies include:
- All locations within a CSV
- Excel sheet names
- Excel headers & footers
- Excel comments
- Excel chart labels
l Place redactions on sheets without matches — select to place inverse redactions or highlights on any
sheets that do not have content that matches this rule. This option best used when you want the majority of the
l Name — enter a name for this rule. Optionally, click on the drop-down menu to view a list of commonly used reg-
ular expressions as well as custom regular expressions users have created and select one to populate both the
Name and Regex fields. These commonly used regular expressions are a starting point and not intended be all-
inclusive of every variation of these patterns. Variations in document type, text quality, and pattern variability
should be considered when using regular expressions.
l Regex — enter a regular expression which can be used to identify important patterns like email addresses,
social security numbers, credit card numbers, and any other content that may appear in a regular pattern
throughout the documents in the selected saved search. Regular expressions require a name and the
Note: If you use regex101.com to help form regular expressions to enter in Redact, ensure that you set it to
/gmi (global, multi-line, case insensitive) to help you better achieve the desired results in Relativity.
When using regular expressions, the scope of markups applied is based on word. When a regular expression
matches the word, it uses spaces to determine where to start and stop applying the markup. So if a set of words
do not have spaces between them, a markup will be applied to the entire set and not just the word that matches
your entered terms.
The following table includes potential terms that can be searched using regular expressions and an example of
a word or phrase that will be completely covered by a markup to illustrate this behavior:
l DtSearch - Enter a DtSearch syntax where you would like to apply markups to any matches based on the
Markup Scope and Markup SubType options selected. By default, Redact will apply markups to every term in a
search syntax. DtSearch uses cross-cell matching so if a rule has text that would span multiple cells, all cells
that contain a match will be redacted.
Optionally, you can apply markups to part of a DtSearch syntax. For example, apple w/2 pear causes both
apple and pear to receive markups. If you would like to apply a markup to one of the terms, in this case, apple,
use the following syntax: (?<redact>apple) w/2 pear.
Noise words and the alphabet list are not compatible with this field. We recommend using W/N operator for prox-
imity matches instead.
Note: Combining special characters or operators may lead to inaccurate results. We recommend using
Regex in these situations instead.
The following syntax options are available with this field:
Note: If a document that is too large is included in a project, it may not receive markups. The maximum file size for
documents that can be opened in the Viewer and receive markups is determined by the Max-
imumNativeSizeForViewerInBytes instance setting. Increasing this instance setting's value can negatively impact
Relativity's performance.
1. Navigate to the Documents tab and select a spreadsheet document from the list that has already been pre-
pared for Redact.
2. Click on the Open Original Native button.
A new browser window opens where you can click Native to view the native spreadsheet document or click Ori-
ginal Native Text to see the document before it was prepared for Redact.
28.8.4 Fields
The following sections and fields display while creating an image markup project:
l Saved Search—click on the drop-down menu and select the saved search that you wish to apply markups to.
Optionally, you can enter a term or terms into search box at the top of the menu to help narrow results and find
the desired saved search.
l Markup Set—click on the drop-down menu and select the markup set that you wish to use to apply markups.
Rules section
The Rules section is optional and these fields determine how the image project will apply markups once it is run. After
completing the fields in this section, a new group of fields will appear below it so that you can create multiple rules in
an image project if desired.
Note: If you are uploading a .csv file, this section should be left blank. To learn more, visit Creating an image
markup project using .CSV rules.
l Redaction/Highlight toggle—determines which type of markup you will be applying for this rule.
l Markup Reason—enter a description of why the markup for this rule will be applied to make it easy to track
when reviewing markups using the Redact Navigation card.
l Markup Scope—determines the markup behavior when the project matches content in a document with a rule.
Select one of the following options:
l Character—places the markup on the exact match even if the match is part of a word. When this option
is selected, new OCR text is generated before markups are applied. This option can also be used to
redact information that is not a word such as an email handle or a social security number
l Word—places the markup on the entire word that matches this rule.
l Line—places the markup on the entire line of text where a word matches this rule.
l Name—enter a name for this rule. Optionally, click on the drop-down menu to view a list of commonly used reg-
ular expressions as well as custom regular expressions users have created and select one to populate both the
Name and Regex fields. These commonly used regular expressions are a starting point and not intended be all-
inclusive of every variation of these patterns. Variations in document type, text quality, and pattern variability
should be considered when using regular expressions.
Note: If you use regex101.com to help form regular expressions to enter in Redact, ensure that you set it to
/gmi, global, multi-line, case insensitive, to help you better achieve the desired results in Relativity.
When using regular expressions, the scope of markups applied is based on word. When a regular expression
l DtSearch—enter a dtSearch syntax where you would like to apply markups to any matches based on the
Markup Scope and Markup SubType options selected. By default, Redact will apply markups to every term in a
search syntax. dtSearch uses cross-cell matching so if a rule has text that would span multiple cells, all cells
that contain a match will be redacted.
Optionally, you can apply markups to part of a dtSearch syntax. For example, apple w/2 pear causes both apple
and pear to receive markups. If you would like to apply a markup to one of the terms, in this case, apple, use the
following syntax: (?<redact>apple) w/2 pear.
Noise words and the alphabet list are not compatible with this field. We recommend using W/N operator for prox-
imity matches instead.
Note: Combining special characters or operators may lead to inaccurate results. We recommend using
Regex in these situations instead.
The following syntax options are available with this field:
28.9.3 Fields
The following fields display in the Create image template project section:
Note: The document you use for this field applies markups to documents in the saved search based on the
number of pages it has. For example, if you enter the control number for a document that only has one page,
when you run the project, it will only apply markups to the first page of all the documents in the saved search,
even if some of those documents contain two or more pages.
28.10.5 Fields
The following sections and fields display while creating a PDF project:
l Saved Search—click on the drop-down menu and select the saved search that contains the documents you
wish to apply markups to. Optionally, you can enter a term or terms into search box at the top of the menu to
help narrow results and find the desired saved search.
l Markup Set—click on the drop-down menu and select the markup set that you wish to use to apply markups.
l PDF Version—select an option to determine which type of PDF file to apply markups to.
l Native—if selected, markups are applied to the original document and they are visible in the Native
Viewer.
l Stored—is selected, markups are applied to the stored PDF generated by the PDF application and the
markups are visible in the PDF Viewer.
l Remove All Attachments—check to remove all attachments from each document in your selected saved
search.
Rules section
The Rules section is optional and these fields determine how the PDF project will apply markups once it is run. After
completing the fields in this section, a new group of fields will appear below it so that you can create multiple rules in a
PDF project if desired.
Note: If you are uploading a .csv file, this section should be left blank. To learn more, visit Creating a PDF markup
project using .csv rules.
l Redaction/Highlight toggle—determines which type of markup you will be applying for this rule.
l Markup Reason—enter a description of why the markup in this group will be applied to make it easy to track
when reviewing markups in the Redact Navigation card.
l Markup Scope—determines the markup behavior when the project matches content in a document with a rule.
Select one of the following options:
l Name—enter a name for this rule. Optionally, click on the drop-down menu to view a list of commonly used reg-
ular expressions as well as custom regular expressions users have created and select one to populate both the
Name and Regex fields. These commonly used regular expressions are a starting point and not intended be all-
inclusive of every variation of these patterns. Variations in document type, text quality, and pattern variability
should be considered when using regular expressions.
Note: If you use regex101.com to help form regular expressions to enter in Redact, ensure that you set it to
/gmi (global, multi-line, case insensitive) to help you better achieve the desired results in Relativity.
When using regular expressions, the scope of markups applied is based on word. When a regular expression
matches the word, it uses spaces to determine where to start and stop applying the markup. So if a set of words
do not have spaces between them, a markup will be applied to the entire set and not just the word that matches
your entered term(s).
The following table includes potential terms that can be searched using regular expressions and an example of
a word or phrase that will be completely covered by a markup to illustrate this behavior:
Note: Combining special characters or operators may lead to inaccurate results. We recommend using
Regex in these situations instead.
The following syntax options are available with this field:
Note: If a document that is too large is included in a project, it may not receive markups. The maximum file size for
documents that can be opened in the Viewer and receive markups is determined by the Max-
imumNativeSizeForViewerInBytes instance setting. Increasing this instance setting's value can negatively impact
Relativity's performance.
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.
Note: Spreadsheet propagation projects are not compatible with nested saved searches. A nested saved search is
where one of the search conditions is in another saved search. Using a nested saved search may result in a project
that does not successfully complete.
l Saved Search—click on the drop-down menu and select the saved search that contains either only Excel or
.csv documents with markups that you wish to use as the source to be applied to another group of Excel or .csv
documents. Optionally, you can enter a term or terms into search box at the top of the menu to help narrow res-
ults and find the desired saved search.
Note: Spreadsheet propagation projects are not compatible with nested saved searches. A nested saved
search is where one of the search conditions is in another saved search. Using a nested saved search may
result in a project that does not successfully complete.
l Markup Set—click on the drop-down menu and select the markup set that contains markups used on the doc-
uments in the source saved search.
Destination Documents
l Saved Search—click on the drop-down menu and select the saved search that contains either only the Excel
or .csv documents that you wish to receive markups from the source documents. Optionally, you can enter a
term or terms into search box at the top of the menu to help narrow results and find the desired saved search.
Note: Spreadsheet propagation projects are not compatible with nested saved searches. A nested saved
search is where one of the search conditions is in another saved search. Using a nested saved search may
result in a project that does not successfully complete.
l Markup Set—click on the drop-down menu and select the markup set that you wish to use to apply markups to
the destination Excel or .csv documents.
Note: If a document is skipped but does not appear to have markups associated with it, try clearing the markup set
and re-running the project.
Note: If a document that is too large is included in a project, it may not receive markups. The maximum file size for
documents that can be opened in the Viewer and receive markups is determined by the Max-
imumNativeSizeForViewerInBytes instance setting. Increasing this instance setting's value can negatively impact
Relativity's performance.
1. Navigate to the Documents tab and select a spreadsheet document from the list that has already been pre-
pared for Redact.
2. Click on the Open Original Native button.
A new browser window opens where you can click Native to view the native spreadsheet document or click Ori-
ginal Native Text to see the document before it was prepared for Redact.
Note: Only text or cell content redactions can be applied to .csv files.
1. Navigate to the Documents tab and select any documents you wish to convert.
2. Select the Convert Spreadsheets Markup option from the mass operations bar.
3. Select the Markup Set you wish to convert and then select the Markup Type and Markup Subtype you wish to
convert from and to.
4. Click Submit.
The selected documents have the applied highlights converted to redactions or the applied redactions con-
verted to highlights and an email is sent to the user's email address that summarizes the results of the mass
operation.
Note: 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.
If you would prefer to have markups applied automatically, see Automated spreadsheet markup project and
Automated spreadsheet propagation.
Note: Due to a limitation in the Excel file format, a cell cannot contain more than 32,000 characters. If you try to
apply a text redaction to a cell and it already contains 32,000 characters, the redaction is applied but you cannot
save it.
Excel files must be prepared for redaction prior to markup application. 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.
When you apply the first markup to an Excel file, the following will occur:
l All calculated fields are replaced with their original calculated values.
l All formulas are replaced with their calculated values.
l All pivot tables are replaced with their original calculated values.
l All change-history is removed from documents.
l All hidden and very-hidden rows, columns, and sheets are unhidden.
l All merged cells are un-merged.
l Comma
l Tab
l Semicolon
l Colon
l Space
If no delimiter is found, the .csv file will display in a single column. Redact provides warning messages that indicate
which .csv files failed to match a delimiter to help you troubleshoot.
You can apply redactions to a single cell or multiple cells by doing the following:
Note: If you apply a markup to a cell where the text overflows into empty neighboring cells, just as in the native
application, the markup does not also overflow into empty neighboring cells. However, when the document is
produced and the markup is burned in, the text from the original cell no longer overflows and is completely hidden by
the markup.
You can apply markups to a single cell or a series of rows or columns by doing the following:
1. Select and apply a markup to the Excel document. See Manually applying markups for more information.
2. Select the desired cell, row, or column that you wish to apply the same type of markup to.
3. Right-click and select the Redact - name of the previously applied markup option. During a session, the
name of this option updates to display the name of the markup type that was most recently applied.
A markup of the same type as was most recently applied is added to the currently selected cells, rows, or
columns.
Note: Due to a software requirement in Excel, each sheet name redaction you enter must be unique com-
pared to the other sheet names.
6. Click Redact.
The Sheet Name redaction is applied to the sheet.
Note: Due to limitations of the .xls file format, the Review Interface is unable to visually represent markups applied
to either the full sheet chart or full sheet chart components. This does not impact Redact's ability to create markups
for these components or the branding process. The Download Marked Up File button can be used to verify markup
application.
l WordArt
l SmartArt
l Embedded documents (email, PowerPoint), images, equations, text boxes, and shapes
You can apply a black redaction to these objects, by doing the following:
1. Navigate to the Documents tab and select a spreadsheet document from the list that has already been pre-
pared for Redact.
2. Click on the Open Original Native button.
A new browser window opens where you can click Native to view the native spreadsheet document or click Ori-
ginal Native Text to see the document before it was prepared for Redact.
l To download a copy of the native file without any markups, click on the document actions menu in the Viewer,
hover your cursor over the Download option, and then select Document native.
l To download a copy of a native spreadsheet file with the markups applied in the Native Viewer, click on the
Download Marked Up File button.
l To export multiple documents that have markups applied, run a production that includes these documents and
then export the production set using Import/Export.
Note: 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.
If you would prefer to have markups applied automatically, see Automated PDF markup project.
1. Select the desired markup set in the bottom-left drop-drown menu. If None is selected, you will not be able to
apply markups.
2. Click the Redaction Mode icon. The black redaction tool is the default. Click the drop-down menu to select a dif-
ferent tool. You can select from the following:
l Black - creates a solid black box, like using a black marker. While you draw the box, a gray translucent fill
appears.
l Text - creates a white redaction box with black text. The text will fill the box by default. You can right-click
a text box redaction and select Edit to change the text redaction as desired. Alternatively, you can right-
click a text box redaction and select either most recent word or phrase you entered while editing a redac-
tion or if you have never edited or created a text redaction before, you can select Redacted instead. The
system admin determines which text options are available.
l White - creates a solid white box with a gray border. The gray border won't be printed or produced.
3. Draw the redaction boxes across the sections of the page you want to redact. You can draw in any direction.
The redaction is applied to the PDF file.
1. Select the desired markup set in the bottom-left drop-drown menu. If None is selected, you will not be able to
apply markups.
2. Click the Highlight Mode icon and select a color from the drop-down menu. Blue is the default color.
3. Draw the highlight across the sections of text you want to highlight.
The highlight is applied to the PDF file.
1. You can use either of the following methods to select highlights or markups:
l Hold down on Ctrl on your keyboard, and left-click on each highlight or markup you wish to reject.
l Right-click on a markup after selecting any other highlight or markup you would like to reject.
2. Do either of the following to reject the selected markups:
l If you right-clicked on a markup, select Reject from the right-click menu.
The selected markups are rejected.
l Otherwise, press the Delete key on your keyboard and click Reject in the modal.
The selected markups are rejected.
l To download a copy of the native file without any markups, click on the document actions menu in the Viewer,
hover your cursor over the Download option, and then select Document native.
l To download a copy of a native PDF file with the markups applied in the Native Viewer, click on the Download
Marked Up File button.
l To export multiple documents that have markups applied, run a production that includes these documents and
then export the production set using Import/Export.
Name Description
Details Displays the location (page number for PDF files or cell name for spreadsheet files) of the markup that
was created, reverted, or accepted/rejected. If the markup was applied to a chart, CHART displays
instead of the location.
Created On Displays the date and time that the action took place.
Created By Displays the name of the user who took the action.
Document Displays the name of the document where the action took place.
Action Displays the type of action taken by the user.
Note: The placed markups in each report are calculated by taking the total number of markups placed within the
selected date range and subtracting the number of markups were both created and reverted within that date range.
Note: We do not recommend applying external markups to a document unless it will only receive external markups.
If a document has external markups, it can no longer receive any other kinds of markups in Relativity to prevent pro-
duction errors.
1. The case team identifies a set of PDF and spreadsheet files that are too big to display in the Viewer.
2. A saved search that includes only these large document files is created.
3. Add the documents to the Redact External Markup tab by checking the Redact Document Warnings and Can-
not be Redacted in Native Viewer field options. To learn more, see Adding documents to External Markups
tab.
4. Reviewers are granted access to the Redact External Markups tab.
5. Reviewers select the markup set that they used to apply any redactions to the documents.
6. Reviewers download documents to apply markups to externally.
7. Markups are placed using your tool of choice such as Microsoft Excel or Adobe Acrobat. If you are applying
markups using Excel, please note that applying a Fill Color over data does not safely redact that information.
Instead, any data in the cells you wish to redact should be removed:
a. Click on the cell you wish to redact.
b. Press Delete on your keyboard.
c. Right-click the cell and select Fill Color with Black selected.
8. The documents with external markups are re-uploaded to Relativity and ready for production.
l By default, projects will run with the eng code which causes English to be the only supported language.
l If there is a chance that multiple languages could be combined together in the documents, you can ensure the
languages receive the appropriate markups by adding a + between each language code. For example, entering
spa+eng causes Spanish and English to receive markups by a project.
l Language codes are prioritized from left to right so the left-most code will be given the highest priority.
1. Navigate to the Redact Project Status tab.Projects are sorted from newest to oldest based upon when they
were created.
Note: Projects are sorted from newest to oldest based upon when they were created.
2. Optionally, apply filters to the Project Type, Name, and/or Current Status column to determine what project
information displays.
3. Optionally, you can click on the name of a workspace to navigate there and edit a project as needed.
Note: Avoid using long text fields for Redact reports because they may result in a malfunctioning .csv file.
After choosing the fields for the report, they can re-ordered. The first field selected will be the left-most column in the
report, while the bottom will be the right-most column.
Note: Regardless of which report you select, markup and document fields are available to be added to the
report. The selected fields may display differently depending on which report you select.
5. Once all of the desired fields have been added to the Fields Included in Report section, click Generate Report.
The user that generated the report receives a copy via email. A Markup Report will have the following naming
convention: RedactionLog_<WorkspaceArtifactID>_<YYYY-MM-DD> and a Document Report will have the fol-
lowing naming convention: DocumentLog_<WorkspaceArtifactID>_<YYYY-MM-DD>.
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.
Additionally, you can create convenient text redaction options by entering them in the Predefined Redaction Text
field and clicking Add. These options will be displayed in the Text Redaction modal when the Text option is selected in
the right-click menu.
If it is no longer needed, a Predefined Redaction Text option can be removed by clicking the red X in that option's row.
Markup annotations
There are three types of markup annotations:
Non-markup annotations
Pop-up annotations typically do not appear by themselves and have a parent property which is associated to a markup
annotation.
If no parent association is defined for a pop-up annotation, the Viewer may use the pop-up annotation's content as the
text for the annotation.
1. Select the desired markup set in the bottom-left drop-drown menu. If None is selected, you will not be able to
apply markups.
2. Click the Redaction Mode icon. The black redaction tool is the default. Click the drop-down menu to select a dif-
ferent tool. You can select from the following:
l Black - creates a solid black box, like using a black marker. While you draw the box, a gray translucent fill
appears.
l Text - creates a white redaction box with black text. The text will fill the box by default. To change the font
size, keep the redaction box selected and click the Font Size drop-down menu, and then select a new
font size from the drop-down menu. You can right-click a text box redaction and select Edit to change the
text redaction as desired. Alternatively, you can right-click a text box redaction and select either most
recent word or phrase you entered while editing a redaction or if you have never edited or created a text
redaction before, you can select Redacted instead. The system admin determines which text options are
3. Draw the redaction boxes across the annotation you want to redact. You can draw in any direction.
Note: You cannot redact part of an annotation. If a redaction is applied to an annotation, the entire annotation
will be redacted.
The redaction is applied to the PDF file.
1. Select the desired markup set in the bottom-left drop-drown menu. If None is selected, you will not be able to
apply markups.
2. Click the Redaction Mode icon. The black redaction tool is the default. Click the drop-down menu to select a dif-
ferent tool. You can select from the following:
l Black - creates a solid black box, like using a black marker. While you draw the box, a gray translucent fill
appears.
l Text - creates a white redaction box with black text. The text will fill the box by default. To change the font
size, keep the redaction box selected and click the Font Size drop-down menu, and then select a new
font size from the drop-down menu. You can right-click a text box redaction and select Edit to change the
text redaction as desired. Alternatively, you can right-click a text box redaction and select either most
recent word or phrase you entered while editing a redaction or if you have never edited or created a text
redaction before, you can select Redacted instead. The system admin determines which text options are
available.
l White - creates a solid white box with a gray border. The gray border won't be printed or produced.
3. Draw the redaction boxes across the annotation you want to redact. You can draw in any direction.
Note: Attachments that are redacted will be removed completely from the document. If you would like to view
the file with the attachment removed, click on the Download Marked Up File button or run a production that
includes the PDF document.
The redaction is applied to the PDF file.
Note: The provided examples are meant to be a starting point for your Redact projects. They are not guaranteed to
find and apply markups to every piece of sensitive information. We recommend double-checking documents before
production to ensure that all sensitive information is properly redacted.
l birth
l birth date
l birthday
l date of birth
l born
IPv4 This regular expression will match and gen- \b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b
eral IPv4 addresses.
IPv6 This regular expression will match and gen- \b([\d\w]{4}|0)(\:([\d\w]{4}|0)){7}\b
eral IPv6 addresses.
Pre-OCR or This regular expression does not find \A
HOCR matches or apply markups. Instead, you can
images use this regular expression to begin running
without any OCR for a large project without needing to cre-
redaction ate other rules first. You can then add the
rules rules for matching terms while the OCR is run-
ning at your convenience.
Redact text \bTerm\s?(?<redact>[\d]{9})
after key
term
\b((4\d{3}|5[1-5]\d{2}|2\d{3}|3[47]\d{1,2})[\s\-]?\d{4,6}[\s\-]?\d{4,6}?([\s\-]\d
{3,4})?(\d{3})?)\b
This regular expression matches the following samples.
Visa
l 4532613257548007
l 4716563756075937
l 4929038415234561233
l 4718 4123 4142 4124
l 4716-5637-5607-5937
MasterCard
l 2720-9928-3988-7281
l 2720992839887281
l 5461718001676921
l 5489790994470834
l 5489 7909 9447 0834
l 5489-7909-9447-0834
American Express
l 372714876128394
l 346781676352683
l 376506566639896
l 3765 065666 39896
l 3467 816763 52683
l 3400 0000 0000 009
l Maine 211274450
l Massachusetts/Rhode
Island 211370545
l Metro DC/Maryland/Vir-
ginia 054001725
l New Hampshire
011400071
l New Jersey/Delaware
031201360
l New York – Metro NYC
or former Commerce
customers 026013673
l New York – Upstate
NY or former Banknorth
customers 021302567
l North Carolina/South
Carolina 05390219
l Pennsylvania
036001808
l Vermont 011600033
US ABA This regular expression can \b(0[0-9]|1[0-2]|2[1-9]|3[0-2]|6[1-9]|7[0-2]|80)\d{7}\b
Routing be used to apply markups to
Transit Num- an ABA routing number.
ber
SWIFT This regular expression can \b[A-Z]{6}[A-Z0-9]{2}([A-Z0-9]{3})?\b
Code be used to redact SWIFT
codes for payment instruction
information.
IBAN Codes This regular expression can (?:(?:IT|SM)\d{2}[\w]\d{22}|CY\d{2}[\w]\d{23}|NL\d{2}[\w]{4}\d
be used to redact IBAN codes {10}|LV\d{2}[\w]{4}\d{13}|(?:BG|BH|GB|IE)\d{2}[\w]{4}\d{14}|GI\d{2}
for payment instruction inform- [\w]{4}\d{15}|RO\d{2}[\w]{4}\d{16}|KW\d{2}[\w]{4}\d{22}|MT\d{2}[\w]
ation. {4}\d{23}|NO\d{13}|(?:DK|FI|GL|FO)\d{16}|MK\d{17}|
(?:AT|EE|KZ|LU|XK)\d{18}|(?:BA|HR|LI|CH|CR)\d{19}|
(?:GE|DE|LT|ME|RS)\d{20}|IL\d{21}|(?:AD|CZ|ES|MD|SA)\d
{22}|PT\d{23}|(?:BE|IS)\d{24}|(?:FR|MR|MC)\d{25}|
(?:AL|DO|LB|PL)\d{26}|(?:AZ|HU)\d{27}|(?:GR|MU)\d{28})
l 40.571.278
l 45.855.200
l 80.933.831
Australia Tax The Australian tax file number is typically 8-9 digit numbers
File Number preceded by TFN. Other indicators in the government website
may say things like payee's tax file number or tax file number.
Spreadsheet Projects
\b[\d]{3} [\d]{2} [\d]{4}|([\d] ?){3}[\—
\-_] ?([\d] ?){2}[\—\-_] ?([\d] ?){4}\b
After opening a document in the Viewer, click the Redact Markup Navigator icon in the bottom-left to expand the
Redact Navigation card. Each markup is displayed in its own row that provides additional information described below.
Optionally, you can click the Approve icon to approve a markup or click the Reject icon to remove the markup from the
document as part of your quality control process.
If you want to approve or reject several markups at once, select the desired markups manually or choose All from the
Checked drop-down menu, and then click Accept or if you want to reject all markups, click Reject.
While viewing the Redact Navigation card in the Image Viewer, you can download a CSV report to your workstation
Column
Description
Name
Accept/Reject This optional column allows you to review markups that have already been applied. The
Accept/Reject column can be in one of the following states depending on which icons have been
selected:
l Not Set - Neither approved or rejected have been selected for this markup. The applied
markup function normally.
l Approved - If selected, the applied markup has been approved for production and will func-
tion normally.
l Rejected - If selected, the applied markup will be removed.
Location Displays the cell name where the markup is located. Optionally, you can click on the cell name to
navigate to the location of this markup.
Markup Scope Displays what each markup obscures as selected when creating the project.
Markup Sub- If the markup is a highlight, this column displays the name of the color used in the highlight. If the
type markup is a redaction, this column display the name of the redaction type.
Markup Text Displays the text in the markup for text redactions.
Markup Type Displays whether the markup is a highlight or redaction. Optionally, you can click on the Markup
Type to navigate to the markup within the document.
Origin Displays one of the following options to indicate where a markup came from:
Click View text to see the extracted text from the current document in a pop-up window.
Click View hocr to see the text from the OCR document in a pop-up window.
After running an automated project, it is a best practice to review documents and ensure that all sensitive information
has been properly redacted or highlighted. To aid you in this process, the Viewer has Quality Review. Click on the
Redact Spreadsheet Markup Navigator icon and ensure that the Quality Review icon is selected.
Quality Review contains a view, Image Quality Review, that allows you to compare the number of matches in the
extracted text of a document as determined by the rules in the project you ran versus the number of markups applied
to the document. You can use this view to find discrepancies and ensure that markups are applied to all of the correct
information before production.
The following columns display in Quality Review:
Column
Description
Name
Type Displays whether each rule was a regular expression or word/phrase.
Rule Displays the name of the rule in a previously ran project that has a match either in the normal text or
extracted text of the document.
Note: By default, a document has up to 55 minutes to finish processing before Redact skips that document
and tries to run the remaining documents in the project. The length of time before a document times out can
be adjusted with the RedactProjectDocumentProcessingTimeOut instance setting. To learn more about
this instance setting, see Adjusting Redact time out length.
We are providing directional estimates on project performance to help you gauge the duration of a project run.
Consider these project estimates more as directional rather than precise because project performance may vary
across other variables (file size, number of rules, pages per document, etc).
To help you determine the size of a project, you can use the Tally/sum/average mass operation. Select the Relativity
Image Count field for the mass operation and include all of the documents in the saved search that the project will
utilize to generate an estimate. To learn more, visit Tally/sum/average.
Image 1 32
2 71
3 105
Spreadsheet 1 700
2 1,089
PDF 1 170
2 250
l Documents prepared—Displays the number of documents that have been added to the project run for poten-
tial markup.
l Documents completed—Displays the number of documents that have been reviewed and had markups
applied according to the project rules.
l Progress bar—Displays the progress of the run. The light blue bar represents the amount of Documents pre-
pared and the dark blue bar represents the amount of Documents completed.
l Time elapsed—Tracks the amount of time that has passed while the project is running.
l Current status—Once a project begins running, a status bar will display to show what task is being completed.
Once multiple tasks are completed, you can click on the bar to view previous tasks.
l Documents Marked Up—Displays the total number of documents that have had markups applied to them by
this project's run. Clicking this tile will navigate you to the Documents tab where a saved search that contains all
of the documents that have had markups applied by this project.
l Markups Placed—Displays the total number of markups that have been applied to documents by this project's
run. Clicking this tile will navigate you to the Documents tab where a saved search that contains all of the doc-
uments that have had markups applied to them.
l Documents to review—To help you quality control the automation process, Redact will compare the number
of matches in the extracted text of a document to the number of markups applied to it and if there are more
matches than markups applied, the document will be flagged. This tile tracks the number of flagged documents
where there is a discrepancy between those two tallies. Clicking on this tile will navigate you to the Documents
tab where a saved search that contains all of the documents that have less markups than there are matches in
the extracted text.
l Documents with warnings—Displays the number of documents that encountered a warning. These warnings
do not affect the project's run or prevent other documents from having markups applied. Clicking this tile will
download a .CSV file to your workstation that contains a list of document warnings and any error messages.
l History—This section contains information and statistics about the most recent project run.
l Docs Processed—The number of documents in the saved search that meet the project type and are eli-
gible to receive markups. For example, if you are running a spreadsheet markup project, only spread-
sheet documents would be tallied for this field even if other document types are included in the saved
search.
l Docs Marked Up—The number of documents in the saved search that contain at least one hit based on
the project rules.
1. Navigate to the Documents tab, click on the Saved Searches browser icon, and click Create New Search.
2. Click Add Condition.
3. In the field list, select the desired Blackout field.
4. Click the Add Condition button and select the same Blackout field.
The filter modal displays.
5. Select the desired markup set options to determine which documents will display in the results of the saved
search.
6. Click the right arrow icon to move the selected markup set options to the right table and click Apply.
7. Click Apply again.
8. Optionally, repeat steps 2-7 to add additional fields as needed.
9. Click Save & Search or Search.
The Document list is updated to show only documents that fit the condition criteria.
Note: The contextual search returns hits on comments and chart labels content in spreadsheet documents. These
content types cannot receive markups using Find and Redact. To apply a markup to a comment or chart label, see
Manual markups with spreadsheet files.
Note: A message displays when markups could not be applied to any results because it is either a comment or
chart label. Locate results that did not receive a markup by refreshing the document and then searching for the
same term again. Any terms that were previously selected and did not receive a markup are returned in the results.
Note: The sampling feature requires the Use Sampling Admin Operations permission. See Workspace security on
page 573.
5. Click Save. The sampling icon is now available on the object as long as you are assigned the Use Sampling
Admin operation permission.
l Fixed size - creates a randomized sample set of a specific number of items from the entire item list. See Creat-
ing a fixed size sample set on the next page.
l Percentage - creates a randomized sample set of a specific percentage of items from the entire item list. See
Creating a percentage sample set on the next page.
l Statistical - creates a randomized sample set of a size based on statistical sample calculations, which determ-
ines how many items reviewers need to address in order to get results that reflect the entire data set as pre-
cisely as needed. See Creating a statistical sample set on page 543.
Note: If you select a sampling type you previously applied in the same workspace, Relativity automatically pop-
ulates the related settings field(s) with your last value(s).
Clicking Sample on the sampling drop-down menu applies your sampling settings to the item list and creates the
randomized sample set.
The sample summary bar displays the sampling type you applied and a count of the sample set out of the total number
of items.
l Click Clear Sample on the sample summary bar menu to clear the sample. The sample set you create persists
on the list of items until a user clears it. This includes while updating search conditions, switching and navigating
within browser panels, including adding in relational items, and navigating to other tabs.
l The Sampling button is disabled when a related items option is selected from the Related Items drop-down
menu or a search. If you have applied sampling and select a related items option from the Related Items drop-
down menu, the sampling is removed from the list.
Note: The Save Search icon is also disabled for sampling results because the sample results are generated
randomly. Clearing a sampled list of items re-enables the Save Search icon.
5. Click Sample.
Note: We recommend that you only use the statistical sampling type on data sets that are large enough to return a
reliable statistical sample. If a data set contains fewer than 300 items, you may want to consider using a different
sampling type.
To create a sample set size based on statistical confidence and margin of error specifications:
Note: Relativity Scripts are a tool to access and modify data stored in Relativity SQL databases. Not all data is
available in SQL, and data currently in SQL may be migrated to other storage systems. The recommended
integration mechanism is to use APIs/Servicesinstead of scripts to avoid future migration or interruption.
You should only use scripts when an appropriate API is not available. Relativity will add new and updated APIs over
time - review the available APIs periodically to determine if you can replace a script with an API or REST service
call.
Caution: Changes to SQL fields executed by Relativity Scripts do not produce Audit logs.
Only users who are members of groups with the appropriate permissions can write scripts. System admins have
permissions to preview, edit, and create scripts.
If a script is locked, it appears as read only, and you can't edit it. If a script is unlocked it's available for editing.
The following table represents the script permissions allowed for each group.
Note: If you use a Relativity script in a custom development project, it is recommended to make a copy of the script
and use the copied script in your project. Software updates may modify the scripts provided by Relativity, which
could cause unintended results if you use the Relativity-provided scripts directly in your custom development pro-
jects.
When upgrading your environment, the unique script key is referenced to determine if an update is required. If so, this
is performed automatically.
3. In the Script Body field, enter values for each script component and click Save.
If any errors occurred in the script body, you will see an error message identifying the line and position of the
problematic text. Relativity will not save the new script until you address the errors.
l Script Type - select Select from Script Library to choose from a list of predefined Relativity scripts.
The Script Library tab is created when Relativity is deployed. Note that this is the only option available for
the Script Type field if the AllowAddOrEditScripts instance setting is set to its default value of False.
l Relativity Script - select the script from the script library.
l Relativity Applications - associates the script with an application created on the Relativity Applications
tab. All existing applications are available when you click the ellipsis. This is only available for those who
have the Manage Relativity Applications permission under Admin Operations. For information on
Caution: Changes to SQL fields executed by Relativity Scripts do not produce Audit logs.
1. Create or select a group of Relativity scripts that you would like to add to a script group . They must all share the
same Category. You can also create new categories. See Creating a new workspace script on page 547.
2. Create a new external tab that links to your script group. See Creating and editing tabs on page 620. If the cat-
egory name contains spaces, replace the spaces with the + sign.
a. Copy the script category’s Report Group URL to your clipboard or Notepad. For example, if you are cre-
ating a script group for all scripts whose category is Case Functionality, open any script belonging to this
category. Then, copy the entire path listed in Report Group URL.
Note: Linked scripts can only be members of a script group as an admin tab. You can't create script groups of linked
scripts within a workspace.
34.1 Filters
You can use filters to limit the documents or items that appear in item lists on Relativity tabs and pop-ups. When you
enable the filters for an item list, you can set criteria on single or multiple fields so that only matching documents or
items appear in the view.
Filters query across the searchable set of documents in the active view to return your results. Relativity supports
multiple filter types so that you can choose the best format for different field types. See the Searching Guide for more
information.
34.5 dtSearch
Available on the Documents tab, you can use dtSearch's advanced searching functionality to run queries with
proximity, stemming, and fuzziness operators, along with basic features such as Boolean operators and wildcards.
System administrators can create a dtSearch index for a specific subset of documents in a workspace, and then
assign security to it. They must manually update indexes when you modify the document search sets used to create
them. See the Searching Guide for more information.
With the search condition option, you can build queries using the same condition options available for saved searches.
You can click Save as Search on the Documents tab to create saved searches based on the criteria defined for
keyword searches, dtSearches, Analytics, or the search conditions option. See the Searching Guide for more
information.
You can also use the search bar to view recent searches. Click in the search bar to see up to 10 of the most recent
searches from any index in descending order, with the most recently run search first.
Select any search from the list to run that search. To clear the list, click Clear Recent Searches.
l
Note: It's recommended to update security permissions for document folders with a large number of doc-
uments during non-business hours to avoid delays in your document review project.
l If the Lockbox feature is enabled via the EnableCustomerLockbox instance setting, 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. If you need more information on this feature, please contact Support.
l Instance permissions - these permissions pertain to system admin groups and are used to control access to
designated system admin objects.
l Workspace permissions - these permissions are associated with user groups added to a particular work-
space. If a user group is not added to a workspace, it implies that users within that group have no access to that
workspace.
You can employ object-level security to restrict entry to specific documents or items within the workspace. These
objects encompass various components such as workspaces, documents, fields, and other elements within the
system.
Tailoring access to these objects can be done on an individual user or group basis. User access determines the extent
of permissions and actions a specific user can perform. Group access simplifies the management of permissions for a
set of users in the same category. By managing user or group access, you can determine who is authorized to view,
edit, or carry out specific actions on the objects within the system.
Furthermore, objects can have document-level or field-level permission configurations. Document-level permissions
allow you to control access to individual documents based on user roles or specific criteria. Similarly, field-level
permissions offer the ability to regulate access to particular fields within a document. You can set restrictions on who is
permitted to view or modify specific fields based on user or group permissions.
Note:
The Manage Object Types permission grants group members the ability to:
l Create a new tab for a new object type when adding the new object type.
l Automatically gain view, add, edit, delete, and secure permissions for all newly created object types.
l Automatically gain tab visibility for newly created tabs.
Note: For some object types, options will be missing from the above list of permissions. For example, admin-
istrators cannot set permissions to 'None' for the 'Users' or 'Views' objects, because it will make Relativity
unusable.
Note: Users must be assigned to the following two groups in order to have full system administration access:
1. System Administrators - This grants access to all admin-level permissions, such as ARM, queue management,
users, and groups tabs.
2. <Customer Name> Admin Group - This gives the user permissions to access all workspaces in the instance,
unless the workspace was migrated through ARM or Migrate without the group being properly mapped first.
35.2.0.1 Features
The Features tab lists all of the features and their associated permissions from the other three tabs. You can enable
and disable permissions at the feature level using this tab.
Toggle Key settings:
l
—Enabled
l
—Disabled
Permission settings
l
—Disabled
l
None —denies users access to the object.
l
View —view the object. This is the lowest level object permission.
l
Edit —edit and view the object.
l
Delete —delete, edit, and view the object.
l
Add —add new objects. This icon turns blue when the setting is unsaved; once you click Save, the blue icon
becomes grey. This icon turns green when you give users this permission both when the setting is unsaved and
saved.
l
Edit Security —grants users the ability to edit the security of objects. This icon turns blue if you click twice
indicating a not applicable status.
You can apply system admin permission settings to any of the following objects in the Object Security tab:
Note: Only system administrators can edit the Client and Matter for a workspace. In addition, the Errors tab is only
available to system administrators.
l License - access to the License tab. Only full system admins can edit license information.
l Resource File - access to the Resource files tab.
l Resource Pool - access to the Resource pools tab.
l Servers - access to the Server tab.
Note: If you see the Workspace Processing Settings item listed in the object security section of your console, note
that this represents an RDO for which there is no front-end implementation. It stores the Invariant StoreID and Data
Grid settings for the workspace, but it provides no functionality, and it controls nothing.
Note: Granting tab visibility to a group without view permissions for the object allows users to view the tab but pre-
vents them from taking action. Granting object permissions to a group without tab permissions for the object
restricts users from completing required tasks.
Note: The following tabs are secured by default and should not be modified. Please contact Relativity Sup-
port if you need to modify these tabs.
Note: Users will have access to the Workspaces tab even without the View Admin Repository permission.
l View Audits - access to the ability to view audit records on the View Audits tab.
Note: If you are using RelativityOne, the following admin operations are secured by default and should not be
modified. Please contact Relativity Support if you think you need to access this functionality.
l Case Metrics
l Staging Explorer
l Workspace Portal
l Processing Administration
l Production/Branding Queue
l ARM
1. Group - select any group in your Relativity environment from the Group drop-down menu. Click Run to see a list
of all system admin permission settings for that group.
2. Preview - displays the Script Body that defines the selected group's permission settings.
3. Run - generates Group Permissions Report on the selected group.
4. Export to File - click Go to export a .CSV file of all the selected group's system admin permission settings.
l Features changes—lists the features that were changed and how they were changed. Changes at the
granular level may affect the status of the feature setting, so review this information carefully.
l Granular permissions changes—lists the changes made at the granular permissions level, including
those resulting from feature changes or direct edits at the granular permission level.
l Preview—preview currently applied security settings for a group. See Preview Security for more information.
l Add/Remove Groups—opens the Add/Remove Groups dialog to grant admin access to groups. See Add/Re-
move Groups below for more information.
Note: A system admin is the only user able to grant other users membership into the System Administrators group.
Any user who is not a member of the System Administrators group is unable to add themselves to any group.
l Available Groups—lists groups in your Relativity environment not yet granted access to the workspace.
l Groups with Admin Permissions—lists groups granted access to admin permissions.
You must add a group to the Groups with Admin Permissions column to grant the group admin security privileges.
Note: Adjusting the settings for individual permissions requires accessing their respective source tabs (Object
Security, Tab Visibility, Admin Operations). Editing them from the Features tab is not possible.
Setting permissions at the feature level is intuitive and simplifies the management of permissions within Relativity.
With one click, the necessary permissions can be enabled or disabled for a particular feature.
35.3.2.1 Considerations
Keep these factors in mind when setting Feature permissions:
l Granular permission settings on the Object Security, Tab Visibility, and Admin Operations tabs are the primary
source of truth and propagate to features listed on the Features tab. Changes to these permissions from those
tabs will also update in the corresponding features.
Scenario:
If you remove the View Admin Repository capability on the Admin Operations tab, it will be disabled within its
corresponding Cost Explorer feature on the Features tab.
Therefore, if all granular permissions are enabled for a feature, the feature's toggle is enabled. If any of the granular
permissions is disabled for a feature, the feature's toggle is automatically disabled.
l Disabling a feature on the Features tab disables its associated granular permissions for that feature. However,
if a granular feature is part of another enabled feature, then it will remain enabled (blue check mark) on the dis-
abled feature’s See Details panel.
Scenario:
The Archive and Restore (ARM) and Cost Explorer features are enabled, and they share the granular permission of
View Admin Repository. If you disable the Archive and Restore (ARM) feature, the View Admin Repository setting
remains enabled (blue check mark) on the See Details panel of Cost Explorer because they are included in the
enabled Cost Explorer feature.
l
Current state of each granular permission for the feature. A blue check mark indicates the selected
group has permission to use this feature (enabled). A red circle with a slash indicates the selected
group does not have permission to use it (disabled). The state permissions may change based on the
toggle key setting.
l
None —denies users access to the object.
l
View —view the object. This is the lowest level object permission.
l
Edit —edit and view the object.
l
Delete —delete, edit, and view the object.
l
Add —add new objects. This icon turns blue when the setting is unsaved; once you click Save, the blue icon
becomes grey. This icon turns green when you give users this permission both when the setting is unsaved and
saved.
l
Edit Security —grants users the ability to edit the security of objects. This icon turns blue if you click twice
indicating a not applicable status.
You must grant tab visibility independent of permission settings for users in a group to access a permitted tab. You can
make any tab visible by selecting the checkbox in the list. To make all sub tabs visible, click on the parent tab and click
Select all (#).
Note: Do not use tab visibility as a sole method of preventing security permissions.
Note: If you assign admin permissions to a user group by copying permissions from system admins, you must unset
and reset the View Workspace permission to allow the user group to edit the workspace.
Note: 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.
l Features
l Object security
l Tab visibility
35.4.2 Features
The Features tab lists all of the features and their associated permissions from the other three tabs. You can enable
and disable permissions at the feature level using this tab.
Toggle Key settings:
l
—Enabled
l
—Disabled
Permission settings:
l
—Enabled
l
—Disabled
l
None —denies users access to the object.
l
View —view the object. This is the lowest level object permission.
l
Edit —edit and view the object.
l
Delete —delete, edit, and view the object.
l
Add —add new objects. This icon turns blue when the setting is unsaved; once you click Save, the blue icon
becomes grey. This icon turns green when you give users this permission both when the setting is unsaved and
saved.
l
Edit Security —grants users the ability to edit the security of objects. This icon turns blue if you click twice
indicating a not applicable status.
Not all item-level rights apply to select objects. Some object permissions require corresponding tab visibility or
browser permission. For example, a group with all item-level rights assigned for the Field object can only add, edit,
delete, or edit security for fields with access to the Fields tab.
Note: This list contains objects related to core functionality, and additional objects may be described in the
documentation for individual features. This list also does not include custom objects you may find in your
environment.
l Alias—a textual representation of an author. Aliases are identified during the Analytics name normalization
operation.
l Analytics Categorization Result—an object that displays the results of an Analytics categorization set.
l Analytics Categorization Set—a group of parameters used for gathering example documents that Analytics
uses as the basis for identifying and grouping other conceptually-similar documents.
l Viewing, editing, deleting, or adding Analytics categorization sets, or editing security of Analytics cat-
egorization sets requires access to the Analytics Categorization Set tab.
l Analytics Categorization Set Build History—a record of the historical actions and changes made during the
process of creating or updating a categorization set for use in analytics. This history may include information
about changes to categories, mappings, and other settings related to the categorization set.
l Analytics Category—an object in Analytics that define the categories specific to your analytics set.
l Viewing, editing, deleting, or adding Analytics categories for Analytics categorization sets, or editing
security of Analytics categories requires access to the Analytics Categorization Set tab.
l Analytics Example—a document that Analytics uses to run the Analytics set against to set a baseline.
l Analytics Index
l Search index permissions must be kept in sync with permissions on the Analytics Index object.
If a user has view permissions to Search Index, but no permissions to Analytics Index, they can still
access Index Search functionality in the item list and in the viewer. If a user has full View/Edit/Add/Delete
security permissions to an Analytics Index, but does not have permissions for Search Index, they will not
be able to View/Edit/Add/Delete Analytics indexes.
l Analytics Profile—a group of parameters used for specifying an Analytics Index's dimensions, concept noise
words, dtSearch noise words, and filter configurations.
l Editing, deleting, or adding Analytics profiles, or editing security of Analytics profiles requires access to
the Analytics Profiles tab.
l Application Field Code—an identifier assigned to a specific field within an application. The field code is used
to reference and manipulate the field's data.
l Audit Dashboard—a visual display that provides an overview of audit-related information, including tracked
activities, user actions, and system changes. The audit dashboard allows users to monitor and analyze audit
data for compliance and security purposes.
l Audit Workspace Setting—a configuration within a Relativity workspace that defines how audit-related activ-
ities and changes are tracked and recorded. This setting determines which actions are logged and the level of
detail captured in the audit trail.
Note: Use the document Edit permission to tag documents with workspace coding values using lay-
outs. Do not assign coding users rights to edit fields or edit layouts. Use the Field edit permission,
along with access to the Fields tab, to edit field properties such as changing a fixed length text field
from 255 to 320 characters.
l Domain—the name of the business or organization on the internet. For example, “@company.com” in the
email address “jsmith@company.com” is the domain for that company email address.
l Entity—the individuals or entities who own or facilitate the data found in the data sources.
l Group members can view, add, edit, and delete the entities used for Relativity Processing, Legal Hold,
and Collection, and Analytics.
l Event Handler—the name of the assembly that helps facilitate the completion of document review and various
other functions in Relativity by applying custom business logic to corresponding user actions.
l Field—the Relativity entity used to store document metadata and coding values within Relativity.
l Add Field Choice By Link—exposes the Manage link option on choice fields, allowing group members
to add new choices to a field on a layout.
l Editing, deleting, sorting, or adding fields, or editing the security of fields requires access to the Fields
tab.
l Field Category—a grouping or classification of related fields within a workspace. Field categories help organ-
ize fields based on their purpose or functionality, making it easier to manage and work with a large number of
fields.
l Filter Set—a predefined set of criteria used to filter and narrow down data displayed in views and reports. Filter
sets allow users to quickly apply specific filters to focus on relevant information.
l Folder—the name of the container of documents in Relativity that are arranged in a hierarchy in the folder
browser.
Note: You can customize permissions for individual child folders. This does not change the per-
missions of a folder's parent, but it can change the behavior of a folder's children, if you configure the
children folders to inherit permissions from their parent.
Note: Changing root folder permissions during import is not a supported workflow.
l Job History—the Job History tab in the Integration Points object, which provides information the history of
import and export jobs run through Integration Points.
l Job History Error—the Job History Errors tab in the Integration Points object, which provides information
errors that occurred during import and export jobs run through Integration Points.
l Imaging Profile—the name of the profile that controls the settings used to image a group of documents.
l Editing, deleting, or adding imaging profiles, or editing security of imaging profiles requires access to the
Imaging Profiles tab.
l Imaging Set—the profile and saved search containing the documents you want to image.
l Editing, deleting, or adding imaging sets, or editing security of imaging sets requires access to the Ima-
ging Sets tab.
l Imaging Warning—a notification or alert generated during the imaging process that indicates potential issues
or discrepancies that may affect the quality or accuracy of the imaged documents.
l Import/Export Extraction Job—a task that involves extracting and transforming data during the import or
export process. Import/export extraction jobs ensure that data is correctly formatted and mapped for successful
transfer.
l Import/Export Job—an automated task that facilitates the import or export of data between different instances
or systems. Import/export jobs enable efficient data transfer while maintaining data integrity.
l Install Event Handler—the name of the pre or post-install event handler, which is an assembly that runs when
you install them to configure your Relativity environment to support your applications.
l Viewing, adding, or deleting event handlers requires access to the Object Type tab.
l Inventory Filter—the filter applied when inventorying files to view how inventories data affects data in your pro-
cessing set using the Processing application.
l Integration Point—the entity that you create to configure data integrations from third-party systems to Relativ-
ity objects using the Integration Points application.
l Integration Point Profile—the profile that you create and save for future use when running future data import
or export jobs through the Integration Points application.
l Integration Point Type—the integration point type, import or export, that you specify when you create an integ-
ration point to configure data integrations from third-party systems to Relativity objects using the Integration
Points application.
l Layout—the name of the web-based coding form that gives reviewers access to view and edit document fields
and complete specific review tasks.
l Editing, deleting, or adding layouts, or editing security of layouts requires access to the Layouts tab.
l Legacy Sentiment Result—an outcome or classification generated by a sentiment analysis process using pre-
vious sentiment analysis models or methods.
Note: The only proper way to secure the text behind a redaction is to the produce the document that
contains the redacted text. If a group has View rights only to a markup set, not Edit or Delete rights,
and a reviewer in that group loads a document in the Viewer because they have no other way to view
that document, they can actually see the text behind the redaction, in which case that text is not totally
secured.
l Mass Operation—single actions performed on multiple documents or objects at the same time, such as mass
edit, move delete, produce, replace, image, print image, send to CaseMap export file, cluster, and process tran-
scripts.
l Viewing, adding, or deleting mass operations requires access to the Object Type tab.
l Native Type—a Relativity-supported file type that an admin can import and image; Native Type pertains to the
Native Types tab and list, which an admin references when selecting file types to restrict from imaging.
l Edit—group members to edit the Restricted From Imaging By Default checkbox for native types.
l Delete—group members to remove native types from the restricted list.
l Add—group members to add existing native types to the restricted list.
Note: Even with all Native Type permissions assigned, a user cannot add new native file types. Relativ-
ity is already configured with the native file types that it recognizes.
l Object Rule—permits special or additional functions with user-configurable options. For example, a New But-
ton Override that redirects an object's new button action to another Relativity page or other URL as directed by
the user.
l Viewing, adding, or deleting object rules requires access to the Object Type tab.
l Object Type—the type of object specified when creating a Relativity Dynamic Object. For example, Document
and Workspace are object types.
l Editing, deleting, or adding object types, or editing security of object types requires access to the Object
Type tab.
l OCR Language—determines what language is used to OCR files where text extraction isn't possible, such as
for image files containing text.
l Viewing, editing, deleting, or adding OCR languages, or editing security of OCR languages requires
access to the Processing tab.
l OCR Profile—a saved, reusable set of parameters that you use when creating an OCR set.
l Viewing, editing, deleting, or adding OCR profiles, or editing security of OCR profiles requires access to
the OCR Profiles tab.
l OCR Set—a group of documents defined by a saved search or production to be OCRed based on the settings
defined by the OCR profile.
Note: Productions appear in the viewer by default. There are no permissions for specific viewer
options. To restrict productions from appearing in the viewer for a certain group, set the Production per-
mission to None .
l Production Data Source—saved set of parameters that Relativity uses when running a production.
l Production Information—information records associated with a production during the Staging process of run-
ning a production.
l Placeholder—text or images you can include in a production as a placeholder for removed or forthcoming
information.
l Queue Refresh Trigger—a mechanism within Relativity's Review Center that initiates a process to update the
review queue with the latest information.
l Relativity Application—a customizable collection of Relativity objects that provides improved case and matter
management.
l Viewing, editing, deleting, or adding Relativity applications , or editing security of applications requires
access to the Relativity Applications tab.
l Relativity Export Service Job—a task initiated to export data from the system using the Relativity Export Ser-
vice. This job ensures the accurate and secure transfer of data to external destinations.
Note: If you are using RelativityOne, the following objects are secured by default and should not be modified.
Please contact Relativity Support if you need to modify these objects.
l Agent Type
l Event Handler
l Install Event Handler
l Viewing, adding, or deleting event handlers requires access to the Object Type tab.
l Case Admin
l Batch Sets
l Markup Sets
l Persistent Highlight Sets
l Production Sets
l Scripts
l Case Metrics
l Reports
l Reviewer Metrics
l Dashboard
l Documents
l Entities
l Entities
l Aliases
l Indexing & Analytics
l Structured Analytics Set
l Analytics Profiles
l Repeated Content Filters
l Search Indexes
l Analytics Categorization Set
l Imaging
l Imaging Profiles
l Imaging Sets
l Native Types
l Password Bank
l Lists
l OCR
l Profiles
l OCR Sets
Note: If a user has view access or greater, edit, delete rights, to the workspace object and has view
access to the Workspace Details tab, but does not have permission to View Workspace Details, the
admin operation, the user cannot view the Workspace Details tab.
l Search Indexes
l Object Type
l Fields
l Choices
l Layouts
l Views
l Tabs
l Relativity Applications
l Custom Pages
l History
Note: If a user has view access or greater to the History tab, but does not have permission to View All
l User Status
Note: This list does not reflect custom tabs or customized parent tab configurations that may vary by environment.
Note: If you are using RelativityOne, the following tabs are secured by default and should not be modified. Please
contact Relativity Support if you need to modify these tabs.
l Worker Status
l Processing > Errors
35.4.6 Browsers
In the Browsers section, you control which browsers are visible to a group. Select a browser type to make it visible for
the group.
The following is a list of Relativity browsers:
l Folders
Note: For more information on securing folders, see Relativity object security on page 604.
l Field Tree
l Advanced & Saved Searches
l Clusters
See the Browsers panel on page 725 section for complete details regarding each browser type.
Groups not granted access to any of the available browsers in a workspace see their document list spanning the
whole screen.
l Assign to Entity—gives group members the rights to select and re-assign an alias to a different entity when
using name normalization in Analytics.
l Cluster—gives group members the rights to cluster documents using Analytics clustering.
l Convert—gives group members the ability to convert a large set of documents into HTML5 format for faster
document load times within the viewer.
l Copy—gives group members the rights to copy securable objects such as views and layouts.
l Export to File—gives group members the right to export the contents of a view to a .csv, .xls or .dat file.
l Image—group members can simultaneously send image requests for multiple native files.
l Move—gives group members the right to simultaneously move documents from one or more folders to one tar-
get folder. Mass Move also requires add and delete document rights.
l Merge—gives group members the rights to select and merge multiple entities into a single entity when using
name normalization in Analytics.
l PDF Actions—gives group members the ability to download, create, store, or number PDFs. For more inform-
ation, see Mass PDF permissions
l Print Image—gives group members the right to simultaneously print images from multiple documents.
Note: While the Print Image mass operation may be visible in the security console, it is not available to use in
RelativityOne. Mass printing of images is only available if you revert back to the ActiveX control, which is not
an option in RelativityOne. Instead of mass printing images in RelativityOne, you can use the option to save
an image as a PDF from the document viewer.
l Produce—gives group members the right to simultaneously add multiple documents to a production set.
l Replace—group members can perform a replace operation on multiple documents. Examples include:
l Copying the contents of one text field to another.
l Adding a set string to the beginning or end of an existing field.
l Merging the values of a source field with the values of a target field.
l Process Transcript—group members can process imported transcripts for viewing in Relativity.
l Send To Case Map—group members can send multiple documents to CaseMap.
l Tally/Sum/Average—group members can tally, sum and average the values of any numeric fields. This action
is recorded under the document history.
l Custom mass operations—may appear in this list. They include mass operations that you added to Relativity
or that are available in applications currently installed in your environment.
For more information about mass operations, see Mass operations on page 318.
Note: 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.
l Delete Object Dependencies—grants group members permission to force the deletion of an object, which
includes unlinking associative objects and deleting child objects. The group members must also have per-
missions to delete any dependent child and/or modify associative objects.
l Email Thread Visualization—grants group members permissions to access email thread visualization.
l Export Dashboard—grants group members permission to download a saved dashboard.
l Manage Object Types—permission that grants group members the ability to:
l Create a new tab for a new object type when adding the new object type.
l Automatically gain view, add, edit, delete, and secure permissions for all newly created object types.
l Automatically gain tab visibility for newly created tabs.
l Manage Relativity Applications—group members can associate objects with applications by making the
Relativity Applications field available on create and edit pages for Field, Layout, View, Script, Object Types,
and all other objects compatible with applications. Users with this and Edit permissions for applications are
allowed to lock and unlock an application from editing.
l Modify System Keyboard Shortcuts—grants group members permission to the Manage System Keyboard
Shortcuts button. User groups must also have permissions to see the Workspace Admin and Workspace
Details tab along with the View Workspace Details permissions. This button is located in the Relativity Utilities
console on the Workspace Details page. See Keyboard shortcuts on page 252
Note: If a user group is given this permission they can modify and delete keyboard shortcuts for their group
within a workspace.
l Override Production Restrictions—grants group members permissions to override the setting in the Pro-
duction Restrictions option on the Workspace Details page. The group members will be able to produce doc-
uments that contain conflicts based on these restrictions. See Adding and editing production restrictions on
page 721.
l Use Pivot/Chart—grants group members permissions to use the Pivot grid and chart functions.
l Use Quick Nav—grants group members the ability to search tabs in a workspace using the quick nav feature.
See Quick nav on page 41.
l Use Sampling—grants group members permission to the sampling menu on any object that has the Sampling
field set to Enabled. The sampling menu users can create sample sets of items using a sampling methodology
Note: If a user has view access or greater to the History tab, but does not have permission to View All Audits,
the user cannot view the History tab.
l View Batch Pane—grants group members permission to view the batches associated with a document in the
related items pane.
l View Images Hidden for QC Review—grants group members permission to view all images in an imaging set
with a QC status set to hide images. For more information, see QC Review on page 227.
l View User Status—grants group members permissions to access the User Status tab.
l View User's Personal Items—grants group members permission to click the View Another User's Personal
Items link on the Workspace Details page and modify the View Other's Personal Items console.
l View Workspace Details—grants group members permissions to access the Workspace Details page and the
Relativity Utilities console.
Note: If a user has view access or greater to the Workspace Details tab, but does not have permission to
View Workspace Details, the user cannot view the Workspace Details tab.
Note: If you are using RelativityOne, the following admin operations are secured by default and should not be
modified. Please contact Relativity Support if you think you need to access this functionality.
Note: While Workspace Administrators have extensive control over their respective workspaces, they do not
automatically inherit the full range of system administrator privileges. Non-standard permissions like "New
Document" must be added. Additionally, the "Workspace" permission is initially set only to "View" status.
Note: You can only designate one group per workspace as a workspace admin group.
You can also grant workspace admins permission to alter the security settings of any group.
l RelativityOne Lockbox has granular control that is managed through separate EnableRelativityLockbox and
EnableCustomerLockbox instance settings. This allows for a precise configuration based on your specific
needs.
l Lockbox Bypass report - This script provides an audit trail of any changes made to the EnableCus-
tomerLockbox instance setting, including details such as who made the change and when it occurred.
l Lockbox report - This script provides a list of all workspaces to which an employee of Relativity ODA LLC cur-
rently has access, as well as the name of the group to which the user is linked.
Note: The report does not include the actual names of users. This report may reference Maintenance work-
spaces ("[DO NOT ACCESS]...") to which Relativity maintains access. While this script is focused on auditing
"Relativity ODA LLC" employees, you can create a similar custom script to audit your own employees if
desired.
l A member of Relativity staff is granted access to a customer workspace while Lockbox is enabled.
l The EnableCustomerLockbox instance setting is disabled.
l A user is added or removed from the Security Notifications group. Note that only the person who was added or
removed will receive the email notification - other group members will not be notified.
Note: If the Security Notifications group is accidentally deleted, you can re-add it.
Additionally, if any person with a Relativity email address is added to a group with associated workspaces, the email
address will receive notifications whenever a user is added to or removed from the group.
When any of these conditions are met, members of the Security Notifications group will receive an email notification.
The notification email includes a link to the Security Center, where Relativity workspace access can be revoked if
needed.
l Modify the settings on the tabs as needed. Refer to the Features tab on page 595, Object Security tab on
page 599, Tab Visibility tab on page 601, or Other Settings tab on page 603 sections for specific inform-
ation of each tab.
4. Click Revert All if you need to undo all your unsaved toggle key changes. The features will return to their ori-
ginal toggle key settings.
5. Click Review and Save after modifying settings.
l Features changes—lists the features that were changed and how they were changed. Changes at the
granular level may affect the status of the feature setting, so review this information carefully.
l Granular permissions changes—lists the changes made at the granular permissions level, including
those resulting from feature changes or direct edits at the granular permission level.
7. Click Save to finalize the changes.
Note: To add and remove groups, you must have the Edit Security permission set for the Workspace object and the
Add and Delete permissions set for the Groups object (instance level security).
Note: Copying permissions from one group to another will cause all permissions to be overwritten. This
includes item level security permissions for the target group.
l Preview—preview currently applied security settings for a group. See Preview Security for more information.
l Add/Remove Groups—opens the Add/Remove Groups dialog on which you can search for and add or remove
groups.
l Available Groups—lists available groups in your Relativity environment not yet granted access to the work-
space.
l Groups in Workspace—lists groups granted access to the workspace.
Note: If you are in a Workspace admin group, you must have the instance-level Edit permission to the Group
object to add a group to a workspace.
l Save—saves all permissions changes and applies them to the selected group.
l Revert—discards all unsaved permissions changes and reverts to the group's last saved permissions.
l Cancel—cancels the attempted dialog close or tab change action.
After making security changes on the Object Security, Tab Visibility, and Other Settings tabs, click Save at any time to
apply the selected permissions settings.
Note: Adjusting the settings for individual permissions requires accessing their respective source tabs (Object
Security, Tab Visibility, Other Settings). Editing them from the Features tab is not possible.
Setting permissions at the feature level is intuitive and simplifies the management of permissions within Relativity.
With one click, the necessary permissions can be enabled or disabled for a particular feature.
35.5.3.1 Considerations
Keep these factors in mind when setting Feature permissions:
l Granular permission settings on the Object Security, Tab Visibility, and Other Settings tabs are the primary
source and propagate to features listed on the Features tab. Changes to these permissions from those tabs will
also update in the corresponding features.
Scenario:
If you remove the Edit capability from Imaging Profile on the Object Security tab, it will be disabled within its
corresponding User Imaging feature on the Features tab
Therefore, if all granular permissions are enabled for a feature, the feature's toggle is enabled. If any of the granular
permissions is disabled for a feature, the feature's toggle is automatically disabled.
l Disabling a feature on the Features tab disables its associated granular permissions for that feature. However,
if a granular feature is part of another enabled feature, then it will remain enabled (blue check mark) on the dis-
abled feature’s See Details panel.
Scenario:
l Disabling a feature revokes access to all granular permissions associated with the feature that are not currently
granted as part of a different enabled feature. Therefore, enabling and then disabling a feature will not neces-
sarily return the group to the state it was previously in. Be sure to examine the Review Permissions Changes
dialog to confirm all permissions changes are as expected.
Scenario:
A group has access to two permissions. If you enable a feature for that group which includes those two permissions as
well as two additional permissions, the group will then have access to all four permissions. Subsequently, if you
disable the feature for the group, all four permissions will be disabled for the group (assuming none of the permissions
are part of another enabled feature). The group will not revert to having access to the original two permissions.
Current state of each granular permission for the feature. A blue check mark indicates the selected
group has permission to use this feature (enabled). A red circle with a slash indicates the selected
group does not have permission to use it (disabled). The state permissions may change based on the
toggle key setting.
l
View —view the object. This is the lowest level object permission.
l
Edit —edit and view the object.
l
Delete —delete, edit, and view the object.
l
Add —add new objects. This icon turns blue when the setting is unsaved; once you click Save, the blue icon
becomes grey. This icon turns green when you give users this permission both when the setting is unsaved and
saved.
l
Edit Security —grants users the ability to edit the security of objects. This icon turns blue if you click twice
indicating a not applicable status.
See Object list for a list of securable objects.
To deny a group any access to an object, click the icon. After setting a group's permission level to None, the icon
appears in color .
1. Navigate to the item’s details page, and then click Edit Permissions. For example, to open the details page for
a particular view in a workspace, click the Administration tab followed by the Views tab, and then click the
name of a view in the list. Or, click the icon for an object in a item list view with the Security field added.
2. Click the Overwrite Inherited Security toggle on the Group Management tab to set one of the following
options:
Note: Altering security permissions from overwrite inherited security to inherit security and vice versa may
involve a wait time for 50,000 records or more. If this occurs, a notification appears to inform you of the impact
of the change.
3. If you set Overwrite Inherited Security to ON to modify an object's security, click Add/Remove Groups to
add or remove groups for which you want to set explicit object permissions.
4. Click Edit Permissions for a group to modify the group's object security rights.
5. Select any of the following object permissions to assign to the group:
l
None —denies users access to the object.
l
View —view the object. This is the lowest level object permission.
l
Edit —edit and view the object.
l
Delete —delete, edit, and view the object.
l
Add —add new objects. This icon turns blue when the setting is unsaved; once you click Save, the
blue icon becomes grey. This icon turns green when you give users this permission both when the setting
is unsaved and saved.
l
Edit Security —grants users the ability to edit the security of objects. This icon turns blue if you click
twice indicating a not applicable status.
Note: Not all permissions listed above apply to all objects. The Object Security tab doesn't display the
icon for a permission that doesn't apply.
6. Click Save.
l
Edit - edit and view the folders.
l
Delete - delete, edit, and view the folders.
l
Add - add new folders. This icon turns blue when the setting is unsaved; once you click Save, the
blue icon becomes grey. This icon turns green when you give users this permission both when the setting
is unsaved and saved.
l
Edit Security - grants users the ability to edit the security of folders. This icon turns blue if you click
twice indicating a not applicable status.
9. Click Save.
The folder will display a padlock icon to show that Overwrite Inherited Security has been toggled On for
that folder.
1. Navigate to the workspace Details tab and click on the Manage Workspace Permissions link.
2. On the Object Security tab, you will find a list of objects (documents, items, or other artifacts) within the work-
space. If item-level security is applied to an object, it will be marked with an ‘Item Overrides’ link.
3. Click on the ‘Item Overrides' link to open a new window. From here, the system will redirect you to the item
security page to customize permissions for the chosen item.
Notes:
l The preview security feature does not allow the system admin to monitor the actions of a user in real time. It
only simulates what the user would see.
l The following features do not work with preview security:
l Testing Review Center access
l Testing PI Detect permissions
l Checking out batches
l See Permissions scenarios for more information about how permissions work.
Note: If the user is a member of the System Administrators group, the preview security button is unavailable.
The favorites menu and some options in the user menu are disabled during preview security sessions.
4. Click Exit Preview on the preview bar to close the preview security session and return to the user details.
l View Audit from User Details: The audit lists the User Name, Action, and Timestamp of any preview secur-
ity session. The audit reports the username of the system admin performing the preview security session and
Timestamps for Security Preview Started and Security Preview Ended.
l View Audit from Group Details: The audit lists the User Name, Action, and Timestamp of any preview
security session. The audit reports the username of the system admin performing the preview security session
and Timestamps for Security Preview Started and Security Preview Ended.
l System administrators—have the highest level of administrative rights with broad access to system settings,
configuration, and management functions. Their permissions and rights supersede those of other user roles.
They can control the overall system behavior, user management, security settings, and other administrative
tasks.
Note: Violating the boundary of client domains in a system like Relativity can lead to significant risks and
consequences, affecting data security, compliance, and overall system integrity. Client domains serve as isolated
environments within the system, providing each client with a segregated space to manage their own data and
operations independently.
1. Case Management—investigation templates offer tools to track and manage case-related information, includ-
ing key dates, participants, and case notes.
2. Evidence Tracking—these templates track and help organize evidence which allows investigators to asso-
ciate documents, interviews, and other artifacts with specific cases or subjects.
3. Interview Management—investigation templates may include features to manage document interviews con-
ducted during the investigation, which can involve capturing interview transcripts, tagging key information, and
linking them to the relevant case or subject.
4. Data Analysis—graphs can provide data analysis and visualization which allows investigators to identify pat-
terns, connections, and trends within the collected data.
1. Purpose—they are specifically designed to evaluate large volumes of data or information at the early stages of
an investigation and quickly identify and rank relevant information, assess the merits of a case, and make
informed decisions regarding further actions.
2. Data Volume and Complexity—ECA templates can handle large and complex datasets commonly found in
cases. They offer mechanisms for efficient data ingestion, indexing, and searching across various sources,
such as emails, documents, and electronic records. In contrast, review templates and investigation templates
may not necessarily deal with such extensive data volumes and may have different mechanisms for data organ-
ization and analysis.
3. Time Sensitivity—ECA templates aim to expedite the initial assessment of a case or investigation, taking into
account time constraints and the necessity for rapid decision-making. They strive to pinpoint critical information,
potential risks, and key players early in the process to steer subsequent actions. While review templates and
investigation templates might involve longer timeframes and more intricate procedures to facilitate com-
prehensive analysis and evaluation.
4. Early Case Strategy—ECA templates often incorporate features that allow legal teams to develop an early
case strategy based on the initial assessment. This includes identifying key issues, potential legal theories, and
relevant documents or evidence that may impact the case.
5. Legal Compliance and Privilege Considerations—ECA templates need to address legal compliance require-
ments and considerations for maintaining attorney-client privilege and work product protections. They may
provide features to flag privileged information, conduct privilege review, or track legal holds on relevant doc-
uments. Review templates and investigation templates may have different compliance requirements depending
on the nature of the review or investigation.
l Create a new tab for a new object type when adding the new object type.
l Automatically gain view, add, edit, delete, and secure permissions for all newly created object types.
l Automatically gain tab visibility for newly created tabs.
l control access to individual documents in a workspace. You can review, and potentially change, item level
security settings when adding a group to objects with override security to guarantee that access is appropriately
restricted.
l define what groups or users can view, edit, delete, or perform other actions on individual documents. You can
set permissions at a granular level to guarantee only authorized individuals have access to specific documents.
When the system determines access to an item, it first evaluates the workspace-level permission settings. Then it
takes into account any item-level permission settings. If there's a conflict between item-level permissions and
workspace-level permissions, the system enforces the more restrictive one.
To change item-level permission settings, you must navigate to the specific document or object and make changes
individually.
1. View and edit permissions on the Document unitization layout—users need these permissions to access
and modify the unitization settings for documents.
2. View permissions on the Document Utilities object—users who need to see the status of unitization jobs or
requests should have view permissions on the Document Utilities object.
Note: If you enable document item-level security and overwrite security on document folders, the relevant
groups must possess Add Document and Add Images permissions per folder.
Important considerations
Take the following into consideration when using document unitization solution:
Note: The solution does not process any data in a workspace if the associated resource pool does not have its own
manager and worker agents. In such cases, document unitization jobs will remain inactive in the queue.
1. Add the Document Utilities application to the Application Library as a Relativity application.
2. Install and configure the Document unitization solution in the desired workspace.
3. Create at least one manager agent and one worker agent. You can generate multiple instances of these agents
to distribute the workload.
4. Create the manager and worker agents on each instance of the agent server associated with the resource pools
used in workspaces where the Document unitization solution will be used.
35.8.8 Scenarios
Additive permissions and Staging Explorer across workspaces
Setup:
You have two groups, Group A and Group B, and two workspaces, Workspace 1 and Workspace 2.
Group A has permission to use Staging Explorer, and permission to access Workspace 1. This is your typical Client
Domain Admin group.
Group B has permission to access Workspace 2. This is a typical Review group.
If a user is in both Group A and Group B, they have three permissions:
Note: In this case, because permissions are additive, and if the StagingPaneOnlyPerClientDomain setting is set
to False or missing, a user in both groups can use Staging Explorer to access the files on file shares for both
Workspaces 1 and 2, even though neither group explicitly gives permissions to use Staging Explorer on the
Workspace 2 file share. For more information regarding this, see the Permissions section of the Staging Explorer
Admin Oper-
Action Object Security Permission Item Security Tab
ation
View • View, Edit, Create, Delete, or Gives group members the rights to Email Email Thread
Relativity Administer for Color Map select and re-assign an alias to a dif- Threading Visualization
Email • View, Edit, Create, Delete or ferent entity when using name nor-
Threads Administer for Structured malization in Analytics.
Analytics Set
• View, Edit, Create, Delete, or
Administer for Structured
Analytics Results
• Create, Read, Update, and
Delete permissions on Email
Thread, Document, and Saved
Search objects.
To access and use the email thread visualization feature, it is essential to have certain security permissions in place.
Additionally, View security permissions are necessary for the following email fields:
l Email Action
l Email Thread Group
l Email Author Date ID
l Inclusive Email
l Email Thread Hash
l Email Duplicate Spare
l Email Threading Display
If any of these security permissions are not in place, you will not be able to use the email thread visualization tool.
Why can't I add permissions to a group to create fields?
To create fields, the Relativity Application view permission must be set to View.
l Relativity Application -
View
Why does an error message appear when users attempt to add a layout, even after I created and gave the new group
the ability to add and modify layouts?
To create fields, the Relativity Application view permission must be set to View.
Note: The Management Console or Cost Explorer object is an Admin Object, so permissions need to be set through
the Instance details tab.
Why am I unable to log in and get an error message indicating the default tab could not be determined?
If your instance setting EnableCustomerLockBox is set to true, it disallows System admin accounts from accessing
workspaces. Another system admin must add the user to the group with access to the desired workspace.
Additionally, it may be related to your object and item security permissions.
Object Security
Action Item Security Tab Admin Operation
Permission
Unable to log- l View on the l View per- The default tab error typically l Requires initial
in. Receiving workspace mission on refers to the initial tab that is configuration and
an error mes- object which the user item displayed when you log-in. setup of the lock-
sage indic- allows you to allows you to The exact name and content of box feature such
ating the access the view and this tab may vary depending as defining lock-
default tab workspace access your on your organization’s con- box folders,
could not be where you own user pro- figuration and customization. assigning secur-
determined. are attempt- file and asso- ity settings, and
ing to log-in. ciated customizing tabs
settings. or layouts.
l View per-
mission on l Edit per- l Manage folder
the user mission on structure within
object the document the lockbox for
enables you object organization.
to view user- enables you
related to modify the
information, documents
including within the
your own lockbox
user profile. folder, includ-
ing editing
their content.
Note: If a user receives the view automated workflows permissions, they can execute actions like Run Imaging Set,
even if they lack Imaging Set permissions. Automated workflows necessitate a distinct group and user within your
workspace for proper functioning. Upon application installation from the Application Library, the group and user will
be automatically added to the workspace. You do not need to make any modifications, creations, or deletions to this
user and group for your users to access automated workflows. This user and group are purposefully generated to
facilitate the functionality of automated workflows applications.
Admin
Action Object Security Permission Item Security Tab
Operation
Create an Auto- The Create permission for the The Create permission for l Automation N/A
mated Workflow “Automated Workflow” item “Automated Workflow” item
type. type. l Object
Security
Why are other users in my workspace unable to see or use an automated workflow that I created?
The user who created the automated workflow needs to confirm they have shared it with the appropriate group or
individuals in their workspace. They can do this by going to the automated workflow's settings and selecting the Share
option.
Note: Create a view with the Security field enabled to allow the selected group or user to access the Automated
Workflow.
Object Security
Action Item Security Tab Admin Operation
Permission
Use an Auto- View, Edit, Confirm you have the appropriate item security Security To configure object
mated Work- Create, and permissions to access the items relevant to the and item security per-
flow with Delete on doc- automated workflow. If the automated workflow missions, you need
access to uments or custom requires modifying or updating specific fields for the necessary admin-
certain objects the auto- items, you should have the necessary item istrative roles or per-
fields. mated workflow security permissions to perform those actions. missions to modify
interacts with. security settings.
Note: Depending on the specific actions performed by the automated workflow, additional permissions may be
required. If the workflow modifies or updates certain fields, you will at least need the Edit permission on those
objects.
How can I confirm multiple users who need to collaborate on a workspace, only have access to the documents and
data that are relevant to their work?
Set up workspace permissions that restrict access to specific documents, folders, or other items within the
workspace. You can also assign different roles to different users, such as reviewer, editor, or admin, depending on
their level of access and responsibility.
How can I streamline the process of assigning and managing permissions for a large team of users working on a
complex project?
Use Relativity's advanced permissions management tools, such as mass operations and custom permissions
templates, to simplify the process of setting up and managing workspace permissions. You can also use reporting and
auditing tools to track user activity and guarantee compliance with your organization's data security policies.
Note: RelativityOne includes a tool that allows you to choose a workspace to use as a source template for tab
structure and then lets you apply that template across multiple workspaces in your instance.
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.
You can add custom tabs in workspaces or at Home. Users with admin rights also have access to a Tabs tab from
Home. The functionality of this Tabs tab is the same as the Tabs tab in a workspace.
In addition, Relativity automatically creates a tab when you add a new object type.
36.2 Fields
Information on the fields in the Tab Information and Tab location are described below.
l Name - the tab’s name. This field must be between 1 and 50 characters. Be as concise as possible when nam-
ing tabs.
l Tab Type - determines the type of tab you want to create:
l Object - creates a tab for a non-document object in your workspace.
l Parent - establishes the tab as a parent tab. Existing tabs can then be set as children of the parent tab,
which causes them to display in the Sidebar's fly-out menu or in the Tab strip when the parent tab is cur-
rently selected. Selecting this option changes the layout by hiding the Object Type and Set as Default
fields.
l External - link to any URL or object type in Relativity.
Note: Selecting External from the Link Type menu causes the Link field to appear below the Parent
field. In the Link field, you can enter a web address to link to a URL.
You can create a link from a tab to an Relativity Dynamic Object (RDO) or a script, using either an Artifact
ID or GUID. To create links to other objects, you must use their GUIDs. For information about working
with objects that don't have GUIDs, see Tabs on the previous page.
Use the following token to link to an object: ObjectArtifactIdentifier=[identifier], where [identifier] is the
GUID of the object, or in the case of RDOs and scripts, the GUID or Artifact ID. For example, you would
use the format ObjectArtifactIdentifier=736b1c1f-d22f-43cf-9094-cc8acf94c60 to create a link from a
tab to the object with this GUID.
Use the following case insensitive text replacement options to customize the URL, allowing you to display current
details about your workspace:
l Object Type - determines which object’s information is displayed in the tab for those specified as Link Type =
Object.
l Set as Default Tab - toggle on to make this tab serve as the workspace’s default tab. Reviewers logging in to
the workspace are taken to the default tab. If a reviewer does not have access to the default tab, he or she is dir-
ected to the Documents tab instead.
l Visible - toggle on to display this tab from the Sidebar, Tab strip, and/or Quick nav.
l Relativity Applications - add this tab to a Relativity application. Clicking the Select button brings up a list of
available applications.
l Show in Sidebar - toggle on to add this tab to the Sidebar. Depending on the number of tabs that have already
been added to the Sidebar, the Order value assigned to this tab, and your browser's resolution, the tab may be
displayed in the More menu if it does not fit into the current Sidebar.
l Parent - select a parent tab to assign the current tab as a child tab. The current tab will display in the fly-out
menu for the parent tab.
l Order - represents the position of the tab by a numerical value. It can be any positive or negative integer. You
cannot use decimals in this field. The lowest-numbered tab displays at the top of the Sidebar. The highest-
numbered tab displays at the bottom of the Sidebar or in the More menu. Items that share the same value are
sorted in alphanumeric order.
Note: It's always a good idea to set tab order by 10's, starting with 10, then 20, then 30, etc. By numbering in
groups of 10 you can insert an item into any position later in the workspace, without the need to reorder (for
example, you can use 10, 20, 25, 30, 40 to insert a new tab between 20 and 30).
1. Create a new tab with a Tab Type of Parent or edit an existing tab.
2. Click the Edit icon next to the tab you want to nest.
3. Choose the parent tab name under the Parent drop-down menu.
4. Click Save.
Repeat for each child tab you wish to nest. Hover your cursor over the parent tab to display the nested child tabs in a
fly-out menu.
l Home - the tab lists users currently logged in to Relativity. You can send web page messages and email mes-
sages to users listed on the tab. You can also force the log out of these users from the system.
l Within a workspace - the tab lists the subset of users accessing the current workspace. You can send web
page messages and email messages to users listed on the tab.
2. Click the New User button in the upper-left. To edit an existing user, click the icon next to their name.
3. Complete the fields on the form. See Fields on the next page.
4. Click Save.
Note: Once you have created users, you can assign them to groups. When you add or remove users from a group,
Relativity will execute a job and send you an email notification once it's completed. In case of an error, the email will
contain a link that you can use to retry the job. Please note that to use the retry link, you need to be logged into
Relativity. Additionally, you can find the retry link in the Errors tab.
Note: In 2025, Relativity is deprecating the (Admin) Errors tab in RelativityOne. This change is part of our effort to
transform the error-handling experience by making it easier to address job-specific errors as they occur at their
source within your workspaces. Starting in April 2025, we'll hide the Errors tab from all production instances in a
phased rollout. In July 2025, we'll permanently remove it from RelativityOne and disable the ability to read errors
through the API. For more details, see Errors tab deprecation.
Note: You can preview the security settings of any workspace available for a user by clicking Preview Security.
37.4 Fields
The User Information section fields are:
l First Name - the user’s first name. This field must be between 1 and 50 characters.
l Last Name - the user’s last name. This field must be between 1 and 50 characters. The system displays a user
as <last name>, <first name>.
l Email - the user’s email address. While the system won't validate this information, you must enter it in the fol-
lowing format: name@domain.extension.
Note: Relativity users can have the same first and last name, but the email address must be unique.
l Type - the user type. The default values are internal or external, but you can add any type value. Type is for ref-
erence purposes only and has no impact on access or billing.
l Client - the client associated with the user. Click Select to choose from available clients.
Note: Items on the selected client list are set by a system view. It's possible you'll see only a sub-set of items.
l Relativity Access - a toggle where you can control the user’s access to Relativity.
l Enabled - the default value. Enabled users can log in to Relativity and are considered for billing under
your Relativity license.
l Disabled - users cannot access Relativity and won't be counted or billed as named users on your Relativ-
ity license.
l When Relativity is first deployed, the system sets the Relativity Access field for existing users using the
following criteria. A system admin can change a user's access at any time.
l If a user is in a group with rights to a workspace, their Relativity Access is set to Enabled.
l If a user is not in a group with rights to a workspace, their Relativity Access is set to Disabled.
l Disable on Date (UTC) - the date when the user's Relativity access is disabled. Use the field to auto-disable
users on a specific date in the future, for example, when managing contact reviewers. When you specify the
date, it can't be in the past. For more information, see Auto-disable users on page 630
Note: The Disable on Date value is in UTC and does not represent local time.
l Trusted IPs - specifies a list of trusted IP addresses for a user. Authentication fails if a user attempts to log in to
Relativity from an unauthorized IP address.
l Change Settings - users without admin rights can change their settings depending on whether the toggle is
enabled or disabled.
l First name
l Last name
l Email address
l Item list page length
l Default selected file type
l Advanced search default
l Enable or disable Native Viewer Cache Ahead
l
Note: While "My Settings" appears grayed out in the user preview, users will still be able to access and
change their own settings based on their assigned permissions.
As of February 2025, the new Feature Permissions redefines Relativity's security management by shift-
ing the focus from Object Types and Tab Visibility to feature-based permissions. This new method is
simply another option; any feature-specific permissions information already in this topic is still applicable.
This new interface enables administrators to manage permissions at the feature level, offering a more
intuitive experience. By viewing granular permissions associated with each feature, administrators can
ensure comprehensive control, ultimately reducing complexity and minimizing errors. For details see
Instance-level permissions and Workspace-level permissions.
l Change Document Viewer - users can change document viewers depending on whether the toggle is enabled
or disabled.
l Enabled - users can select which viewer they want to use. You can still set a default viewer in the Docu-
ment Viewer field, but users can switch between viewers.
l Disabled - users can't select which viewer they want to use. Whatever viewer appears in the Document
Viewer field in User Settings is the only viewer the user has access to.
l Document Skip - This feature is not currently compatible with RelativityOne and as a result, this option does
not impact a user's ability to access this feature.
l Keyboard Shortcuts - Choose a default setting for the keyboard shortcuts icon in the Review Interface. This
property is set to Enabled by default.
The Defaults section fields are:
l Item List Page Length - a numeric field indicating the default list length for all views in Relativity except for
views that are embedded into layouts as an Associative Object List. You can set it from 1 to 200.
Note: Associative object lists in a layout do not inherit this value (the default number of items per page for
these lists is 10 and cannot be customized).
l Document Viewer - uses the Aero viewer to review documents. This field is non-editable.
Note: If a user is currently logged in to Relativity when a system admin modifies a setting, the user must log
out and log back in for the changes to take effect. This also applies to the system admin if they are altering the
setting on their own account.
l Saved Search Owner - determines whether saved searches are public or private by default. If Public is selec-
ted, the search is public and all users with rights to it can see it. If User is selected, the search is private and only
the logged in user is able to see it. The property’s default value is configurable on a system level.
l Document Skip Preference - controls whether or not the user has the ability to skip documents during review
that no longer meet the original conditions of a view due to propagation. This field is non-editable and set by
default to be disabled.
l User-Group Email Notifications (if applicable) - controls the type of email notifications Relativity will send to
an admin that is adding or deleting users or groups. The available options are:
l Receive All- receive all email notifications regarding the addition or removal of a user or group.
l Receive Errors Only - receive email notifications on failed operations only regarding the addition or
removal of a user or group.
l Do Not Receive - receive no email notifications regarding the addition or removal of a user or group.
Note: Audit records are not modified when a user is deleted or disabled. You will still be able to search for a user's
audits based on their user name.
l User Name - The name of the Relativity user who performed the action.
l Action - The action that was performed.
l Timestamp - The date and time that the action was performed.
1. Open the User Status tab in from within a workspace or from Home.
2. Select the checkbox next to the names of the users you want to send a message to.
3. Select Send Message from the drop-down menu at the bottom of the page.
4. Click Go. The Webpage Dialog appears.
5. Enter your message in the Message field, and then click Send Messsage. The selected users receive a web
page message immediately.
To send an email message to an individual recipient, you can click on their email address link. This will launch your
native email application, allowing you to compose the message. Your login information will identify you as the sender
of the email message.
If the button is enabled, click it to remove the user's email from the bounce list, then resend the invitation or ask the
user to log in again to generate the 2FA challenge email. Follow this process to troubleshoot situations where users do
not receive Relativity-sent emails. This applies to all workflows, not just user authentication.
Note: If the button is not enabled, the user is not on the bounce list, and there may be another issue with the user's
email address or server. The user should check their junk email and spam folders, and may need to consult with
internal IT. For more information on user invitations, see Centralized Authentication.
Note: When you use the Force Log Out option to terminate a user's session, any changes the user made and did
not save will be lost.
Note: If you select the checkbox and leave the date value blank, will clear the Disable On Date (UTC) for the
users.
6. Click Ok. The Disable On Date (UTC) field is set for the selected users, and they will be automatically logged
out on the specified date and time.
Note: If an Object Type List page does not have a view, it does not load and an error message appears that states
no views have been created.
When you create a view, you can set conditions so that only objects that meet certain criteria appear in the view.
However, you shouldn't rely on views to control security. If you need to prevent users from viewing an item, you must
set the appropriate security permissions for that item.
If a user does not have access to any of the available views, an error message appears that states the page is
secured.
Note: These relational views are automatically generated when you make a relational field. By
default, they are not included on the Documents tab and are only used to determine the fields
that appear in the related items pane for that relational group.
l Search Results Pane view - controls which fields are visible in the related items pane when you right-click in
the viewer to run an Analytics search for similar documents.
l History Pop up - controls which fields appear when clicking details from the related items pane document his-
tory.
l Production Documents - controls which fields display for documents included on a production details page.
Include the fields you use to qualify a document for production in the production documents view. You can then
filter the list for disqualifying field values, providing a final QC step in the production process.
l Markup History Details - controls which fields appear when you launch a document’s history details from the
related items pane.
l Default Search view - controls which fields are returned, by default, on an advanced or saved search. You can
always include additional fields from the advanced or saved search field selector. This view also controls the
sort order of these fields as well. See Creating a saved search in the Searching guide.
l Linked - controls which fields are shown in the pop-up. You can then link to a document in the viewer.
l Link Pane view - controls which fields are shown in the related items pane showing the linked documents.
l Batch Set Batches - controls which fields are shown for the list of batches displayed at the bottom of the Batch
Sets tab.
l Document Batches (Default) - controls the pop-up for searching batches on a view or an advanced or saved
search.
Note: For more information on searching with Batch fields as search conditions, see Batch field as search
conditions in the Searching guide.
l Advanced Search Browser view - controls the fields displayed in the Advanced Search Browser.
l Event Handlers on Object Type - controls the fields displayed in the pop-up for event handlers attached to an
application.
Note: We recommend avoiding sensitive data in tab names. You can secure new tabs by overriding inherited secur-
ity settings and applying .item-level security.
4. Click Save.
Note: It’s always a good idea to order by 10's, starting with 10, then 20, then 30, etc. By numbering in
groups of 10 you can insert an item into any position later in the workspace, without the need to reorder
all items.
l Group Definition - includes propagated documents in the view and groups those documents together between
blue lines within the document list.
l Query Hint - used to optimize views. Only use the query hint if instructed by the Relativity Customer Support
team. Currently, you can use Hashjoin: (true/false) or Maxdop: (x) to populate the field.
l Relativity Applications- associate this view with an application created in the Applications tab. Click Add to
select an existing application. This is only available for those who have the Manage Relativity Applications per-
mission under Admin Operations.
l Visible in Dropdown- makes the view available in the selected object type's tab.
l Inline Editing Enabled- If enabled, this view allows users to edit fields using inline editing. If disabled, users
cannot edit fields using inline editing while in this view.
Move any fields you want in your view to the right box, Selected items. You can move fields between boxes by:
view. Place your cursor in the Selected items box to order the fields using drag and drop.
There are several special system fields unique to views that you can add to a view:
Note: The number of fields, or columns, you select can impact page load performance.
To define the criterion for your view, you can choose to add conditions, logic groups, or both.
To set a condition, complete the following steps:
Note: If you are setting a condition on a view that can utilize field categories, you can conveniently filter the
list of available fields by selecting a field category from the drop-down menu above the fields list.
3. A pop-up appears to select your search operator and enter the value to be searched. Available operators differ
depending on the type of field being searched.
With date-based fields, you can enter dates with the MM/DD/YYYY format or use the date range filter.
Depending on the field type and operator, you can choose the value(s) from a popup picker. A popup picker is
available for selecting choices and objects that provide the following operators:
l Any of these
l None of these
l All of these (only for multi-object fields)
l Not all of these (only for multi-object fields)
Each row represents a sort criterion. Select the desired sort field in the first column. The second column sets whether
the sort should run ascending or descending. The sorts are applied in nested order.
l In the Views tab in a workspace, click the Edit icon next to the desired view in the item list and move through the
steps for creating a view.
l For all Relativity Dynamic Objects (RDO), and most system objects, you can click on the view drop-down to dis-
play the list of views. Next, click Edit icon next to the view you wish to edit, and then move through the steps for
creating a view.
l Owner - sets the user(s) who can see the view. If the owner is set to Public, all users with rights to the view are
able to see it. If the owner is set to a specific reviewer, the view is visible to only that reviewer. Clicking Me
assigns the view to the logged in user.
View information
Note: It’s always a good idea to order by 10's, starting with 10, then 20, then 30, etc. By numbering in
groups of 10 you can insert an item into any position later in the workspace, without the need to reorder
all items.
l Visible in Dropdown - makes the view available in the selected object type's tab.
Advanced Settings
38.11 Fields
In the second step of the wizard you select the fields that appear on your view.
All potentially available fields appear in the left box, Available Fields. Move any fields you want in your view to the
right box, Selected Fields. You can move fields between boxes by:
l Cancel - ends the creation of the view. No information entered in the wizard is saved.
l Back - takes you back to the previous step of the wizard.
l Next - saves the information on the form and takes you to the next step of the wizard.
l Save - records the information on the form and completes the creation of the view.
38.12 Conditions
In the third step of the wizard you determine which items you want your view to return. A field condition can contain up
to 4,000 characters.
When the item list for the view loads slowly due to a long running query, a message box displays with a Cancel
Request link. This link is available when you perform other actions on item lists containing documents or Dynamic
Objects that initiate a query in the background, as well as when you perform searches, filter, or sort on these objects.
Note: The Set Conditions section is similar to the Conditions section in saved searches. For more information on
the available options, see Saved search in the Searching guide.
l The first box, Criteria - select a single, double or triple parentheses. With this option you can create complex
levels of grouping between different criteria. This is only available when you have more than one row.
l The second box, Field - select any available field in your workspace. The types of fields present differ based
on the type of view you are creating.
l The third box, Operator - select your search operator. Available operators differ depending on the type of field
being searched.
l The fourth box, Value - select the value to be searched.
Note: With date-based fields, you can enter @today as the value instead of choosing a date.
l The fifth box - close any parentheses opened in the first box.
l The sixth box - connect each criterion with an “AND” or “OR” operator.
Depending on the field type and operator, you can choose the value(s) from a pop-up picker. A pop-up picker is
available for selecting choices and objects that provide the following operators:
l Any of these
l None of these
l All of these (only for multi-object fields)
l Not all of these (only for multi-object fields
When you click next to any of these operators, the following window appears:
l View Order - opens a pop-up that displays the order of existing items to determine where the new item should
display.
l Add Conditions - displays a new conditions row where additional conditions can be set.
38.13 Sort
In the fourth and final step of the wizard you define the default sort order of the view. If you don't select a sort criterion,
the view sorts by artifact ID. Users are able to temporarily sort the view by any field that has Allow Sort/Tally set to Yes
included on the view.
Dashboards are available for dynamic object type views. They are also supported by the following static objects:
l Document
l Install Event Handler
l Mass Operation
l Markup Set
l Production
Note: Using your internet browser to zoom to any size other than 100% while using the Viewer is not supported and
can cause unexpected behavior.
If you do not see the document in the Viewer, it either has not been loaded to the workspace, its conversion failed, or
you do not have permission to see it.
Note: The Viewer displays PDF text by mapping the character codes to Unicode in most cases. To check whether
PDF text has been properly encoded and will display correctly in the Viewer, copy the text in the original PDF file
and paste it into another application like Microsoft Word or Notepad. If the pasted text does not display correctly, the
PDF is not properly encoded. If the pasted text displays correctly in another application but not in the Viewer, con-
tact Support for assistance.
l Zoom Out/In —zooms out and in on the current document in increments of 10% within a range of 10% to
4,000%. If you attempt to zoom out to a percentage lower than 10%, the Viewer automatically sets the display to
10%. If you attempt to zoom in to a percentage higher than 4,000%, the Viewer automatically sets the display to
4,000%. Your zoom setting persists as you navigate through a document set. This means that if you have set
one document to 150% and you go to the next document, the next document defaults to 150% zoom.
To specify a zoom percentage without using the zoom out/in toolbar buttons, type the number in the percentage
field and press the Enter key.
l Reset Zoom —resets the zoom to 100%.
l Fit Width —increases the size of the document to fit the maximum width of the Viewer. This setting persists
when you re-size the window.
l Fit Page —fits the entire document into the total size of the page. Clicking this zooms out the document and
reduces the font size.
l Fit Actual —fits the document display to the actual size it was in its native application. By default, this resets
the zoom percentage to 100%.
l Layout Mode —select one of the following options to determine how documents that are more than one page
long display in the Viewer.
l Single —one page of a document will display at a time. Use the page navigation options at the bottom of
the Viewer to adjust which page you view.
l Single Continuous —displays the pages in the document stacked vertically so you can scroll up and
down to view them.
l Facing Continuous —displays the pages in the document in a row horizontally so you can scroll left and
right to view them.
l Draft Mode —click to begin Draft Mode which automatically contrasts text from the background, help you
identify poorly drawn redactions, and identify corrupt OCR text. This option is only available on the Native
Viewer and PDF Viewer with rendered documents.
l Go To Next/Previous Highlight —moves through previous and next highlighted terms in the document.
l Rotate All Pages —rotates all pages in a document clockwise 90 degrees. This option is only available for doc-
uments that have been paginated.
l Redact Markup Visibility —this option determines how markups display in the Viewer.
It only displays if you have the Redact application installed and open a PDF or spreadsheet document in the Nat-
ive Viewer.
Click the Redact Markup Visibility icon to toggle between the following modes:
l Solid - Markups in the document are fully visible and cover text underneath.
l Transparent - Markups in the document are partially visible so that you can still see the text underneath.
l Transcript Text—This option only displays if you have an audio-visual document open in the Native Viewer.
Click to expand the panel and view the transcribed text for an audio-visual document.
l Search Bar —searches for terms in the current document and navigates through the hits.
l Entering a term and either clicking the left or right arrow button or pressing Enter in this text box scrolls to
and highlights the text of the next instance of the term, from the placement of the cursor.
l Searching in this text box is not case sensitive.
l Searching supports dtSearch and so proximity, fuzziness, and stemming can be used.
l You can remove a term you previously searched for or all of the terms you have recently searched for
from the Persistent Highlight Pane. Removing a term or terms will also remove any highlights they
l Persistent Highlighting—displays or hides a panel containing all recent searches from the criteria entered in
the search bar and any persistent highlight sets in the workspace. You can also create a dtSearch or keyword
search in the Your recent searches section. Only terms in the sets and recent searches that are in the current
document will display in the pane.
Additionally, you can control which highlights display in the current document by clicking on either the persistent
set to only display highlights from that set or you can click on a specific term to only see that term highlighted in
the document. You can also navigate to and from highlights using this pane.
l Thumbnail—click to expand the left drawer and display the Thumbnail Viewer. Each page of the document you
are reviewing has its own numbered thumbnail in the Thumbnail Viewer.
l Sentiment—click to expand or collapse the left drawer and display sentiment analysis highlights in the Viewer.
l aiR for Review Analysis—click to expand or collapse the left drawer and display aiR for Review results. You
can also enable or disable aiR for Review highlights.
l aiR for Privilege Analysis—click to expand or collapse the left drawer and display aiR for Privilege results.
Additionally, to exit the Viewer and return to the page you were previously on, you can click the Exit viewer button at
any time.
Note: If you don't have permission to the Local Access option on the Document object, you can't use the Ctrl+C or
Ctrl+Ins options in either the Native Viewer or the Extracted Text Viewer.
The audio and video controls that display in the Viewer depend on your internet browser.
Note: Audio files that are longer than 30 minutes cannot be opened in the Native Viewer.
Waveform is a visualization of sound that you can view while listening to an audio file in the Native Viewer. Click the
Show/Hide Waveform icon to display the Waveform visualization. The visualization tracks the volume and intensity
of sound to help you avoid audio inactivity. You can use the audio controls to skip these sections. The visualization
also scrolls with a time scale along the bottom to help you identify when a particular audio event occurs.
File exten-
File type Annotation type Tracked changes
sions
Excel .xls, .xlsx, Tracked Changes, formulas, hidden pages/- Inserted cell, moved cell,
.xlsb columns/rows, Comments, concealed cell contents modified cell, cleared cell
Inserted column, deleted
column
A hidden content icon is available when a supported file type is in the Native Viewer. Click the Hidden Content icon to
open or close the annotations bar. If you are viewing an unsupported file type, the icon is not available. For supported
file types, see the Tracking annotations.
Annotation bar
The annotation bar is for sorting and viewing the hidden content found with Document Intelligence. Each annotation
has a card that lists the tracked change, a description of the change, time and date, and author of the change.
If there are multiple annotation cards in the annotation bar, then you can sort them in multiple ways. Click the Sort By
drop down menu for these options:
l Location
l Author A-Z
l Author Z-A
l Oldest first
l Newest first
l Annotation type
Leader lines
Clicking on an annotation in the Viewer connects the selected annotation to the related annotation tile in the
annotation bar. Click on another annotation to view the leader line to that annotation card. One grey connector line is
available at a time, unless you moved a cell. In this case, there is a leader line where the cell was originally located and
a leader line in the cell's new location. Click the same annotation to remove the leader line.
Note: If you used the Basic Imaging profile to produce images of a PDF file, please note that the Viewer displays
PDF text by mapping the character codes to Unicode in most cases. To check whether PDF text has been properly
encoded and will display correctly in the Viewer, copy the text in the original PDF file and paste it into another applic-
ation like Microsoft Word or Notepad. If the pasted text does not display correctly, the PDF is not properly encoded.
If the pasted text displays correctly in another application but not in the Viewer, contact Support for assistance.
l Zoom Out/In —zooms out and in on the current document in increments of 10% within a range of 10% to
4,000%. If you attempt to zoom out to a percentage lower than 10%, the Viewer automatically sets the display to
10%. If you attempt to zoom in to a percentage higher than 4,000%, the Viewer automatically sets the display to
4,000%. Your zoom setting persists as you navigate through a document set. This means that if you have set
one document to 150% and you go to the next document, the next document defaults to 150% zoom.
To specify a zoom percentage without using the zoom out/in toolbar buttons, type the number in the percentage
field and press the Enter key.
l Reset Zoom —resets the zoom to 100%.
l Fit Width —increases the size of the document to fit the maximum width of the Viewer. This setting persists
when you re-size the window.
l Fit Page —fits the entire document into the total size of the page. Clicking this zooms out the document and
reduces the font size.
Note: Image rotation is persistent. Any pages that you rotate will be rotated the next time you return to them
in the Viewer and for other users who view them after you rotate them. Rotation is also applied when you run
the production containing the images.
l Redaction Type - <Style> —enables single redaction tool. For more information on redacting, see Creating
basic redactions on page 307. Select from the following types of redactions:
l Thumbnail—click to expand the left drawer and display the Thumbnail Viewer. Each page of the document you
are reviewing has its own numbered thumbnail in the Thumbnail Viewer. To learn more, visit Thumbnail Viewer.
l aiR for Review Analysis—click to expand or collapse the left drawer and display aiR for Review results. You
can also enable or disable aiR for Review highlights.
l aiR for Privilege Analysis—click to expand or collapse the left drawer and display aiR for Privilege results.
Additionally, to exit the Viewer and return to the page you were previously on, you can click the Exit viewer button at
any time.
Notes: Relativity displays all long text fields made available in the Viewer in the drop-down menu, regardless of
whether that field contains text for the current document. If you select a long text field from the drop-down list, and
the current document does not have text for that field, the Viewer displays a message stating, "This page is empty".
The Viewer displays PDF text by mapping the character codes to Unicode in most cases. To check whether PDF
text has been properly encoded and will display correctly in the Viewer, copy the text in the original PDF file and
paste it into another application like Microsoft Word or Notepad. If the pasted text does not display correctly, the
PDF is not properly encoded. If the pasted text displays correctly in another application but not in the Viewer, con-
tact Support for assistance.
l Zoom Out/In —zooms out and in on the current document in increments of 10% within a range of 10% to
4,000%. If you attempt to zoom out to a percentage lower than 10%, the Viewer automatically sets the display to
10%. If you attempt to zoom in to a percentage higher than 4,000%, the Viewer automatically sets the display to
4,000%. Your zoom setting persists as you navigate through a document set. This means that if you have set
one document to 150% and you go to the next document, the next document defaults to 150% zoom.
To specify a zoom percentage without using the zoom out/in toolbar buttons, type the number in the percentage
field and press the Enter key.
l Reset Zoom —resets the zoom to 100%.
l Go To Next/Previous Highlight —moves through previous and next highlighted terms in the document.
l Tab character size —select an option from the drop-down menu to determine the amount of space that is
taken when the Tab key was used in the current document. This option can help you ensure that the spacing in
a spreadsheet document is aligned and works best when the Tab key is used after each column in the spread-
sheet.
l Toggle WordWrap —determines whether the text in the current document will wrap so that it fits on the current
page or not.
l Enabled —text in the current document will be forced onto the next line if it cannot display in the current
window size. You cannot scroll horizontally with Toggle WordWrap enabled.
l Disabled—text in the current document will not be forced onto the next line will display in more horizontal
fashion. You can scroll horizontally to control to view the desired text
l Search Bar—searches for terms in the current document and navigates through the hits.
l Entering a term and either clicking the left or right arrow button or pressing Enter in this text box scrolls
to and highlights the text of the next instance of the term, from the placement of the cursor.
l Searching in this text box is not case sensitive.
l Searching supports dtSearch and so proximity, fuzziness, and stemming can be used.
Note: If you don't have permission to the Local Access option on the Document object, you can't use the Ctrl+C or
Ctrl+Ins options in either the Native Viewer or the Extracted Text Viewer.
l Sentiment—click to expand or collapse the left drawer and display sentiment analysis highlights in the Viewer.
l aiR for Review Analysis—click to expand or collapse the left drawer and display aiR for Review results. You
can also enable or disable aiR for Review highlights.
l aiR for Privilege Analysis—click to expand or collapse the left drawer and display aiR for Privilege results.
l Contextual Search—click to expand the right drawer and display the Contextual Search card. This feature
allows you to quickly navigate to matching search terms in a document which is useful in longer documents or
ones that have many matching search terms. The Contextual Search card has the same functionality as the
Search Bar. To learn more about the Search Bar's functionality, see Search Bar. Additionally, each search term
match is displayed in a box that includes both words before and after the search term match to make it easy for
you to view the context of each one.
Enter a term or terms in the search box and press Enter on your keyboard to highlight in yellow any matches in
the current document. You can click on a desired search term box in the pane to jump to that place in the doc-
ument. The active search term box will display with a blue border and the matching search term in the document
will be highlighted in blue to make it easy to find.
Additionally, to exit the Viewer and return to the page you were previously on, you can click the Exit viewer button at
any time.
Note: The redactions that are burned into a produced image are the redactions that were on the image at the time
that you produced it. If you add or remove redactions from an image after you have produced it, then the image and
the produced version of that image will be out of sync.
Select a production set from the drop-down menu to see how a document was produced in the selected production. If
a document is not included in a production, the productions mode option is unavailable.
Note: Image rotation is persistent. Any pages that you rotate will be rotated the next time you return to them
in the Viewer and for other users who view them after you rotate them. Rotation is also applied when you run
the production containing the images.
Note: If the source file of the document you are imaging is changed during the conversion process, for example
through overlay, that document becomes undeliverable and you receive an error. To resolve this error, refresh the
page or re-image the document.
After imaging a document on the fly, you can access thumbnail renderings of the imaged pages of the document.
Imaging some file formats can cause problems. Consider the following:
l Many PDFs render and image very well. However, you may have problems rendering and imaging some PDFs
due to the variety of their content.
l While most Microsoft Office documents render and image well, you may experience issues when imaging doc-
uments with embedded files.
l You may have problems rendering and imaging vector-based documents like Visio and CAD.
Note: You may experience slowness if you try to open PDF documents that are larger than 300 megabytes.
The Viewer displays PDF text by mapping the character codes to Unicode in most cases. To check whether PDF
text has been properly encoded and will display correctly in the Viewer, copy the text in the original PDF file and
paste it into another application like Microsoft Word or Notepad. If the pasted text does not display correctly, the
PDF is not properly encoded. If the pasted text displays correctly in another application but not in the Viewer, con-
tact Support for assistance.
l Zoom Out/In —zooms out and in on the current document in increments of 10% within a range of 10% to
4,000%. If you attempt to zoom out to a percentage lower than 10%, the Viewer automatically sets the display to
10%. If you attempt to zoom in to a percentage higher than 4,000%, the Viewer automatically sets the display to
4,000%. Your zoom setting persists as you navigate through a document set. This means that if you have set
one document to 150% and you go to the next document, the next document defaults to 150% zoom.
To specify a zoom percentage without using the zoom out/in toolbar buttons, type the number in the percentage
field and press the Enter key.
l Reset Zoom —resets the zoom to 100%.
l Persistent Highlighting—displays or hides a panel containing all recent searches from the criteria entered in
the search bar and any persistent highlight sets in the workspace. You can also create a dtSearch or keyword
search in the Your recent searches section. Only terms in the sets and recent searches that are in the current
document will display in the pane.
Additionally, you can control which highlights display in the current document by clicking on either the persistent
l Thumbnail—click to expand the left drawer and display the Thumbnail Viewer. Each page of the document you
are reviewing has its own numbered thumbnail in the Thumbnail Viewer.
l Sentiment—click to expand or collapse the left drawer and display Sentiment Analysis Highlights in the Viewer.
l aiR for Review Analysis—click to expand or collapse the left drawer and display aiR for Review results. You
can also enable or disable aiR for Review highlights.
l aiR for Privilege Analysis—click to expand or collapse the left drawer and display aiR for Privilege results.
l Hidden Content—displays or hides all hidden cells in a Microsoft Excel spreadsheet. This functionality is only
available for Excel files and does not work on imaged documents because Relativity only images unhidden
cells.
l Contextual Search—click to expand the right drawer and display the Contextual Search card. This feature
allows you to quickly navigate to matching search terms in a document which is useful in longer documents or
ones that have many matching search terms. The Contextual Search card has the same functionality as the
Search Bar. To learn more about the Search Bar's functionality, see Search Bar. Additionally, each search term
match is displayed in a box that includes both words before and after the search term match to make it easy for
you to view the context of each one.
Enter a term or terms in the search box and press Enter on your keyboard to highlight in yellow any matches in
the current document. You can click on a desired search term box in the pane to jump to that place in the doc-
ument. The active search term box will display with a blue border and the matching search term in the document
will be highlighted in blue to make it easy to find.
Additionally, to exit the Viewer and return to the page you were previously on, you can click the Exit viewer button at
any time.
l Download—hover your cursor over this option and select one of the following:
Note: Files over 4 GB cannot be downloaded using this option. If you have a document that is over 4 GB, you
can create a saved search that includes any documents you wish to export and then export them using
Import/Export.
l Active Production—select to download a copy of the produced document. A user must be granted the
Documents - Local Access (Download, Copy Text) permission to use this option.
l Document native—select to download a copy of the current document. A user must be granted the
Documents - Local Access (Download, Copy Text) permission to use this option.
If you cannot download a copy of the document, this option is grayed out. Hover your cursor over this
option to view a tooltip that contains an explanation why this option is disabled.
A system or case administrator can determine which native file types users can and cannot download by
doing the following:
1. Navigate to the Native Types tab.
2. Click the Edit icon in the row of the desired file type.
3. On the Prevent Native Download field, select Yes to prevent users from downloading it or No to
allow users to download it.
l PDF—select to download a copy of the stored PDF of the current document. To create a stored PDF, use
Mass PDF. A user must be granted the Documents - Local Access (Download, Copy Text) permission to
use this option.
If you cannot download a copy of the document, this option is grayed out. Hover your cursor over this
option to view a tooltip that contains an explanation why this option is disabled.
Note: If the document has produced images, these are not affected by this option. To remove the pro-
duced images from a document, delete the production set instead.
l Image on the fly—to image the current document from the Viewer, hover your cursor over this option
and the Image Profile options will display. Select the desired profile option to begin the imaging process.
A system or case administrator can determine which native file types can or cannot be imaged using
Image on the fly by doing the following:
1. Navigate to the Native Types tab.
2. Click the Edit icon in the row of the desired file type.
3. On the Restricted From Imaging By Default field, select Yes to prevent users from using this
option to image the native type or No to allow users to image the native file type.
l Replace images for this document—to replace the images for the current document using an imaging profile,
hover your cursor over this option and select the desired Imaging Profile option to begin the imaging process.
l Reconvert—select to clear your internet browser's cache and reload the current document for review.
l Download translated document—hover your cursor over this option and select the desired language to down-
load a copy of the document in the selected language. This option only displays if a document has been trans-
lated.
l Related items —displays a group of documents related to the active document. Options vary within the work-
space. Hover over each icon to display the name of the item. Examples include: family group, duplicates, and
thread group.
l Document history —displays a history of actions taken on the current document. You may not have access to
document history. If you store your audits in Data Grid, this displays the field name, old value, and new value.
Note: In the Document History card, you can click the Details link to display a pop-up with the audit history
for the document. Click Run Details to display information about document imaging jobs, including the name
of the imaging profile and the formatting options used during mass imaging or imaging on the fly.
l Production —displays all productions in which the document was included. You may not have permissions to
view production information.
l Linked —displays all linked records on the active document.
l Search results —displays the results of an Analytics search.
l Batch sets —shows all the batch sets for the active record. See Batches on page 110. You may not have per-
missions to view this section.
39.12 .eml and .msg header dates and times in the Viewer
.eml, .msg and RSMF documents have header dates and times in Coordinated Universal Time (UTC) format. The
Relativity Native Time Zone Offset field determines how these date/time values are displayed in the Native Viewer,
based on the desired time zone and its offset from UTC.
Note: Relativity does not automatically account for Daylight Savings Time. For documents processed in Relativity,
DST rules are automatically taken into account when calculating the Relativity Native Time Zone Offset value. For
all other documents, if you need the Viewer to account for Daylight Savings Time, deploy the Set Native Timezone
Offset With DST script. You must be a Relativity admin to deploy this script.
Note: The Thumbnail Viewer may not be available in the Native Viewer for document types that do not paginate
such as spreadsheets or plain text.
Note: You can change the value of either of the fields at any time while in the Document Compare window.
3. Select the desired document from the list and click Set. The Document Compare window displays the selected
document in the With field.
4. Click Compare. The window displays the similarities and differences between the documents.
5. The similarities and differences between the documents are reflected in the legend at the bottom of the window:
l Inserted - text appears in the "With" document but doesn't appear in the "Compare" document.
l Deleted - text appears in the "Compare" document but doesn't appear in the "With" document.
l Unchanged -text appears in both documents.
Note: Relativity does not support any third-party applications after the user downloads a file. This includes specific
browser and media-player combinations, such as Internet Explorer and Windows Media Player.
File Exten-
Program/File Type Category Type/Version
sion
File Exten-
Program/File Type Category Type/Version
sion
7z Archive .7z
Note: BZIP2 and split archives are not supported.
7z Self Extracting exe Archive .exe
Note: BZIP2 and split archives are not supported.
LiveNote Evidence File Archive .lef
LZA Self Extracting Compress Archive .lza
LZH Compress Archive .lzh
Microsoft Office Binder Archive 95, 97 .obd
Microsoft Cabinet (CAB) Archive .cab
PKZip Archive .zip
RAR Archive 1.5, 2.0, 2.9 .rar
TextMap Evidence File Archive .xmef
UNIX Compress Archive .z
UNIX GZip Archive .gz
UNIX tar Archive .tar
Uuencode Archive .uue
Zip Archive PKZip, WinZip .zip
DataEase Database 4.x .dba
DBase Database III, IV, V .dbf
First Choice DB Database Through 3.0 .fol
Framework DB Database 3.0
Microsoft Access Database 2007/2010 .accdb
Microsoft Works DB for DOS Database 2.0 .wdb
Microsoft Works DB for Macintosh Database 2.0 .wdb
Microsoft Works DB for Windows Database 3.0, 4.0 .wdb
Microsoft Works DB for DOS Database 1.0 .wdb
Paradox for DOS Database 2.0 - 4.0 .db
Paradox for Windows Database 1.0 .db
Q&A Database Database Through 2.0 .db
IBM Lotus Notes Domino XML Language DXL Email 8.5 .xml
IBM Lotus Notes NSF (Win32, Win64, Linux x86-32 and Oracle Email 8.x .nsf. .ntf
Solaris 32-bit only with Notes Client or Domino Server)
MBOX Mailbox Email RFC 822 .mbox
Note: Excel files with slicers will convert and display normally
in the Viewer, but slicer elements in those files will not display.
Note: Program/file types listed with text only or PDF preview only can be reviewed in the Viewer as listed. If
PDF preview only, a PDF file saved as part of the native will be viewed. Text only will just display the text without any
formatting.
Note: Relativity does not support any third-party applications after the user downloads a file. This includes specific
browser and media-player combinations, such as Internet Explorer and Windows Media Player.
To resolve the error, ensure that your internet browser can play the selected file type. If that does not resolve the error,
check the MaximumNativeSizeForViewerForMediaFilesinMegaBytes instance setting to ensure that the file type is
not too big for the Viewer to stream.
File Format Container - Audio Codec Chrome Firefox Internet Explorer Safari
FI_RIFFWAVE wave - pcm √ √ √
Quicktime Movie mov - aac √ √ √ √
Quicktime Movie mov - vorbis √
MPEG Layer3 ID3 Ver 1.x mp3 - mp3 √ √ √
MPEG Layer3 ID3 Ver 2.x mp3 - mp3 √ √ √ √
FI_MPGAV2L3 mp3 - mp3 √ √ √
MPEG-4 file mp4 - aac √ √ √ √
MPEG-4 file mp4 - opus √
MPEG-4 file mp4 - vorbis √
MPEG-1 audio - Layer 3 mov - mp3 √ √ √
MPEG-1 audio - Layer 2 mp4 - mp2 √ √
MPEG-1 audio - Layer 3 mp4 - mp3 √ √ √
Ogg Opus ogg - opus √ √
Ogg Vorbis ogg - vorbis √ √
Note: As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the
focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option;
any feature-specific permissions information already in this topic is still applicable. This new interface enables
administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular
permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing
complexity and minimizing errors. For details see Instance-level permissions and Workspace-level permissions.
2. Click New Workspace to create a new workspace. If you want to edit an existing workspace, click the pencil
icon next to the workspace name.
3. Complete the fields in the form. See Fields on the next page.
4. Click Save. A window displays the progress of the workspace creation process. You cannot access the work-
space until it is created and its status is Active. If needed, close the progress window to continue working in
RelativityOne. This will not interfere with the creation process.
To find out the status of the workspace, review the Workspace State column in the Workspaces list:
l Active—the workspace is available for use.
l Creating—the workspace is in the process of being created.
l Cold storage—the workspace has been migrated to Cold Storage. See Migrating and retrieving work-
spaces to and from cold storage on page 717.
l Name—the name used to identify the workspace. This must not exceed 50 characters.
Note: You can edit a workspace name at any time without affecting any data. The root folder name for the
workspace updates along with the workspace name.
l Matter—the case or legal action associated with the workspace. Click Select to choose a matter. The Select
Item - Matter modal displays a list of matters based on the conditions set in the MattersOnPicker view.
l Template Workspace—an existing workspace structure used to create the new workspace. Click Select to
select a template. The Select Item - Template Workspace modal displays a list of templates based on the con-
ditions set in the WorkspacesOnPicker view. For more information, see the Admin Guide.
Notes:
l Any groups that are part of a template workspace will also be a part of the client domain workspace.
We recommend removing these non-client domain groups to prevent the client domain admin from see-
ing information on non-client domain users and groups.
l We recommend selecting an empty workspace without any documents as a template to prevent poten-
tial errors when trying to clean up all the references.
l Workspace Admin and Client Domain Admin permissions are not copied from the workspace template
when a new workspace is created. They are taken from the Sys Admin permissions.
All of the following non-document objects in the template copy to the new workspace:
Note: To enable an automatic carryover of Imaging Sets to newly created workspaces, confirm the
Copy Instances on Workspace Creation setting within the corresponding Object Type template
workspace (Imaging Set) is set to Yes.
Note: Only export type Integration Point profiles with a source and destination of Relativity are copied.
l Layouts
l Markup sets
l Native types
l OCR profiles
l OCR sets
Note: To enable an automatic carryover of OCR sets to newly created workspaces, confirm the Copy
Instances on Workspace Creation setting within the corresponding Object Type template work-
space (OCR Set) is set to Yes.
Note: The SQL Server settings determine the languages available in this list. Contact your system
admin if you require additional languages. For information on configuring and managing word break-
ers, go to Microsoft's guidance on Configuring & managing word breakers & stemmers for search (SQL
server).
l Workspace Admin Group—determines the group that has workspace admin permissions over this
workspace. Click Select to choose a workspace admin group. See Workspace admin group on page 722
for more information.
l Keywords—any keywords you want to associate with the workspace.
l Notes—any notes you want to add to describe the purpose of the workspace.
Note: You must have Delete permissions for the workspace object in order to delete a workspace.
When you delete a workspace in Relativity, it automatically moves to the Recycle Bin, providing a safety net for
deleted workspaces. You can manually choose to permanently delete the workspace from the system or restore it
within the seven-day period in the Recycle Bin.
During off-hours, the Case Manager agent deletes the following:
l Any documents in the Relativity file repository, except those loaded with pointers.
l dtSearch indexes.
l Analytics indexes and staging areas.
l The SQL database (Relativity does not delete database logs and backups).
l Select or deselect one or more of the following check boxes: Ctrl, Alt, or Shift for the Control, Alt, and Shift
keys, respectively.
Note: You must select either or both the Ctrl and Alt checkboxes. Relativity displays the error message
<Invalid Keyboard Shortcut> when these checkboxes are not selected.
l In the Key drop-down menu, select a letter, number, or navigation key. The navigation keys include End, Home,
Space, Return, Down Arrow, Up Arrow, Left Arrow, Right Arrow, Page Down, and Page Up.
l
Click the Keyboard Legend icon to display a list of keyboard shortcuts currently in use by the System and
browsers. See Keyboard shortcuts legend.
l Click Clear to reset the options for keyboard shortcuts.
After you have completed your updates, click Save to display the Workspace Details page.
Note: To move multiple users between boxes, click the double arrows. You can also select and double-click
on user names to move the between boxes.
4. Click Save.
Instance level
Workspace: Manage Cold storage
l View, Edit,
Delete
l View, Edit
Note: Text migration jobs must be run before moving a workspace to Cold Storage.
Note: Migrating a workspace to cold storage is an immediate action that does not impact potential client-
related due date charges. However, once data is migrated to cold storage, it becomes inaccessible.
Notes:
l A workspace in cold storage cannot be used as a template.
l A workspace in cold storage cannot be used by Import/Export or Integration Points.
l When you move a workspace to cold storage, billing continues at the original data tier rate until the
start of the next calendar month. At that point, the system automatically switches to the cold storage
rate.
l To qualify for the discounted cold storage rate, the data must remain in cold storage for the entire
calendar month. To ensure this, move the workspace to cold storage before the end of the current
month. For example, if you move a workspace to cold storage on the 3rd of the month, you won’t
receive the discounted rate until the following month.
l When you move a case between Review and Cold Storage, the system updates the billing status
automatically. However, to qualify for the discounted cold storage rate, the case must remain in cold
storage for the entire calendar month.
l Workspaces in cold storage can be archived directly using ARM without having to be moved to an act-
ive state before archiving. See the ARM content on the RelativityOne documentation site for more
information.
l After moving a workspace to Cold Storage, it must remain there for 30 days before it can be deleted.
For example, if you move a workspace to Cold Storage on January 1st at 11:20 AM, it will be eligible
for deletion after 11:20 AM on January 31st. Once 30 days have passed, the "Delete Workspace"
button becomes available, allowing you to delete the workspace. Before 30 days, you cannot delete
the workspace directly from Cold Storage.
4. Click Retrieve Workspace to retrieve the workspace from cold storage. The Cold Storage Retrieval con-
firmation page displays.
Note: You must have permissions to the documents included in a production to remove production restrictions.
1. Create a saved search with criteria that returns documents that you want excluded from the production set.
Include family groups in your saved search so that all of the family items are kept together and can be removed
if necessary.
2. Click to edit the workspace details page. You can only update the Production Restrictions option when edit-
ing a workspace. See Creating and editing a workspace on page 709.
4. Run your production set. If a conflict occurs, you can override the production restriction if you're a system admin
with the Override Production Restrictions permission. See Workspace security.
Note: While Workspace Administrators have extensive control over their respective workspaces, they do not
automatically inherit the full range of system administrator privileges. Non-standard permissions like "New
Document" must be added. Additionally, the "Workspace" permission is initially set only to "View" status.
Note: You can only designate one group per workspace as a workspace admin group.
l You have the same fields / layouts / views available in both workspaces (repository and review) so the learning
curve for the teams administering the case is minimal.
l When you promote data between repository and review workspace (using Integration Points) you can use the
same field names and types to push data between them, reducing the opportunity for errors since both work-
spaces are born out of Template Review Workspace (Workspace –A) originally.
Below, we'll describe two scenarios for creating a Repository Workspace, followed by a few quick workflows that will
come in handy as you use those workspaces.
40.10.2 Example 1
You currently have a Review Template (Workspace-A). You can create a new workspace (Workspace-Z) from
Workspace-A, add the Repository application to Workspace-Z and designate it as a Repository Template.
1. In Repository Template Workspace-Z remember to setup the appropriate security groups that limit access to
case admins and disable access to the reviewer groups.
2. You have two designated workspace templates – one for review (Workspace–A) and one for repository (Work-
space-Z).
3. You can create Review Workspace-B and Repository Workspace-Y from these templates.
l Promotion workflow is not limited to just repository to review (ex: documents and metadata), it will also
work between review and repository (ex: overlay Priv Coding designations).
l It is recommended to tag documents that were promoted on an admin field in the repository workspace to
facilitate easy QC.
l Following promotion of, inclusive & non-duplicate emails or some documents from certain clusters, trying
to rerun the email threading or clustering (in these examples) in the review workspace, will result in dif-
ferent results, by design.
l To take advantage of the reduced data costs offered by the repository workspace, it is recommended to
promote documents via links only to review workspaces instead of storing copies of the files in the case
review workspace. If you choose to promote actual files to your case review workspace, your calculated
data usage will include both the files in the repository workspace billed at the reduced rate and the duplic-
ated files in the standard case review workspace which is billed at the standard rate (please refer to your
contract for more specific information for how this is calculated).
l If you promote documents via links from repository to review workspace – keep in mind that if you did
delete the documents in the repository workspace or delete the repository workspace itself, the links to
the promoted documents in the review workspace will be broken.
a. Administrators can load data in using Import/Export and processed data via Relativity Processing in the
repository.
b. If you are loading data via Import/Export:
i. Watch out for deduplication challenges across the mixed data.
ii. To avoid errors on retry (of processing errors), use unique control numbers that will not conflict
with the Relativity Processing Numbering scheme (Ex: HardCopy-xxxxx or LoadFile-xxxxx).
c. Process data with deduplication turned off on the processing profile and use the Processing Duplication
Workflow to cull your data. It provides better flexibility in case of changes in dedupe order / type.
l When using Analytics:
a. For structured analytics sets - Evaluate if you need to repopulate text or update only new documents. For
more information, see Running structured analytics in the Analytics guide.
b. For conceptual indexes – Evaluate if you need to do a full index update or an incremental one. For more
information, see Best practices for updating a conceptual index in the Analytics guide.
c. When clustering documents, evaluate if you would like to cluster the entire universe or just a subset of
documents based on your needs.
l Folders
l Field Tree
l Saved Searches
No matter which of these options you use, there are several display options you can use to customize your workspace.
Field Tree Browse your documents according to how they were coded or grouped.
Saved Create a new search, or browse previously saved searches.See Saved Search in the
Searches Searching Guide.
Folders
Click on the Folders icon to navigate the folder hierarchy for your workspace. The folder structure is set when
documents are imported. It can be based on the document’s source, or according to a folder structure set by your
Relativity administrator. Clicking on a folder displays that folder’s documents in the document list.
Note: To ensure stable performance, we recommend creating no more than 250,000 folders in a workspace and
having 15 sub-folders or less within each folder.
A folder often has multiple sub-folders. Click on the folder to view the sub-folders. Click on the arrow next to the folder
to hide the sub-folders.
To change the folder scope, click on the This folder and subfolders or Only this folder icon.
Field tree
Click on the Field Tree icon to display the field tree in the browser. Selected single and multiple-choice list fields and
their choices appear in a tree structure.
l New documents—click to upload new documents using Simple File Upload. If the Transcripts application is
installed in this workspace, this icon is replaced with a drop-down menu that allows you to choose between
uploading a new document or a new transcript.
l Views drop-down menu—click to select a view.
l New view—click to create a new view from within the view drop-down menu. This icon only displays if
you have permission to add a new view. If the icon is not present, contact your Relativity administrator to
add a view.
l Edit view icon—click to edit a view that displays within the view drop-down menu. This icon only dis-
plays if you have permission to edit the view. If the icon is not present, contact your Relativity admin-
istrator to edit the current view.
l Include Related Items drop-down menu—returns documents related to the documents currently in the view.
The options vary by workspace, but may include email family groups, duplicates, or similar documents.
Show Document Preview Panel icon will then display in the upper-right. Additionally, users must have the
Document Preview permission in Other Settings assigned to use this feature.
Note: The Document Preview panel does not support viewing hidden content, creating or modifying markups, or
editing coding decisions. Open the document in the Viewer instead to perform these tasks.
l Persistent Highlighting—displays or hides a panel containing any persistent highlight sets in the workspace.
Only terms that are in the current document will display in the pane. Additionally, you can control which high-
lights display in the current document by clicking on either the persistent set to only display highlights from that
set or you can click on a specific term to only see that term highlighted in the document.
l Document preview panel Viewers—click on the name of the Viewer in which you would like to view the doc-
ument. Viewer names that are displayed in black indicate that the document is available for viewing. The Viewer
that is currently open is bold with an orange underline underneath the name. If a name appears in italics, that
Viewer is not available for the current document.
l Markup set—displays the active markup set in a drop-down menu. Choose a markup set from the drop-down
menu to make a different set active. This menu only appears when viewing a document in the Image Viewer of
the Document Preview panel.
l Page navigator—use any of the following options to help you navigate the pages in the document you are pre-
viewing:
Option Description
Click to move to the first page in the document.
Icon Description
Inline Click to enable edit mode where a user can edit eligible fields from the document list.
Note: User access to Inline Editing is determined by permissions as well as on the view by a
Editing system administrator. As a result, some users may not see this icon, depending on which view
they are using.
Freeze/Un- Click the blue snowflake icon to refreeze columns that were most recently frozen. If the icon is
orange, click it to unfreeze the columns. This option only displays if you have already frozen a
freeze columns column this session.
Sampling If you have proper permissions, clicking the Sampling icon lets you create random sample sets
from the item list using three different methodologies from the pop-up menu that appears.
Show/Hide fil- Click the blue filter icon to show filters for columns in the item list. Click the orange icon to hide
them.
ters
Clear filters Click the blue clear filter icon to clear any filters applied to the item list.
Reset column Click the blue Reset column sizes icon to return to the original settings for the columns.
sizes
Turn Grid style Click the blue grid icon to turn grid style on. This shrinks the row padding and alternates row
shading to make your data more compact and easier to read. Click the orange icon to turn grid
on/off style off.
Use these navigational controls to navigate the pages in the document list.
The fields that appear in the item list are based on the selected view, which you can edit. You can also edit a view to
rearrange the order that the columns display. Contact your Relativity administrator to change the fields in your view.
To change a column’s size, hover over the white line at the edge of the column header. A double arrow appears,
indicating that you can resize the column. Drag it in either direction to adjust the column width. The other columns on
the page automatically adjust to fill the rest of the window. Column data can be cut off. If you wish to return to the
original settings click the Reset Column Sizes icon.
1. In the right-most column that you wish to freeze, hover your cursor over the column's title and click on the
ellipses.
Note: Once you have frozen a column or columns, you can freeze additional columns to the right of the
frozen columns by repeating steps 1-2.
l Hover your cursor over the right-most frozen column, click on the ellipses, and select Unfreeze Columns.
l Click the Unfreeze Columnicon in the upper-right section of the list.
Note: You can determine if a user has access to this feature by enabling or disabling the Copy Mass Operations per-
mission.
1. In the column that you wish to copy, hover your cursor over the column's title and click on the ellipses.
2. Select Copy column values.
A modal displays the total number of column values that were successfully copied to clipboard.
Note: If your item list does not contain the file icon, contact your Relativity administrator to add it.
40.11.4.5 Sorting
You can use any field in the view to sort all of the results in an item list.
Click any field heading once to sort the items in that field in ascending order, alphabetically. A down arrow appears
next to the heading name, as in the Responsive field below. Click a second time to sort the items in descending order,
alphabetically. An up arrow appears. Clicking the field name a third time clears the sort and returns the field to its
original order.
If you are not able to sort a particular field, contact your administrator to make sure the field has the Sort option set to
Yes.
A pop-up window will appear to confirm to moving the workspace to the Recycle bin.
l
To recover a workspace, click the restore icon.
l
To permanently delete a workspace, click the trash can icon.
l To move one or more workspaces to Cold Storage, click the button below the table.
41.1 Tutorials
Relativity provides video tutorials to teach you the basics of Relativity and its features. You can find the tutorials
at https://help.relativity.com/topic.html?t=H6HK2.
Note: All customer data is treated as sensitive and confidential. Relativity Support will not accept any customer data
from clients for use in Relativity software troubleshooting or software development without explicit permissions from
the client. In the rare case where customer data is necessary to troubleshoot the issue, the document
troubleshooting will be contained in the RelativityOne environment on secure region-specific RelativityOne
Jumpboxes.