View and Manage Organization Role-Based Permissions

Home > selected Organization > menu or right-click > Settings > General > Role Permissions
Project > Settings drop-down > Organization Settings > General > Role Permissions

Requires Organization - Roles - View, Add/Edit, and Delete Permissions

A user in the Organization Administrator role can always manage the role-based permissions (access rights, or privileges) in effect for the Organization's defined Administrators, Users, and Groups.

When you select Role Permissions from the Organization Settings, an Organization Administrator or user with the appropriate permissions can use the top-level context menu to perform the following action:

  • Create a role by clicking the (New Role) option, which launches the New Role dialog. Adding a custom role enables you to start with the default Project Administrator permissions and then specify your own permissions set.

For a selected role, clicking the ellipses displays a context menu of available actions:

  • Select Set as Default – This option is available to all roles including the Organization Administrator role. This option marks the selected role as the default role when using New User to add an Organization User to the Organization.
  • Edit – This option is available to all roles except the Organization Administrator role. It allows editing of the name and/or description for a role other than the Organization Administrator role (which also cannot be edited).
  • Copy – This option is available to all roles including the Organization Administrator role. It enables you to make a copy of an existing role and its set of permissions as a starting point for a new role. Supply a new, unique name for the newly copied role.
  • Delete – This option is available to all roles except the Organization Administrator role. It allows deletion of a role other than the Organization Administrator role (which cannot be deleted). A popup asking you to verify the deletion of the selected role from the Organization.

All actions that Administrators, Users, and Groups can perform are based on a selected role and the individual actions permitted or denied for that role.

Note: When determining permissions, the software considers both the individual User role (if applicable) and the role the User has within a Group. If an Organization User has both an individual User role as well as a Group role, the permissions for that User represent a "union" of the individual User's permissions and the Group permissions. Effectively, this means that the User gains the higher permission level when comparing each permission in the User role versus the Group role.

In addition to the Organization Administrator, the predefined roles aim to accommodate a common set of permissions that control actions on Project objects. If these roles are not sufficient, new roles can be defined with selected permissions. Any new roles defined and applied will subsequently appear in the role drop-down list when a user account is created.

Note: You cannot alter the permissions for the Organization Administrator role. All permissions are enabled for this role.

The provided roles include the following:

  • Role — A role represents a set of permissions to apply actions to objects. If you have the appropriate permissions you can select the default role (determined by the Set as Default option from Role Permissions), another of the predefined roles, or a custom role created for the Organization. By default, the predefined roles have the following permissions:
    • Organization Administrator — Always has permissions to manage all Organization Settings and all aspects of Projects within the Organization; cannot be edited or deleted.
    • Project Administrator — Has view permissions for all Project Data nodes in the Navigation Tree and add/edit permissions for some of those nodes, such as Tags, Folders, Saved Searches, Workflows, Comparisons, and Synthetic Documents. Also has document-related permissions to add or remove Tags from documents and documents from a Folder, download native document and PDFs, and view document reports, as well as view permissions for some settings and the ability to edit the list of Metadata View Fields.
    • Project Member – Has limited permissions to perform general document search and analysis, but not to control any aspects of the Project.
    • Claimant — Used in Reef Claims (previously known as Class Action) Projects on a Reef Express system; not intended for use in eDiscovery.

Note: At least one Organization Administrator must be available in the Organization, so you will not be able to remove permissions from the last available (or only) Organization Administrator.

The Organization's Roles list provides a central location for managing permissions across key Organization objects and objects in a Project. The object permissions for each of the Organization roles appears in the list. If you have the appropriate permission, you can select a role to see the per-object permissions for that role.

The provided roles are intended to support common permission levels. If you have the Organization - Role Permissions - Add/Edit permission and you want to change the individual permissions for a provided role (for example, Project Administrator), it is good practice to make a copy of that role instead of editing the individual permissions for the existing role. That way, you can preserve the original permission set. Having Organization - Role Permissions - Add/Edit permission enables you to add, edit, and copy roles, and use the checkboxes for an editable role to change permissions on a per-object basis. To assign custom permissions:

  • Identify the role for which you want to assign custom permissions.
  • Examine the appropriate permissions.
  • Identify any actions that you want to change.
  • Select or clear the checkboxes controlling the actions for the appropriate role. (Selecting a checkbox grants permissions to perform the action; clearing a checkbox denies permissions to perform the action.)
  • Make sure that for the actions you include, you have all of the associated permissions set as well. For example, New Project requires a set of permissions to be in place to ensure that the Project is available with all the required entities. Without all of the associated permissions in place for New Project, the Project cannot be initialized.

Some permissions are controlled with a single checkbox setting. However, many eDiscovery permissions for the Work Basket, Navigation Tree items, and Settings provide the following levels of permissions:

  • View – Ability to view the object.
  • Add/Edit – Ability to not only view the object, but also create or edit the object.
  • Delete – Ability to not only view and add/edit the object, but also delete the object.

Note: The dependencies between the permissions are maintained as you check or clear boxes. For example, clearing View for a given object will automatically clear Add/Edit and Delete for that object, if they are set. Or, clearing Add/Edit for an object will also clear Delete, if set. Likewise, setting Add/Edit for an object will also set View. Setting Delete for an object will also set View and Add/Edit.

