Last date modified: 2026-Nov-09
Permissions scenarios
In this topic, you can explore various scenarios that involve managing permissions.
See the following related pages:
- Feature permissions
- Setting workspace permissions
- Setting instance permissions
- Setting permissions on objects
- Preview security
- Relativity aiR Security Center
- Security Alerts
Hierarchical structure
System administrators have the highest level of managerial rights followed by workspace administrators. Standard users have limited administrative capabilities and primarily operate within the permissions assigned to them.
- 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 groups. They can control the overall system behavior, user management, security settings, and other administrative tasks.
- Workspace administrators—have administrative control over specific workspaces. They can manage settings, configurations, object permissions, and layouts within their assigned workspaces, and they can be granted permission to change other groups' security in those workspaces. Creating users and groups and managing group membership happen at the instance level.
- Standard users—do not have administrative privileges and cannot modify system or workspace settings. They are only allowed to access and interact with objects based on the permissions assigned to their user accounts or the groups they belong to.
Client domains
In the hierarchical structure of permissions, client domain permissions are positioned below system administrators but above workspace administrators and standard users. This arrangement facilitates the delegation of administrative tasks to a specific user group known as client domain admins. Unlike the System Administrator group, client domain admins have limited visibility and control confined to their designated client domain. This isolation provides more precise administrative control over a defined segment of the environment, preventing unauthorized access or changes to the overarching Relativity aiR instance.
Client domain admins possess the flexibility to adjust permission settings for various objects within their domain, customizing them to align with their specific preferences. However, these permissions are restricted solely to their allocated domain and do not extend beyond it. This boundary is designed to prevent them from accessing or modifying permissions outside their designated client domain. By implementing client domain permissions, system administrators can proficiently oversee their domain while upholding the integrity and security of the broader Relativity environment.
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.
User groups
User groups serve as a means to organize and manage users who need the same access or permissions. You can assign user groups at either the workspace level or the system level, based on the intended extent of access and management. When assigned at the workspace level, user groups pertain to a particular workspace, governing the permissions and access rights within that workspace. On the other hand, at the system level, user groups have wider-ranging implications and can influence permissions and access across multiple workspaces within the Relativity environment.
Feature permissions and granular permissions
Grant access with feature permissions on the Features tab whenever you can, instead of setting individual permissions on the Object Security, Tab Visibility, and Other Settings or Admin Operations tabs. A feature groups the permissions a capability needs. Each feature is made up of actions, which are the individual tasks users can perform, such as viewing, managing, deleting, or securing items. A preset is a starting set of actions that you can add to or remove from before you save.
How you manage the underlying granular permissions depends on the feature:
- Modernized features: the granular permissions are locked, and you can change access only through the feature. All modernized features are instance-level features.
- Non-modernized features: you can still change the granular permissions directly, and the Features tab reflects those changes. The granular permissions behind workspace-level features are not locked.
When Relativity updates how a feature's permissions are grouped into actions, the permissions your groups already have don't change. The Features tab may show the feature differently afterward, for example as partially enabled. Click See details on the feature to review which actions the group has.
The scenarios and frequently asked questions in this topic name the feature or action to grant first, where one exists. For more information, see Feature permissions.
Template groups
Workspace templates come with their own groups, called template groups. Each template group has a predefined set of permissions for a common type of user in that workspace. When you add a new group to a workspace, you can copy the permissions of a template group to it, and then preview the access it grants. For steps, see Groups.
The permissions listed for each template group are the defaults after the template is installed. You can change them at any time, so the template groups in your workspaces may differ.
Review Template groups
The Review Template includes four groups:
- Level 1 Reviewer: for reviewers who only need to check batches in and out and review documents.
- Level 2 Reviewer: for reviewers who, in addition to Level 1 responsibilities, need to process data, set up searches, or run productions.
- Attorney: for users who only need to search and review documents and run search terms reports.
- Administrator: for users who need access to all workspace functionality. This group is assigned as the workspace admin group.
To see the permissions a template group currently grants, open the group's permissions in the workspace. See Setting workspace permissions.
Other workspace templates
Other templates, such as the Investigations, Early Case Assessment (ECA), Hold and Collect, and FOIA templates, include their own template groups. For the list of templates, see
Object-level permissions
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.
The Manage Object Types permission grants group members the ability to:
- Create a new tab for a new object type when adding the new object type.
- Automatically gain view, add, edit, delete, and secure permissions for all newly created object types.
- Automatically gain tab visibility for newly created tabs.
Item-level permissions
Item-level permissions control access to a single item in a workspace, such as one document, view, or OCR set, instead of relying on the permissions set for its object type across the workspace. With item-level permissions, you can:
- restrict an item to specific groups. When you turn on Override Inherited Security for an item, only the groups on that item's security list can access it.
- define what each of those groups can do with the item, such as view, edit, delete, or edit its security. Item-level permissions are most often used to give a group less access to an item than it has across the workspace, but you can also give a group more access.
When you turn on Override Inherited Security for an item, the item starts with the same permissions as the workspace-level settings for its object type. You can then change the permissions for that item. From then on, the system uses the item-level permissions for that item and ignores the workspace-level settings. For example, if a group has None for the OCR Set object at the workspace level, but you add that group to the item-level security of a specific OCR set, users in that group can view that OCR set.
To remove a group's access to an item completely, remove the group from the item using the Add/Remove Groups button. You can't set a group's access to None on an item. If a group is added to an item, the lowest level of access it can have is View.
To change item-level permission settings, you must navigate to the specific document or object and make changes individually.
Document unitization
Document unitization lets users split imaged documents into child documents. To give a group access, enable the Unitize Documents action of the Document Actions feature on the Features tab. Document unitization isn't supported when item-level security is enabled on the document.
Relativity has a current version and a legacy version of document unitization. For permissions, setup, and considerations for both versions, see
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 the instance-level Data Transfer feature, which grants access to 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:
- Permission to use Staging Explorer, granted instance-wide by the Data Transfer feature.
- Permission to access Workspace 1.
- Permission to access Workspace 2.
| User Groups |
Permissions |
Access to Workspaces |
|---|---|---|
|
Group A (Client Domain Admin) |
Use Staging Explorer (Data Transfer feature, instance-wide) |
Workspace 1 |
| Group B (Review) |
Access to Workspace 2 |
Workspace 2 |
| User in both Group A & B |
Use Staging Explorer (Data Transfer feature, instance-wide) Access Workspace 1 & 2 |
Workspace 1 & 2 |
In this case, because permissions are additive, 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
Frequently asked questions
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| View Relativity Email Threads |
|
N/A | Email Threading | Email Thread Visualization |
This tool is available for all email threading jobs that run as full builds. After the job finishes, you can view the visualization by opening any document in the document viewer.
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:
- Email Action
- Email Thread Group
- Email Author Date ID
- Inclusive Email
- Email Thread Hash
- Email Duplicate Spare
- 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.
To create fields, the Relativity Application view permission must be set to View.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Create Fields |
|
N/A | Workspace - Admin Fields | N/A |
To add or modify layouts, the group needs the following permissions.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Add or Modify Layouts | View, Edit, Create | View, Edit | Workspace Details, Layouts, Layout Sets, Layout Templates, Dynamic Objects | N/A |
To create automated workflows, a group needs the Manage Automated Workflows action of the Automated Workflows feature on the Features tab. The Distribute Automated Workflows action also allows creating workflows, and lets users copy workflows to other workspaces. To add actions such as dtSearch or search terms reports to a workflow, users also need permissions for those objects. Ask your workspace administrator to confirm your group's access.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Create an Automated Workflow | Automated Workflows - View, Add, Edit | N/A |
|
N/A |
Other users need the View Automated Workflows action of the Automated Workflows feature to see workflows in the workspace. If the workflow has item-level security, their group must also be on the workflow's security list.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Share an Automated Workflow | Automated Workflows - View | Review item-level permission settings to confirm the affected users or groups have the necessary permissions to access and work with the automated workflow. |
|
N/A |
Use item-level security on the workflow. Open the workflow's details page, click Edit Permissions, turn on Override Inherited Security, and add only the groups that should use the workflow. To change a workflow's security, you need the Secure Automated Workflows action of the Automated Workflows feature. For more information, see Item-level permissions.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Restrict access to an automated workflow | Automated Workflows - View, Secure | Override Inherited Security on the workflow, with only the allowed groups added |
|
N/A |
To edit automated workflows, a group needs the Manage Automated Workflows action of the Automated Workflows feature. If the workflow has item-level security, the group also needs Edit permission on that workflow. Check with your workspace administrator to confirm your group's access.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Modify an Automated Workflow | Automated Workflows - View, Edit | Edit for the Automated workflow. |
|
N/A |
The user who originally created the automated workflow may need to modify it to use fields that are accessible to all users who need to use it. It’s also necessary to check with your workspace administrator to confirm you have the appropriate permissions.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Use an Automated Workflow with access to certain fields. | View, Edit, Create, and Delete on documents or custom objects the automated workflow interacts with. | Confirm you have the appropriate item security permissions to access the items relevant to the automated workflow. If the automated workflow requires modifying or updating specific fields for items, you should have the necessary item security permissions to perform those actions. | Security | To configure object and item security permissions, you need membership in an administrative group or the necessary permissions to modify security settings. |
Set up workspace permissions that restrict access to specific documents, folders, or other items within the workspace. You can also add users to different groups, such as reviewer, editor, or admin groups, depending on their level of access and responsibility.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Limit multiple users’ access to documents and data relevant to their work |
|
|
Workspace Details > Manage Workspace Permissions, and Edit Permissions on each secured item | N/A |
Create a new group specifically for the vendor and set up workspace permissions that limit their access to only the documents and data that are relevant to their work. You can also use redaction or other security features to protect confidential information from unauthorized access.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Limit third-party vendor workspace access to documents and data relevant to their work | View document, field, layout, and saved search. | Configure the security group’s item security permissions to restrict access to confidential or privileged data. |
|
N/A |
Use the built-in security features of Relativity’s workspace permissions to add users to groups and set permissions based on each user’s job responsibilities and level of access. You can also create groups for specific projects or workflows, so that each user's access is limited to the data their work requires.
| Action | Object Security Permission | Item Security | Tab | Admin Operation |
|---|---|---|---|---|
| Grant a new team member access to a workspace with the appropriate permissions. |
|
N/A |
|
|
Manage access through groups and features instead of individual users. For workspace groups, copy permissions from an existing group or a template group when you add a group to the workspace. See Template groups. You can also use reporting and auditing tools to track user activity and support compliance with your organization's data security policies.
Yes. The granular permissions behind workspace-level features are not locked, so you can change them on the Object Security, Tab Visibility, and Other Settings tabs. The Features tab reflects those changes. We recommend granting access through features on the Features tab instead, so that groups get every permission a task needs. At the instance level, the granular permissions behind modernized features are locked. For more information, see Feature permissions and granular permissions.
When Relativity breaks a feature into actions or changes which permissions an action includes, the permissions your group already has don't change. Only the way the Features tab groups them changes. As a result, a feature that was enabled may now show as partially enabled, or a preset may no longer match the group's actions. Click See details on the feature to review the group's actions, and then select or clear actions to match the access the group needs. For more information, see Feature actions.