Create a Project

Home page > selected Organization > New Project

Requires Projects - Add/Edit Permissions

Only users with the appropriate Projects - Add/Edit permissions (for example, as an Organization Administrator) will be able to use the New Project option.

Creating a Project includes the following:

  • Information
  • Membership
  • Settings

Note: Project creation requires additional permissions, as noted in View and Manage Role-Based Permissions.

Specify Basic Information

First, you define the essential Project information, which involves assigning a name and an optional description for the Project:

! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”

Establish Membership

Users in a role with Projects - Add/Edit permissions can assign the users and groups that will be members of a new Project. To open a Project and perform Project operations, Users and Groups (regular Organization Users and Groups, or System Users and Groups) must have Project membership and an assigned role, which represents a set of permitted actions that control access to Project operations and elements.

During Project Creation, the current User (for example, an Organization Admin) is the User initially listed in the team member list. Click Add / Remove Members to see the list of all Users and Groups defined with a role in the Organization. It is possible that some Users only have Group membership but have no individual role. These Users have permissions based on their Group role.

Each member added is shown with the following information (if configured):

  • Type — This can be User, Group, System User, or System Group. Icons help you distinguish between the different types. Organization Users and Organization Groups have explicit membership within a given Organization. System Users and System Groups have explicit membership within one or more Organizations, and are configured by a System User in a role with the appropriate System-level permissions.
  • Name — This is the assigned name of the System Group, Group, System User, or User. The list is sorted by name in alphabetical order by default.
  • 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.

Select Settings from Templates

Users in a role with Projects - Add/Edit permissions can select one or more templates to use in a new Project. Available templates will be either Organization templates or System templates, if you have the appropriate permissions. To see a list of available System templates, you must have 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.)

For each template type, the drop-down displays the available Organization templates and System templates. The available Organization templates are listed alphabetically, and the available System templates are listed alphabetically.

You can select one or more of the following eDiscovery templates using the drop-down list of available templates:

Note: As of 5.2.5.x, all new Projects will be created using Parsing Library Version V2, and you will only see V2-based Organization and System-level templates in the list for Index Settings and Billing Reports when you create a Project. Any V1 versions of these template types in existing Organizations will not be listed. All new Index Setting or Billing Reports templates in new or existing Organizations will be V2-based. You can only select what is now a V2 Organization default template, or any V2-based template that you create, for Index Settings or Billing Reports. In existing Organizations, for clarity, you will see the V2 Index Settings and Billing Reports default templates identified as V2 in the name. (In a new Organization, you will not see V2 in the name, since everything will be V2.) Note that when you are managing the list of available Index Settings or Billing Reports templates from the Organization Settings of an existing Organization, a V1 template cannot be set as the default template.

  • Alias Lists — For the lists of Aliases that you want to use in your Project. You must define Alias Lists for the template, since the initial template does not have any Alias Lists.
  • Billing Reports — For establishing File Type Exclusion Groups with the File Types you want to exclude from the billing reports for the Imports, Data Set, and Project Data views.
  • Custom Fields — For establishing custom fields that you want to display and use (for example, for a DAT Load File).
  • Domain Lists — For the list of email domains you want to recognize.
  • Excluded Content — For content that you want removed from the content index so that the content is not responsive to searches.
  • Export Fields — For the list of Export metadata fields you want to apply to data that you export from the Project.
  • Export Settings — For the list of Export Settings you want to apply to data that you export from the Project.
  • Index Settings — For parsing-related Index settings such as OCR processing, Language Detection, and Numeric Settings.
  • Load File Import — For establishing the settings and fields needed for a Load File Import (for example, a DAT Load File).
  • Metadata Search Fields — For the list of Metadata fields you want to be searched automatically as part of all term search queries (that is, as long as the Include Metadata option remains enabled, a keyword-based search is expanded to include the specified list of metadata fields). The system supplies a default subset of metadata fields, but you can choose which fields you want to include.
  • Metadata View Fields — For the list of metadata fields you want to view in the Project (for example, in the Document Viewer Metadata pane).
  • Patterns — For the list of patterns (regular expressions) you want to have applied during parsing.
  • Reports — For selecting the reports you want to have generated for Imports, a Data Set, and Project Data.
  • Search Settings — For the Search Syntax and Search Term Report options you want to use in the Project.
  • Survivorship Model — For the list of queries in a given order you want to employ as an email survivorship model used for document deduplication at Export (email or non-email deduplication). You must define queries for the model, since the default template does not include an queries.
  • Tags — For the set of Tags you want to make available for document tagging.

Default templates with values are available for all but the Excluded Content template and Survivorship Model, for which the templates must be built with a list of entries. This can be done by a user with the appropriate permissions.

Create the Project or Cancel the Operation

  • Create Project — Click the Create Project button when you are ready to start the Project creation process.
  • Cancel — Click the Cancel button if you want to cancel the operation instead.