In general, be aware of the following:

  • Any given dialog may require multiple permissions to support different actions or lists. If you do not have all the required permissions for a given dialog, an error in the dialog will help you identify the missing permission. In general, the default roles are designed to accommodate related permissions. If you modify a role such as Project Administrator or add your own role, make sure that you have all the permissions needed (for example, creating a Project requires multiple permissions).
  • Multi-section dialogs and dedicated popups that are intended to include one or more lists of items for selection require the corresponding object's View permission in order to populate the list. For these dialogs and popups, note the following if you start changing individual permissions for a role:
    • Within a multi-section dialog, you will see an error if you lack the View permission that controls a given list.
    • For a popup than uses individual tabs for lists (for example, Project-level, Organization-level and System-level template lists), you will only see the tabs for which you have permissions (for example, Project-level View permission for a setting with Project templates, Organization-level View permission for a setting with Organization templates, or System-level View permission for a setting with System Templates. (You must be a System User in a role with at least View permission to see a list of System templates for a particular type of template.)
  • In general, if you do not have permission to perform an individual action, you will not see the option in the list of available options. This includes right-click options for a view in the Navigation Tree, options on the Document drop-down menu for a given document list, Dashboard or tab-specific toolbar options, options for an individual chart on a Reports tab, or select options within a dialog/popup. It also applies to ellipses menu operations for Settings when you do not have permissions to perform any of the operations (for example, if you lack the permissions to perform Save to Template and Load from Template operations for Alias Lists).
  • To open and gain access to a Project, you must have the following permissions:
    • Project Data - View
    • Work Basket - View
    • Project-level Preferences - View
    • Project-level Search Settings - View

These View permissions should remain enabled to ensure proper functioning of the application (for example, a user needs to see Work Basket tasks generated for operations, and needs view access to Project Data ).

Projects – Controls access to Projects in an Organization.

  • View (Projects - View permission) – All default roles have View access to Projects in an Organization. This permission is not editable and is shown set and grayed out.
  • Add/Edit (Projects - Add/Edit permission) – By default, only an Organization Administrator can use the following options from the Home page:
    • Selected Organization > New Project (which also requires Imports - Add/Edit, Project Data - Add/Edit, Organization - Role Permissions - View, Organization - Users - View, Organization - Groups - View, Project Members - Add/Edit, and View permissions for each Organization Setting with a template. System-level View permission is needed to list System Templates for the Settings. (You must be a System User in a role with at least View permission to see a list of System templates for a particular type of template.)
    • Selected Organization > Import Project (which also requires Connector Access permission and Organization - Project Data Areas - View permission).
    • Selected Project > Export to Export an entire Project (which also requires Connector Access permission and Organization - Project Data Areas - View permission).
    • Selected Project > Edit (to edit a selected Project's name or description).
  • Delete (Projects - Delete permission) – By default, only an Organization Administrator can delete a Project from the Home page (selected Project > Delete).

Work Basket – Controls access to the Work Basket area as well as the ability to control the display of items in the Work Basket.

  • View (Work Basket - View permission) – By default, all provided roles have View access to the Work Basket.
  • Add/Edit (Work Basket - Add/Edit permission) – By default, an Organization Administrator or a Project Administrator have access to the following Work Basket task options and can control Work Basket states:
    • Task Notification (right-click option)
    • Cancel Task (right-click option) and (Cancel) state
    • (Pause) state
    • (Resume) state
  • Delete (Work Basket - Delete permission) – By default, only an Organization Administrator can delete a selected Work Basket task using the right-click Delete Task(s) option or using the (Delete) state icon.

Navigation Tree Node

This section contains permissions that control access to eDiscovery items in the Project Navigation Tree.

Imports – Controls access to the Imports node in the tree and all associated Data Sets and reports.

  • View (Imports - View permission) – By default, only an Organization Administrator can view the information for all Imports and individual Data Sets. This includes the ability to see the Imports node in the tree, which controls the following:
    • Imports Summary and Imports Reports tab
    • Individual Data Sets under Imports (Data Set All Docs, Exceptions, and Reports tabs)
    • View Configuration option for a Data Set
    • Select Target popup > selection of all Imports or a Data Set as a search target
  • Add/Edit (Imports - Add/Edit permission) – By default, only an Organization Administrator can add and manage Data Sets under Imports, which includes the following options:
    • Needed for New Project (as one of the permissions needed to set up required entities within a Project)
    • Imports > New Data Set
    • Imports > New Data Set from Load File
    • Imports > Add Shared Data Set, which also requires Organization - Shared Data Sets - View and Projects - Add/Edit, and, for adding to Project Data, also Project Data - Add/Edit
    • Selected Data Set > Copy to Document Storage, which also requires Project - Index Settings - View
    • Selected Data Set > Edit of a Data Set
    • Selected Data Set > Share | Unshare
    • Selected Data Set > Reindex
    • Search results for all Imports or a Data Set > Create Data Set from Search Results
    • Search results for all Imports or a Data Set > Update Metadata
    • Search results for all Imports, a Data Set > Reprocess, Project Data-based results or a Workflow Step > Reprocess
    • OCR Candidates Report > Drill-through Search results for all Imports or a Data Set > OCR, which also requires Project - Index Settings - View permissions
    • Warnings and Errors Report > Drill-through Search results for all Imports or a Data Set > Extract Office 365 Data
    • Data Set Search Results > Copy to External Area (which also requires Connector Access permission)
    • Data Set Search Results > Load from External Area (which also requires Connector Access permission)
  • Delete (Imports - Delete permission) – By default, only an Organization Administrator can delete a selected Data Set or files from a Data Set:
    • Selected Data Set > Delete
    • Search results for all Imports or a Data Set > Document menu > Delete File(s) from Project

Exports – Controls access to the Exports node in the tree and all associated Export Streams and Volumes. To view Exports, it is assumed that you have Project Data - View permissions.

  • View (Exports - View permission) – By default, all provided roles have View access to Exports in the tree, which controls the following:
    • Exports Summary
    • Each individual Export Stream and associated Export Volume under Exports
    • Select Target popup > selection of an Export Stream as a search target
    • Selected Project Data-based search result from Navigation tree, Search History, a selected Workflow Step > Create Export Comparison Report or a selected Workflow > Reports tab > Generate More Reports > Export Comparison Report
  • Add/Edit (Exports - Add/Edit permission) – By default, only an Organization Administrator can add or manage Export Streams and Volumes in a Project. This permission controls the options for an Export Stream and Volume, as follows:
    • Exports > New Export Stream
    • Selected Export Stream > New Export Volume
    • Selected Export Stream > Export All Staged
    • Selected Export Stream or Export Volume > Generate Load File
    • Selected Export Stream > Export Duplicates Volume
    • Selected Export Stream > Create Near-Duplicate Metadata
    • Selected Export Stream > Update Custodians
    • Selected Export Stream > Edit
    • Selected Export Volume > Inclusion/Exclusion checkbox
    • Selected Export Volume > Export
    • Selected Export Volume > Update
  • Delete (Exports - Delete permission) – By default, only an Organization Administrator can delete an Export Stream or last (highest-numbered) Volume using the Delete option.

Project Data – Controls access to the top-level Project Data node in the tree.

  • View (Project Data - View permission) – By default, all provided eDiscovery roles have View access to Project Data. This includes the ability to select Project Data in the tree and as a search target in the Select Target popup. This permission is generally required to view any item that is classified as part of Project Data, including Custodians, Folders, Tags, the Discard Pile, and also for Exports and Workflows. To ensure proper functioning, do not disable this permission.
  • Add/Edit (Project Data - Add/Edit permission) – By default, only an Organization Administrator can control the content within Project Data. This includes the following:

    • Needed for New Project (as one of the permissions needed to set up required entities within a Project)

    • Add to Project Data checkbox in New Data Set, Add Shared Data Set, and Create Data Set from Results dialogs
    • Selected Data Set from Navigation Tree or Imports Summary, Data Set or Imports results > Add to Project Data
    • Selected Data Set from Navigation Tree or Imports Summary, Data Set or Imports Results > Project Data-based results or Workflow Step > Remove from Project Data
    • Add to (for adding documents from a Data Set or Imports-based view to a Custodian or Folder within Project Data, which requires both this permission and Document - Add to/Remove from a Custodian or Document - Add to/Remove from a Folder permission).
    • Add Tags (for tagging from a Data Set or Imports-based view, which requires both Project Data - Add/Edit permission and Document - Add/Remove Tag(s) permission, since the tagging adds the tagged documents to Project Data and then performs tagging). Add Tags generally requires Document - Add/Remove Tag(s) permission.
    • Project Data > Import External Images
    • Project Data Search Results > Copy for External Imaging
    • Add Family (for Project Data views such as a Custodian, Tag, or Folder view)
  • Delete (Project Data - Delete permission) – Currently, not applicable.

Custodians – Controls access to the Custodians node under Project Data in the tree, and in all popups providing a list of Custodians.

  • View (Custodians - View permission) – By default, all roles have View access to Custodians. This includes the following:
    • Custodians Summary
    • Each individual Custodian view
    • Select Target popup > list of Custodians and selection of a Custodian as a search target
    • Add to or Remove from popup > listing of Custodians
    • Advanced Search > Custodians section
  • Add/Edit (Custodians - Add/Edit permission) – By default, only an Organization Administrator can use the following:
    • New Custodian from the tree, Summary, or Add to popup.
    • Selected Custodian > Edit
  • Delete (Custodians - Delete – By default, only an Organization Administrator can use the Delete option for a selected Custodian.

MediaIDs – Controls access to the MediaIDs node under Project Data in the tree, and in all popups providing a list of MediaIDs.

  • View (MediaIDs - View permission) – By default, all roles have View access to MediaIDs. This includes the following:
    • MediaIDs Summary
    • Each individual MediaID view
    • Select Target popup > list of MediaIDs and selection of a MediaID as a search target
    • Add to or Remove from popup > listing of MediaIDs
  • Add/Edit (MediaIDs - Add/Edit permission) – By default, only an Organization Administrator can use the following:
    • New MediaID from the tree, Summary, or Add to popup.
    • Selected MediaID > Edit
  • Delete (MediaIDs - Delete – By default, only an Organization Administrator can use the Delete option for a selected MediaID.

Batches – Controls access to the Batches node under Project Data in the tree, and in all popups providing a list of Batches.

  • View (Batches - View permission) – By default, all roles have View access to Batches. This includes the following:
    • Batches Summary
    • Each individual Batch view
    • Select Target popup > list of Batches and selection of a Batch as a search target
    • Add to or Remove from popup > listing of Batches
  • Add/Edit (Batches - Add/Edit permission) – By default, only an Organization Administrator can use the following:
    • New Batch from the tree, Summary, or Add to popup.
    • Selected Batch > Edit
  • Delete (Batches - Delete – By default, only an Organization Administrator can use the Delete option for a selected Batch.

Tags – Controls access to the Tags node under Project Data in the tree and all popups that provide a list of Tags, and governs the Project-level Add/Edit and Delete operations for Tags.

  • View (Tags - View permission) – By default, all roles have View access to Tags in Project Data. This includes the following:
    • Tags Summary
    • Each individual Tag view
    • Viewing of Project Settings > Tags
    • Select Target popup > list of Tags and selection of a Tag view as a search target

    • Within a Workflow, listing of Project Tags (user can select multiple)

    • Advanced Search > Tags section
  • Add/Edit (Tags - Add/Edit permission) – By default, an Organization Administrator or a Project Administrator can use the following:
    • New Tag (from Tags Summary, Add Tags popup, the Document Viewer, Project Settings, and New Tag when using Select Tags to create a Tag to use in a Workflow)
    • Project Settings > Selected Tag > Edit
    • Project Settings > Load from Template
  • Delete (Tags - Delete permission) – By default, only an Organization Administrator can use Project Settings > Selected Tag > Delete.

Folders – Controls access to the Folders node under Project Data in the tree, and in all popups providing a list of Folders.

  • View (Folders - View permission) – By default, all roles have View access to Folders. This includes the following:
    • Folders Summary
    • Each individual Folder view
    • Select Target popup > list of Folders and selection of a Folder as a search target
    • Add to or Remove from popup > listing of Folders
    • Within a Workflow, listing of Folders (user can select only one)
    • Advanced Search > Folders section
  • Add/Edit (Folders - Add/Edit permission) – By default, only an Organization Administrator or Project Administrator can use the following:
    • New Folder (from tree, Folders Summary, Add to popup, New Folder to create a Folder to use in a Workflow)
    • Selected Folder > Edit
  • Delete (Folders - Delete permission) – By default, only an Organization Administrator can use the Delete option for a selected Folder.

Discard Pile – Controls access to the Discard Pile under Project Data in the tree.

  • View (Discard Pile - View permission) – By default, all provided roles have View access to the Project Data Discard Pile.
  • Add/Edit (Discard Pile - Add/Edit permission) – By default, only an Organization Administrator can control population of the Discard Pile using the following:
    • Project Data-based view > All Docs Document menu > Send to Discard Pile
    • Discard Pile > Restore
  • Delete – Not applicable.

Saved Searches – Controls access to the Saved Searches node under Searches in the tree.

  • View (Saved Searches - View permission) – By default, all roles have View access to Saved Searches. This includes the following:
    • Saved Searches Summary
    • Each individual Saved Search
    • Select Target popup > selection of a Saved Search as a search target.

    • Selected Workflow > selected Workflow Step > Edit (query) > Saved Searches tab

  • Add/Edit (Saved Searches - Add/Edit permission) – By default, an Organization Administrator or a Project Administrator can use the following:
    • Term-based search results > Save Search
    • Selected Saved Search > Edit
  • Delete (Saved Searches - Delete permission) – By default, only an Organization Administrator can use the Delete option for a selected Saved Search.

Workflows – Controls access to the Workflows node of the tree. To view Workflows, it is assumed that you have Project Data - View access.

  • View (Workflows - View permission) – By default, all roles have View access to Workflows. This includes the following:
    • Workflows Summary
    • Each individual Workflow and its Steps
    • Select Target popup > selection of a Workflow step as a search target.

    Note: Workflows - View permission is the minimum permission required to use the Validate and Run options for existing Workflows.

  • Add/Edit (Workflows - Add/Edit permission) – By default, only an Organization Administrator or Project Administrator can use the following:
    • New Workflow from Summary or tree
    • Selected Workflow > Copy
    • Selected Workflow > Edit (name or description)
    • Workflow Content tab configuration, including Save Changes, Discard Changes, Select Target, Step - all Edit menu actions, Step - Report Description, Step - Comments.
    • Workflow Tag selection and removal, including to Select Tags (which also requires Document - Add/Remove Tag(s) permission) and Remove Tag x button. Note that Tags - View permissions is also required to view the Tags, andTags - Add/Edit permission is also required for New Tag.
    • Workflow Folder selection and removal, including to Select Folder (which also requires Document - Add to/Remove from a Folder permission) and Remove Folder x button). Note that Folders - View permission is also required to view the Folders. Folders - Add/Edit permission is also required for New Folder.
  • Delete (Workflows - Delete permission) – By default, only an Organization Administrator can use the Delete option for a selected Workflow.

Comparisons – Controls access to the Comparisons node under Analytics in the tree.

  • View (Comparisons - View permission) – By default, all roles have View access to Comparisons, including the following:
    • Comparisons Summary
    • Each Comparison view
  • Add/Edit (Comparisons - Add/Edit permission) – By default, only an Organization Administrator or Project Administrator can use the following:
    • New Comparison from the tree or Summary
    • Selected Comparison > Edit
  • Delete (Comparisons - Delete permission)– By default, only an Organization Administrator can use the Delete option to delete a Comparison.

Synthetic Documents – Controls access to the Synthetic Documents node under Analytics in the tree.

  • View (Synthetic Documents - View permission) – By default, all roles have View access to Synthetic Documents, including the following:
    • Synthetic Documents Summary
    • Each individual Synthetic Documents in the tree (including the History tab)
  • Add/Edit (Synthetic Documents - Add/Edit permission) – By default, an Organization Administrator or a Project Administrator can use the following:
    • New Synthetic Document from the tree or Summary
    • Selected Synthetic Document > Edit
    • Synthetic Document tab configuration, including Synthetic Document text, Comment, Save and Discard Changes buttons.

    • Document Viewer > Add Selected Text to > Synthetic Document

  • Delete (Synthetic Documents - Delete permission) – By default, only an Organization Administrator can use the Delete option to delete a Synthetic Document.

Document Actions:

This section contains checkbox permissions related to document actions.

Add /Remove Tag(s) (Document - Add/Remove Tag(s) permission) – Controls the ability to apply Tags to documents and remove Tags from documents. By default, an Organization Administrator or a Project Administrator can add or remove Tags from documents. Adding or removing Tags affects the population of Tag views in the Navigation Tree. In general, to view a list of Tags, you also need Tags - View permission. Operations affected by this permission include the following:

  • Add Tags (from an entire view in the tree, from the Document drop-down on a document list, from the Tags area of the Document Viewer with the Tag checkboxes, Tag Queue, Comment box, and Apply Queue, from applicable Reports Details popups, and from applicable Work Basket tasks) for one or more selected Tags. (When tagging from a Data Set or Imports-based view or report, you must also have Project Data - Add/Edit permission, since tagging adds the affected document to Project Data and then performs tagging.)
  • Remove Tags (from an entire view in the tree, from the Document drop-down on a document list, from the Tags area of the Document Viewer with the Tag checkboxes, Tag Queue, Comment box, and Apply Queue, from applicable Reports Details popups, and from applicable Work Basket tasks) for one or more selected Tags.
  • Reprocess dialog > Apply Parent Tags to Children for one or more selected Tags. Also, Reprocess generally requires Imports - Add/Edit permission.
  • Reprocess dialog > Apply New Tags to Children for one or more selected Tags. Also, Reprocess generally requires Imports - Add/Edit permission.
  • Selected Workflow > Content tab > to Select Tags (which also requires Workflows - Add/Edit permission).

Note: Creation of a Tag with New Tag requires Tags - Add/Edit permission.

Add to / Remove from a Folder (Document - Add to/ Remove from a Folder permission) – Controls the ability to add documents to a Folder and remove documents from a Folder. By default, an Organization Administrator or a Project Administrator can add and remove documents from a Folder. In general, to view a list of Folders, you also need Folders - View permission.

  • Add to (from an entire view in the tree, from the Document drop-down on a document list, from applicable Reports Details popups, and from applicable Work Basket tasks) for a selected Folder. When performing the operation from a Data Set or Imports-based view or report, you must also have Project Data - Add/Edit permission.
  • Remove from (from an entire view in the tree, or from the Document drop-down on a document list, from applicable Reports Details popups, and from applicable Work Basket tasks) for a selected Folder.
  • Selected Workflow > Content tab > to select a Folder (which also requires Workflows - Add/Edit permission).

Note: Creation of a Folder with New Folder requires Folders - Add/Edit permission.

Add to / Remove from a Custodian / Batch / MediaID (Document - Add to/ Remove from a Custodian / Batch / MediaID permission) – Controls the ability to add documents to a Custodian, Batch, or MediaID view and remove documents from a Custodian, Batch, or MediaID view. By default, only an Organization Administrator can add and remove documents from a Custodian, Batch, or MediaID view. In general, to view a list of Custodians, Batches, or MediaID views, you also need Custodians - View, Batches - View, or MediaIDs - View permissions.

  • Add to (from an entire view in the tree or from the Document drop-down on a document list, from applicable Reports Details popups, and from applicable Work Basket tasks) for a selected Custodian, Batch, or MediaID view. When performing the operation from a Data Set or Imports-based view or report, you must also have Project Data - Add/Edit permission.
  • Remove from (from an entire view in the tree, or from the Document drop-down on a document list, from applicable Reports Details popups, and from applicable Work Basket tasks) for a selected Custodian, Batch, or MediaID view.

Note: Creation of a Custodian with New Custodian requires Custodians - Add/Edit permission. Creation of a Batch with New Batch requires Batches - Add/Edit permission. Creation of a MediaID with NewMediaID requires MediaIDs - Add/Edit permission.

Download Native (Document - Download Native permission) – By default, all roles have permission to download native documents. This permission controls the availability of the following:

  • Document Viewer toolbar option > Nativefor download of a single native document.
  • Download Native option from the Document drop-down on a document list. You can download selected documents on a page of a document list or all documents in a list (with a warning) in native format.
  • Download All Natives right-click option for an entire view in the Navigation Tree or right-click option for an applicable Work Basket task. After display of a warning, you can proceed to download all natives in a view (for example, a Data Set, Project Data, a Custodian, MediaID, Batch, Tag, Folder, search result, Saved Search, or Workflow Step), or all natives for an applicable Work Basket task such as a search result.

Download PDF (Document - Download PDF permission) – By default, all roles have permission to download PDF versions of native documents. The permission controls the availability of the following:

  • Document Viewer toolbar option > PDF for download of a single document in PDF format, as long as the document has existing stored images, as shown on the Image tab.
  • Download as PDF option from the Document drop-down on a document list for download of selected documents on a page or all documents in the list (with a warning) as PDF.
  • Download All as PDFs right-click option for an entire view in the Navigation Tree or right-click option for an applicable Work Basket task. After display of a warning, you can proceed to download all documents as PDFs for a view (for example, a Data Set, Project Data, a Custodian, MediaID, Batch, Tag, Folder, search result, Saved Search, or Workflow Step), or for an applicable Work Basket task such as a search result.

Other

This section provides permissions to control Connector Access, Project Monitoring Access, and access to auditing-related items, document reports, and the ability to lock or unlock a Workflow.

Connector Access (Connector Access permission) – By default, only an Organization Administrator can select Connector locations for the following operations :

  • Imports > New Data Set (for Connector list)
  • Imports > New Data Set from Load File (for Connector list)
  • Exports > New Export Stream (for listing Export Data Areas for a read/write Connector)
  • Selected Export Stream > New Export Volume (for listing Export Data Areas for a read/write Connector)
  • Generate Load File (for listing Export Data Areas for a read/write Connector)
  • Update Export (for listing Export Data Areas for a read/write Connector)
  • Creation of a Load File Import Template (for Discover Fields with Connector list and Folder navigation)
  • Home Page > Selected Organization > Import Project (for Connector access to a Project Data Area)
  • Home Page > Selected Project > Export (for Connector access to a Project Data Area)
  • Create Manifest with the Save to Server option (Create Manifest generally requires Document Reports permission)
  • (Download)Word List with the Save to Server option
  • Bulk Search with Load from file > Connector file
  • Project Data > Import External Images
  • Data Set Search Results > Copy to External Area
  • Data Set Search Results > Load from External Area
  • Warnings and Errors Report > Drill-through Search results for all Imports or a Data Set > Extract Modern Attachments.
  • Project Data-based Search Results > Copy for External Imaging

Project Monitoring Access (Project Monitoring Access permission) – Controls access to System Status information for components used by a Project, accessible using the (Critical) or (Warning) icon on the main Project toolbar (when appropriate, one of these icons will appear instead of the standard book icon that precedes the Project name). By default, only an Organization Administrator can view this Status information.

Audit Access (Audit Access permission) – By default, only an Organization Administrator can view and use the following:

  • View Audit Log
  • Generate Billing Report
  • Generate Source Tracking Report
  • Generate Processing Report
  • the History tab of the Document Viewer
  • the Search History Owner column All selection from Search History or from a Workflow Step > Edit (query) > Search History tab
  • the Tasks from all users option in the Work Basket, which would also allow searches from other users to appear in the Work Basket instead of just the current user's own searches. (It is assumed that you have the View permission for the target view searched in order to open the search results from another user.)

Document Reports (Document Reports permission) – By default, all roles have this permission, which controls use of the following:

  • Create Manifest option for an accessible view
  • to download all accessible reports, and individual report details, on the Reports tab of a view based on permissions
  • from the Exception Details for all Imports or a Data Set (assumes Imports - View permissions).
  • Clusters tab > Generate Report
  • Communication Grid tab > Generate Report
  • Domain Grid tab > Generate Report
  • Work Basket > selected task for generated report >
  • Workflow > Workflow Report >
  • Export Volume Report >
  • Word List for a view >
  • Download Metadata option from the Document Viewer

Workflow Lock/Unlock (Workflow Lock/Unlock permission) – By default, only an Organization Administrator can use the Lock option (or lock icon within a Workflow) to explicitly lock or unlock an existing Workflow. Note that this permission is not required in order to perform an edit or deletion of a Workflow (but Workflows - Add/Edit permission is required for editing and Workflows - Delete permission is required for deleting a Workflow).

DR Access (DR Access permission) – By default, all core eDiscovery roles (Organization Administrator, Project Administrator, and Project Member) have this permission enabled to ensure access to the eDiscovery application.

Setting

This section describes permissions related to the various settings at the appropriate levels (Project and Organization).

Note: Any Organization Setting View permission (or higher) lets a user select the Settings option for an Organization on the Home Page and view the Organization Settings. Any Project Setting View permission (or higher) lets a user select the Settings option for a Project on the Home Page and view the Project Settings.

Preferences – Controls access to Project-level Preferences, which include options for the Time Zone and Hide Duplicates in Lists.

  • Project-level View (Project - Preferences - View permission) – By default, all three default roles have View access to Project Preferences.
  • Project-level Add/Edit (Project - Preferences - Add/Edit permission) – By default, only an Organization Administrator can modify the Project Preferences (that is, make selections, use Save or Discard Changes). This permission also controls the Dashboard > Enable Dashboard Reports checkbox.

Email Delivery – Controls access to Project-level Email Delivery settings, which enable email delivery of Workflow Reports and Export Comparison Reports to one or more email addresses.

  • Project-level View (Project - Email Delivery - View permission) – By default, only an Organization Administrator can view the Email Delivery settings.
  • Project-level Add/Edit (Project - Email Delivery - Add/Edit permission) – By default, only an Organization Administrator can modify the Email Delivery settings (that is, make selections and use Save or Discard Changes).

Project Members – Controls access to the list of users and groups who are members of the Project.

  • Project-level View (Project - Project Members - View permission) – By default, only an Organization Administrator can view the list of Project Members. Note that the list will be populated as long as the Organization - Users - View, Organization- Groups - View, and Organization - Role Permissions - View permissions are enabled.
  • Project-level Add/Edit (Project - Project Members - Add/Edit permission)– By default, only an Organization Administrator can modify the list of Project Members (that is, use the Add/Remove Members popup, select a role with the Role column drop-down, and use Save or Discard Changes).

Connectors – Controls access to the list of configured Connectors in the Organization and the ability to add, edit, and delete Connectors.

  • Organization-level View (Organization - Connectors - View permission) – By default, only an Organization Administrator can view Connector information in the Settings.
  • Organization-level Add/Edit (Organization - Connectors - Add/Edit permission) – By default, only an Organization Administrator can use New Connector to add a Connector, or use Edit to modify information for a selected Connector. This permission also enables use of the Connector Validate option and the Deactivate option. This permission is also required to add or edit Data Areas, associated with the appropriate Data Area Add/Edit permission (for example, Organization - Export Data Areas - Add/Edit permission).
  • Organization-level Delete (Organization - Connectors - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Connector.

Project Data Areas – Controls access to the list of configured Project Data Areas under Settings and for Project Export/Import, and the ability to add, edit, and delete Project Data Areas in the Organization.

  • Organization-level View (Organization - Project Data Areas - View permission) – By default, only an Organization Administrator can view Project Data Area information.
  • Organization-level Add/Edit (Organization - Project Data Areas - Add/Edit permission) – By default, only an Organization Administrator can use New Project Data Area to add a Project Data Area or use Edit to modify information for a selected Project Data Area, if the Organization - Connectors - Add/Edit permission is also set.
  • Organization-level Delete (Organization - Project Data Areas - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Project Data Area.

Export Data Areas – Controls access to the configured Export Data Areas needed for eDiscovery Export and other operations, and the ability to add, edit, and delete Export Data Areas in the Organization.

  • Organization-level View (Organization - Export Data Areas - View permission) – By default, only an Organization Administrator can view Export Data Area information in the Settings.
  • Organization-level Add/Edit (Organization - Export Data Areas - Add/Edit permission) – By default, only an Organization Administrator can use New Export Data Area to add an Export Data Area or use Edit to modify information for a selected Export Data Area, if the Organization - Connectors - Add/Edit permission is also set.
  • Organization-level Delete (Organization - Export Data Areas - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Export Data Area.

Shared Data Sets – Controls view access to the list of Shared Data Sets available under Organization Settings and in the Add Shared Data Set dialog.

  • Organization-level View(Organization - Shared Data Sets - View permission) - By default, only an Organization Administrator can view Shared Data Set information.

Export Databases – Controls access to the list of configured Export Databases in the Organization and the ability to manage Export instances.

  • Organization-level View (Organization - Export Databases - View permission) – By default, only an Organization Administrator can view Export Database information.
  • Organization-level Add/Edit (Organization - Export Databases - Add/Edit permission) – By default, only an Organization Administrator can use New Database to add an Export Database or use Edit to modify information for a selected Export Database.
  • Organization-level Delete (Organization - Export Databases - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Export Database instance.

Users – Controls access to the list of configured Users and the ability to manage Organization Users.

  • Organization-level View (Organization - Users - View permission) – By default, only an Organization Administrator can view User information. This permission is generally required list Users (individual Users and Users within Groups) and is required for use of Add/Remove Members.
  • Organization-level Add/Edit (Organization - Users - Add/Edit permission) – By default, only an Organization Administrator can use New User to add an Organization User or use context menu options such Edit to modify Organization User information using the eDiscovery application. Note that Retry TP Auth Setup will apply only to User entries on a TP Auth systems that have a status of Failure, and Change Password and Unlock will apply only to User entries on systems configured for Standard Authentication. Note that New User and Edit for an Organization User also require Organization - Role Permissions - View permission for role selection.
  • Organization-level Delete(Organization - Users - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Organization User from the eDiscovery application.

Groups – Controls access to the list of configured Groups and the ability to manage Organization Groups.

  • Organization-level View (Organization - Groups - View permission) – By default, only an Organization Administrator can view Group information. This permission is required to view Organization Groups, which also requires Organization - Users - View to list the Users in a selected Group.
  • Organization-level Add/Edit (Organization - Groups - Add/Edit permission) – By default, only an Organization Administrator can use New Group to add an Organization Group or use Add/Remove Members to modify Organization Group members using the eDiscovery application. Note that the ability to view Groups and the Users in the Group as well as the ability to control Group members with Add/Remove Members requires Organization - Users - View permission. Note that New Group and Edit for a Group also require Organization - Role Permissions - View permission for role selection.
  • Organization-level Delete (Organization - Groups - Delete permission) – By default, only an Organization Administrator can use Deletefor a selected Organization Group using the eDiscovery application.

Role Permissions – Controls access to the list of configured Roles and the associated permissions, as well as the ability to manage Roles.

  • Organization-level View (Organization - Role Permissions - View permission) – By default, only an Organization Administrator can view Role Permissions information under Role Permissions in the Organization Settings, and select a Role for an Organization User or Group (for example, when choosing Project Members for a new Project or as part of the Project Members Setting, or when adding/editing Organization Users and Groups from the Organization Settings).
  • Organization-level Add/Edit (Organization - Role Permissions - Add/Edit permission) – The Organization Administrator role cannot be modified at all, although it can be copied. Other provided Roles as well as Custom Roles can be edited. By default, only an Organization Administrator can use the following:
    • (New Role) to add a Role
    • Set as Default (Organization Administrator Role is the default Role)
    • Edit (name, for Roles other than Organization Administrator)
    • Copy
    • Make checkbox selections for an eligible Role.
    • Save or Discard Changes
  • Organization-level Delete (Organization - Role Permissions - Delete permission) – By default, only an Organization Administrator can use Delete for a selected, eligible Role (other than the Organization Administrator role). The Organization Administrator Role cannot be deleted. Other provided Roles as well as Custom Roles can be deleted.

Container Key Files Controls access to the list of configured Container Key Files, which help processing of password-protected Lotus Notes NSF files or Microsoft BitLocker-encrypted disk partitions. Container Key Files are at the Organization level only.

  • Organization-level View (Organization - Container Key Files - View permission) – By default, only an Organization Administrator can view Container Key File information.
  • Organization-level Add/Edit (Organization - Container Key Files - Add/Edit permission) – By default, only an Organization Administrator can use New Key File to add a Container Key File or Edit to modify information for a selected Container Key File.
  • Organization-level Delete (Organization - Container Key Files - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Container Key File.

About Save to Template and Load from Template Operations for Settings

For the following settings, which apply to both the Project- and Organization-level, the Save to Template and Load from Template template commands generally require the following:

Note: If you do not have the permissions needed to perform either of these operations for a given Setting, you will not see the ellipses menu for the Setting.

  • Save to Template - You must have Add/Edit permissions for a given Organization-level Setting to use the Save to Template option to save Project settings to an Organization template for that Setting. You can either select an existing Organization template (including the Default template), or you can select the top-level (New Template,) which launches the New Template dialog.
  • Load from Template - You must have Add/Edit permissions for a given Project-level Setting to use the Load from Template option to load settings from a selected Organization template. Loading from an Organization template also requires Viewpermissions for that Organization Setting, to list the Organization templates on the Organization Templates tab in the Load from popup. In general, the listing of System Templates on the System Templates tab in the dialog requires System-level View permission for a given Setting. (This means you must be a System User in a role with at least View permission to see a list of System templates for a particular type of template in the dialog.) Note that not all Settings can be configured in templates at the System level (for example, Alias Lists).

Alias Lists – Controls access to the Alias Lists and email Aliases within each list.

  • Project-level View (Project - Alias Lists - View permission) – By default, all three default roles have the ability to view Project-level Alias List information. This permission is also required to use the Advanced Search > Alias Lists section.
  • Project-level Add/Edit (Project - Alias Lists - Add/Edit permission) – By default, an Organization Administrator or Project Administrator can use the following:
    • Load from Template
    • New Alias List to add Project-level Alias Lists
    • Selected Alias List > Edit
    • Add Aliases to add Aliases within a List
    • Selected Alias(es) > Delete Selected to delete selected Aliases.
    • Document Viewer > Add Selected Text to > Alias List
  • Project-level Delete (Project - Alias Lists - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Project-level Alias List.
  • Organization-level View (Organization - Alias Lists - View permission) – By default, only an Organization Administrator can view Alias List templates.
  • Organization-level Add/Edit (Organization - Alias Lists - Add/Edit permission) – By default, only an Organization Administrator can manage Alias List templates using the following:
    • New Template
    • Project-level Alias Lists > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Selected template New Alias List
    • Selected Alias List > Edit
    • Selected Alias List > Delete
    • Add Aliases to add Aliases within a List
    • Selected Alias(es) > Delete Selected
  • Organization-level Delete (Organization - Alias Lists - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Alias List template.

Analytic Settings – Controls access to the Analytic Settings at the Project level and Organization template level.

  • Project-level View (Project - Analytic Settings - View permission) – By default, only an Organization Administrator can view the Project Analytic Settings.
  • Project-level Add/Edit (Project - Analytic Settings - Add/Edit permission)– By default, only an Organization Administrator can manage the Project Analytic Settings using the following:
    • Load from Template
    • Analytic Setting selections
    • Save or Discard Changes
  • Organization-level View (Analytic Settings - View permission) – By default, only an Organization Administrator can view Analytic Settings templates.
  • Organization-level Add/Edit (Analytic Settings - Add/Edit permission) – By default, only an Organization Administrator can manage Analytic Setting templates using the following:
    • New Template
    • Project-level Analytic Settings > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Analytic Setting selections
    • Save or Discard Changes
  • Organization-level Delete (Analytic Settings - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Analytic Setting template.

Billing Reports – Controls access to the Billing Report information that populates the Billing Report chart on the Reports tab.

  • Project-level View (Project - Billing Reports - View permission) – By default, only an Organization Administrator can view the Project-level Billing Report information.
  • Project-level Add/Edit (Project - Billing Reports - Add/Edit permission) – By default, only an Organization Administrator can manage Project-level Billing Report information using the following:
    • Load from Template
    • File Type selections (and drag-and-drop controls) to exclude from billing in the Project
    • Save or Discard Changes
    • Add File Type Group and icons for a File Type Group or specific File Type
  • Organization-level View (Organization - Billing Reports - View permission) – By default, only an Organization Administrator can view Billing Report templates.
  • Organization-level Add/Edit (Organization - Billing Reports - Add/Edit permission) – By default, only an Organization Administrator can manage Billing Report templates using the following:
    • New Template
    • Project-level Billing Reports > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • File type selections (and drag-and-drop controls) to exclude from billing in the Project
    • Save or Discard Changes
    • Add File Type Group and icons for a File Type Group or specific File Type
  • Organization-level Delete (Organization - Billing Reports - Delete permission)– By default, only an Organization Administrator can use Delete for a selected Billing Report template.

Custom Fields  – Controls access to the Custom Field information.

  • Project-level View (Project - Custom Fields - View permission) – By default, only an Organization Administrator can view the Project-level Custom Field information.
  • Project-level Add/Edit (Project - Custom Fields - Add/Edit permission) – By default, only an Organization Administrator can use New Custom Field to add a Custom Field at Project-level.
  • Organization-level View (Organization -Custom Fields - View permission) – By default, only an Organization Administrator can view Custom Field templates.
  • Organization-level Add/Edit (Organization - Custom Fields - Add/Edit permission) – By default, only an Organization Administrator can manage Custom Field templates using the following:
    • New Template
    • Project-level Custom Fields > Save to Template or Selected Template > Save to Template
    • Selected template > Edit
    • Selected template > Set as Default
    • New Custom Field
  • Organization-level Delete (Organization - Custom Fields - Delete permission) – By default, only an Organization Administrator can delete Custom Field templates.

Domain Lists – Controls access to Domain Lists and Domains within each list.

  • Project-level View (Project -Domain Lists - View permission) – By default, all three roles have the ability to view Project-level Domain List information. This permission is also required to use the Advanced Search > Domain Lists section.
  • Project-level Add/Edit (Project - Domain Lists - Add/Edit permission) – By default, an Organization Administrator or Project Administrator can use the following:
    • Load from Template
    • New Domain List to add Project-level Domain Lists
    • Selected Domain List > Edit
    • Add Domains to add Domains within a List
    • Selected Domains > Delete Selected to delete selected Domains.
    • Document Viewer > Add Selected Text to > Domain List
    • Add to Domain List from the Sending Domains or Receiving Domains report > Details > selected Domains > Document drop-down menu>
  • Project-level Delete (Project - Domain Lists - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Project-level Domain List.
  • Organization-level View (Organization - Domain Lists - View permission) – By default, only an Organization Administrator can view Domain List templates.
  • Organization-level Add/Edit (Organization - Domain Lists - Add/Edit permission) – By default, only an Organization Administrator can use the following:
    • New Template
    • Project-level Domain Lists > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • New Domain List
    • Selected Domain List > Edit
    • Selected Domain List > Delete
    • Add Domains to add Domains within a List
    • Selected Domains ) > Delete Selected
  • Organization-level Delete (Organization - Domain Lists - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Domain List template.

Excluded Content – Controls access to the list of Excluded Content blocks affecting parsing.

  • Project-level View (Project - Excluded Content - View permission) – By default, only an Organization Administrator can view Project-level Excluded Content block information.
  • Project-level Add/Edit (Project - Excluded Content - Add/Edit permission) – By default, only an Organization Administrator can manage Excluded Content block in the Project using the following:
    • Load from Template
    • New Content Block
    • Selected Content Block > Edit
    • Selected Content Block > Duplicate
  • Project-level Delete (Project - Excluded Content - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Project-level Excluded Content block.
  • Organization-level View (Organization - Excluded Content - View permission) – By default, only an Organization Administrator can view Excluded Content templates.
  • Organization-level Add/Edit (Organization - Excluded Content - Add/Edit permission) – By default, only an Organization Administrator can manage Excluded Content templates using the following:
    • New Template
    • Project-level Excluded Content > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected Template > Edit
    • Selected Template > Set as Default
    • New Content Block
    • Selected Content Block > Edit
    • Selected Content Block > Duplicate
    • Selected Content Block > Delete
  • Organization-level Delete (Organization - Excluded Content - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Excluded Content template.

Export Fields – Controls access to the list of Export Field templates.

  • Project-level View (Project - Export Fields - View permission) – By default, only an Organization Administrator can view Project-level Export Field templates. This permission is also needed for operations that list Project-level Export Field templates (for example, New Export Stream, New Export Volume, selected Export Stream or Volume > Generate Load File).
  • Project-level Add/Edit(Project - Export Fields - Add/Edit permission) – By default, only an Organization Administrator can manage Project-level Export Field templates using the following:
    • New Template
    • Project-level Export Fields > Save to Template (to save to another Project-level template)
    • Load from Template
    • Selected Template > Edit
    • Selected Template > Set as Default
    • Export Field selections (and positioning)
    • Save or Discard Changes
    • New Transformed Field
    • Reset to Defaults
    • Download (.xml)
  • Project-level Delete (Project - Export Fields - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Project-level Export Field template.
  • Organization-level View (Organization - Export Fields - View permission) – By default, only an Organization Administrator can view Export Field templates. This permission is also needed for operations that list Organization-level Export Field templates (for example, New Export Stream, New Export Volume, selected Export Stream or Volume > Generate Load File).
  • Organization-level Add/Edit (Organization - Export Fields - Add/Edit permission) – By default, only an Organization Administrator can modify Export Field templates using the following:
    • New Template
    • Project-level Export Fields > Save to Template (to save to an Organization template) or Selected Organization template > Save to Template (to save to another Organization template)
    • Load from Template
    • Selected Template > Edit
    • Selected Template > Set as Default
    • Export Field selections (and positioning)
    • Save or Discard Changes
    • New Transformed Field
    • Reset to Defaults
    • Download (.xml)
  • Organization-level Delete (Organization - Export Fields - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Export Field template.

Export Settings – Controls access to the list of Export Settings.

  • Project-level View (Project - Export Settings - View permission) – By default, only an Organization Administrator can view the Project Export Settings. This permission is also needed if you select SQL DB as a format when creating an Export Stream.
  • Project-level Add/Edit (Project - Export Settings - Add/Edit permission) – By default, only an Organization Administrator can manage the Project Export Settings using the following:
    • Load from Template
    • Export Setting selections
    • Save or Discard Changes
  • Organization-level View (Organization - Export Settings - View permission) – By default, only an Organization Administrator can view Export Settings templates.
  • Organization-level Add/Edit (Organization - Export Settings - Add/Edit permission) – By default, only an Organization Administrator can manage Export Setting templates using the following:
    • New Template
    • Project-level Export Settings > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected Template > Edit
    • Selected Template > Set as Default
    • Export Setting selections
    • Save or Discard Changes
  • Organization-level Delete (Organization - Export Settings - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Export Settings template.

Index Settings – Controls access to the Index Settings affecting parsing at the Project level and Organization template level.

  • Project-level View (Project - Index Settings - View permission) – This permission controls viewing of the Project-level Index Settings. This permission is also required to use the OCR option from OCR Candidate Report Drill-through Search results for all Imports or a Data Set (and the OCR option also requires Imports - Add/Edit permissions). By default, only an Organization Administrator can view the Project Index Settings.
  • Project-level Add/Edit (Project - Index Settings - Add/Edit permission)– By default, only an Organization Administrator can manage the Project Index Settings using the following:
    • Load from Template
    • Index Setting selections
    • Save or Discard Changes
  • Organization-level View (Index Settings - View permission) – This permission controls viewing of the Organization-level Index Settings. By default, only an Organization Administrator can view Index Settings templates.
  • Organization-level Add/Edit (Index Settings - Add/Edit permission) – By default, only an Organization Administrator can manage Index Setting templates using the following:
    • New Template
    • Project-level Index Settings > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Index Setting selections
    • Save or Discard Changes
  • Organization-level Delete (Index Settings - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Index Setting template.

Load File Imports – Controls access to the Load File Import template information at the Project level and Organization level.

  • Project-level View (Project - Load File Import - View permission) – By default, only an Organization Administrator can view Project-level Load File Import templates.
  • Project-level Add/Edit(Project - Load File Import - Add/Edit permission) – By default, only an Organization Administrator can manage Project-level Export Field templates using the following:
    • New Template
    • Project-level Load File Import > Save to Template (to save to another Project-level template)
    • Load from Template
    • Selected Template > Edit
    • Selected Template > Set as Default
    • Save or Discard Changes
    • Discover Fields dialog (which also requires Connector Access permission for Connector list and Folder Navigation)
    • Add Field
    • Delete Selected (fields and mappings)
    • Transformer Icon Menu
    • Mapped Field Menu
    • Options (Preserve Families, Process Load File Images)
    • All other selections (including drag-and-drop)
  • Project-level Delete (Project - Load File Import - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Project-level Load File Import template.
  • Organization-level View (Organization - Load File Import - View permission) – By default, only an Organization Administrator can view Load File Import templates.
  • Organization-level Add/Edit (Organization - Load File Import - Add/Edit permission) – By default, only an Organization Administrator can modify Load File Import templates using the following:
    • New Template
    • Project-level Load File Import > Save to Template (to save to another Project-level template) or Selected Organization template > Save to Template (to save to another Organization template)
    • Load from Template
    • Selected Template > Edit
    • Selected Template > Set as Default
    • Save or Discard Changes
    • Discovery Fields dialog (which also requires Connector Access permission for Connector list and Folder Navigation)
    • Add Field
    • Delete Selected (fields and mappings)
    • Transformer Icon Menu
    • Mapped Field Menu
    • Options (Preserve Families, Process Load File Images
    • All other selections (including drag-and-drop)
  • Organization-level Delete (Organization - Load File Import - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Load File Import template.

Metadata Search Fields – Controls access to the list of metadata fields that are searched when the Include Metadata option is set for Freeform, Advanced, and Bulk Searches.

  • Project-level View (Project - Metadata Search Fields - View permission) – By default, all three default roles can view the Project Metadata Search Fields.
  • Project-level Add/Edit (Project - Metadata Search Fields - Add/Edit permission)– By default, only an Organization Administrator can manage the Project Metadata Search Fields using the following:
    • Load from Template
    • Metadata Search Field selections
    • Save or Discard Changes
  • Organization-level View (Metadata Search Fields - View permission) – By default, only an Organization Administrator can view Metadata Search Field templates.
  • Organization-level Add/Edit (Metadata Search Fields - Add/Edit permission) – By default, only an Organization Administrator can manage Metadata Search Field templates using the following:
    • New Template
    • Project-level Metadata Search Fields > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Metadata Search Field selections
    • Save or Discard Changes
  • Organization-level Delete (Metadata Search Fields - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Metadata Search Fields template.

Metadata View Fields – Controls access to the list of metadata fields that appear when you view Metadata for a document in the Document Viewer or request Current Project Metadata field information for Create Manifest.

  • Project-level View (Project - Metadata View Fields - View permission) – By default, all three default roles can view the Project Metadata View Fields. This permission should be enabled to use Create Manifest > fields options, including From Metadata View Fields Template, with the Current Project Settings selection. You should keep this permission enabled to ensure that you can view Metadata for a document in the Document Viewer and request Project-level Metadata field information for Create Manifest.
  • Project-level Add/Edit (Project - Metadata View Fields - Add/Edit permission)– By default, an Organization Administrator or Project Administrator can manage the Project Metadata View Fields using the following:
    • Load from Template
    • Metadata View Field selections
    • Save or Discard Changes
  • Organization-level View (Metadata View Fields - View permission) – By default, all three roles can view Metadata View Field templates. This also controls the Create Manifest > From Metadata View Fields Template option with Organization template selection.
  • Organization-level Add/Edit (Metadata View Fields - Add/Edit permission) – By default, an Organization Administrator can manage Metadata View Field templates using the following:
    • New Template
    • Project-level Metadata View Fields > Save to Template or Selected template > Save to Template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Metadata View Field selections
    • Save or Discard Changes
  • Organization-level Delete (Metadata View Fields - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Metadata View Fields template.

Password Cracking – Controls access to the Project-level Password Cracking information for the supported Password Cracking modes. Password Cracking is at the Project level only.

  • Project-level View (Project - Password Cracking - View permission) – By default, only an Organization Administrator can view the Password Cracking information.
  • Project-level Add/Edit (Project - Password Cracking - Add/Edit permission) – By default, only an Organization Administrator can manage Password Cracking information (making selections and using Save or Discard Changes).

Patterns – Controls access to the list of Patterns (regular expressions) that affect parsing.

  • Project-level View (Project - Patterns - View permission) – By default, all three roles can view Project-level Pattern information.
  • Project-level Add/Edit (Project - Patterns - Add/Edit permission) – By default, an Organization Administrator or Project Administrator can manage Pattern information using the following:
    • Load from Template
    • New Pattern
    • Selected Pattern > Edit
    • Selected Pattern > Copy
  • Project-level Delete (Project - Patterns - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Pattern.
  • Organization-level View(Organization - Patterns - View permission) – By default, only an Organization Administrator can view Pattern templates.
  • Organization-level Add/Edit (Organization - Patterns - Add/Edit permission) – By default, only an Organization Administrator can manage Pattern templates using the following:
    • New Template
    • Project-level Patterns > Save to Template or Selected template > Save to template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • New Pattern
    • Selected Pattern > Edit
    • Selected Pattern > Copy
    • Selected Pattern > Delete
  • Organization-level Delete (Organization - Patterns - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Patterns template.

Reports – In general, controls access to the Reports settings that apply to an All Imports, Data Set, or Project Data view (that is, which Reports appear for each view on the appropriate Reports tab). At Project level, this also controls access to the reports on all Reports tabs.

  • Project-level View (Project - Reports - View permission) – By default, all three default roles can view the Project-level Reports settings and the reports on all Reports tabs. If this permission is changed to disabled, the Reports tabs will not appear.
  • Project-level Add/Edit (Project - Reports - Add/Edit permission) – By default, only an Organization Administrator can manage Project-level Reports settings using the following:
    • Load from Template
    • Selected Reports settings
    • Save or Discard Changes
  • Organization-level View (Organization - Reports - View permission) – By default, only an Organization Administrator can view Report templates.
  • Organization-level Add/Edit (Organization - Reports - Add/Edit permission) – By default, only an Organization Administrator can manage Report templates using the following:
    • New Template
    • Project-level Reports > Save to Template or Selected template > Save to template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Selected Reports settings
    • Save or Discard Changes
  • Organization-level Delete (Organization - Reports - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Reports template.

Search Settings – Controls access to the Search Settings, which determine the search syntax in effect as well as which columns appear in a Search Term Report.

  • Project-level View (Project - Search Settings - View permission) – By default, all three default roles can view the Project-level Search Settings.
  • Project-level Add/Edit (Project - Search Settings - Add/Edit permission) – By default, only an Organization Administrator can manage the Project-level Search Settings using the following:
    • Load from Template
    • Selected Search settings (all configurable items)
    • Save or Discard Changes
  • Organization-level View (Organization - Search Settings - View permission)– By default, only an Organization Administrator can view Search Setting templates.
  • Organization-level Add/Edit (Organization - Search Settings - Add/Edit permission) – By default, only an Organization Administrator can manage Search Setting templates using the following:
    • New Template
    • Project-level Search Settings> Save to Template or Selected template > Save to template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Selected Search settings (all configurable items)
    • Save or Discard Changes
  • Organization-level Delete (Organization - Search Settings - Delete permission)– By default, only an Organization Administrator can use Delete for a selected Search Setting template.

Survivorship Model – Controls access to configured Survivorship Model queries, which are used for document deduplication at Export.

  • Project-level View (Project - Survivorship Model - View permission) – By default, only an Organization Administrator can view the Project-level Survivorship Model queries.
  • Project-level Add/Edit (Project - Survivorship Model - Add/Edit permission) – By default, only an Organization Administrator can manage the Project-level Search Settings using the following:
    • Load from Template
    • Survivorship Model query selections
    • Save or Discard Changes
  • Organization-level View (Organization - Survivorship Model - View permission)– By default, only an Organization Administrator can view Survivorship Model templates.
  • Organization-level Add/Edit (Organization - Survivorship Model - Add/Edit permission) – By default, only an Organization Administrator can manage Survivorship Model queries in templates using the following:
    • New Template
    • Project-level Survivorship Model > Save to Template or Selected template > Save to template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • Survivorship Model query selections
    • Save or Discard Changes
  • Organization-level Delete (Organization - Survivorship Model - Delete permission)– By default, only an Organization Administrator can use Delete for a selected Survivorship Model template.

Tags – Controls access to the Organization-level Tag template information. (Project-level access is governed by the Navigation Tree permissions for Tags.)

  • Organization-level View (Organization - Tags - View permission) – By default, only an Organization Administrator can view Tag templates.
  • Organization-level Add/Edit (Organization - Tags - Add/Edit permission) – By default, only an Organization Administrator can manage Tag templates using the following:
    • New Template
    • Project-level Tags > Save to Template or Selected template > Save to template
    • Load from Template
    • Selected template > Edit
    • Selected template > Set as Default
    • New Tag (Organization level)
    • Selected Organization Tag > Edit
    • Selected Organization Tag > Delete
  • Organization-level Delete (Organization - Tags - Delete permission) – By default, only an Organization Administrator can use Delete for a selected Tag template.

Save or Discard Changes Options

If you do not save your role changes before navigating away, you will be prompted to either save your changes and continue navigating away, discard your changes and continue navigating away, or cancel your changes and remain in the current location.

  • Save – Saves your changes to the role and its permissions. This button becomes active once you make changes.
  • Discard Changes – Discards your changes to the role and its permissions.