Feature permissions

You can manage permissions more efficiently using the Features tab. Instead of adjusting individual settings across Object Security, Tab Visibility, and Other Settings, you can enable permissions by feature.

Features represent key system capabilities such as Preservation, Production, Imaging, and Configure Doc Review. Each feature groups together the necessary permissions from the three tabs. When you enable a feature, all related permissions are automatically applied.

To achieve this, all permission changes must now be made through Feature Permissions instead of the older granular settings in Object Security, Tab Visibility, and Other Settings/Admin Operations. The modernization of Feature Permissions simplifies permissions management and creates consistency across workflows. This update ensures that feature behavior is standardized and easier for end users to understand and use.

Feature Permissions are rolling out through a phased modernization. Migration tooling supports controlled adoption with full audit visibility.

During migration, each feature exists in one of two states:

• Modernized— Feature Permissions controls all permissions for the feature. Granular permissions are locked, and the feature toggle governs them. You cannot directly edit permissions in Object Security, Tab Visibility, or Other Settings.

• Non-modernized— Legacy behavior remains. You can continue to modify granular permissions in Object Security, Tab Visibility, and Other Settings, and those changes appear on the Features tab.

When you enable or disable a feature, Feature Permissions applies or revokes the entire set of dependent permissions in a single action. This simplifies configuration and reduces the risk of misaligned settings.

Currently modernized features

Below you will find the current Feature Permissions that are modernized. When a feature is modernized, its associated Object Security, Tab Visibility, and Admin Operations permissions are locked and can only be modified through the Feature Permission toggle. For more information, see Modernized feature permissions behavior.

= Shared granular permission

Modernized Feature Permission	Level	Object Security	Tab Visibility	Admin Operations / Other
aiR for Review	Instance	None	aiR for Review Jobs	View Admin Repository
Archive and Restore (ARM)	Instance	None	ARM ARM Jobs Configuration	None
Cost Explorer	Instance	None	Cost Explorer Management Console	View Admin Repository View Cost Explorer
Data Transfer	Instance	None	Staging Explorer	View Admin Repository Access RelativityOne Staging Explorer Send Email Notification
Migrate	Instance	Migrate Migration – View, Edit, Add, Delete, Secure Migrate Restore Job – View, Edit, Add, Delete, Secure Migrate Source Instance – View, Edit, Add, Delete, Secure	Migrate	View Admin Repository Access Migrate
Security Center	Instance	None	Security Center	None
Staging Reports	Instance	None	Staging Reports Management Console	View Admin Repository View Instance-wide Staging Reports View Client Domain Staging Reports
Usage Reports	Instance	None	Management Console	View Admin Repository View Instance-wide Usage Reports View Client Domain Usage Reports

This table is updated as additional features move to the modernized state. Check back regularly or review the release notes for the latest changes.

Considerations

Keep these factors in mind when setting Feature permissions:

• For modernized features, the Feature Permission becomes its own unique entity and is no longer simply a stateless collection of the granular permissions associated with that feature. Once modernized, the Feature Permission can only be granted or revoked by modifying the value of the Feature Permission directly and will never be changed based on modification of the granular permissions.
• For non-modernized features, any change modifications should happen in the Feature tab, but are still available for granular permission settings on the Object Security, Tab Visibility, and Other Settings tabs.

Using the Features tab

The Features tab lists the features available for the selected group. Each feature shows its current state for that group.

To apply a preset to a feature:

1. Find the feature in the list.
2. Click See details. A panel opens on the right.
3. Select a preset.
4. Click Review and Save.
5. Review the changes, then click Save.

Some features control only a few permissions and do not offer presets. Select the checkbox next to the feature to grant access. Clear the checkbox to remove access.

You can also do the following from the Features tab:

• Use the Search bar to find a feature in the list.

• In a feature's See details panel, click Granular permissions mapping. A read-only reference shows the granular permissions behind each preset.

Feature actions

Example: the Audit feature includes two actions: View Audit and View Audit Migration Reports.

Key details about actions:

• Each action maps to one or more granular permissions, managed by Relativity.
• Actions are additive. Selecting an action grants access to its task. It does not remove access granted by other actions or features.
• Each action belongs to one feature. The same action does not appear in another feature.

Presets

A preset is an optional group of related actions. It gives you a starting point for a feature. When you select a preset, Relativity selects the actions defined for that preset. You can then select or clear individual actions before you save.

Most features with presets offer Viewer and Administrator. Staging Reports and Usage Reports offer Client Domain and Instance-wide. Some features have no preset. For those, select all actions, or select individual actions.

Feature states

A feature’s state for a selected group depends on how many actions are enabled:

• Disabled: None of the feature’s actions are selected.
• Partially Enabled: Some, but not all, actions are selected.
• Enabled: All of the feature’s actions are selected.

A feature with no actions has only two states: Disabled or Enabled.

Viewing the legacy permissions mapping

Some features map their actions to granular permissions. To see this mapping, open the feature's See details panel. Click Granular permissions mapping. The mapping is a read-only reference. It shows the granular permissions behind each preset or action.

The mapping uses these icons:

• Enabled permission — the group has this granular permission.
• Disabled permission — the group does not have this granular permission.
• Permission used by multiple Features — more than one feature includes this permission.
• Permission not found by name — a tab permission was renamed. Relativity cannot identify it by the new name, so Relativity does not modify this permission.

Configuring feature actions for a group

1. Open permissions for the group. For steps, see Setting instance permissions.
2. In the Features list, find the feature.
3. Click see details.
4. Select a preset, or select individual actions
5. Click Review and Save.
6. Review the listed changes, then click Save.

Modernized feature permissions behavior

As features move to the modernized state, the way you manage permissions for those features changes. The Feature Permission becomes the only way to manage access to that feature, and restrictions are placed on the modification of any legacy granular permissions associated with that feature.

Feature Permissions are accessed via the Features tab on the Permissions UI.

Legacy granular permission pages, such as Object Security, have a warning banner directing all permission modifications to be done via Feature Permissions.

Granular permissions behavior

The behavior of a legacy granular permission depends on how it relates to Feature permissions.

Granular relation to features	Status of features	Behavior
Non-modernized: Not associated with any modernized Feature Permission	Not applicable	Able to be modified
Fully modernized: Associated with one or more modernized Feature permissions and no other Feature Permissions	Not applicable	Unable to be modified
Partially modernized: Associated with one or more modernized Feature Permissions and one or more non-modernized Feature Permissions	1+ associated modernized Feature Permissions is enabled.	Unable to be modified
	All associated modernized Feature Permissions are disabled.	Able to be modified.

Granular permissions that are associated with a fully modernized feature permission are in a read-only state and have a tool-tip noting which feature permission(s) to use instead.

A granular permission that is associated with both modernized and non-modernized feature permissions appears in a read-only state when one or more of those features is enabled. In this state, a message indicates which feature permission(s) require that granular permission.

Shared granular permissions

If a granular permission is shared across multiple Feature Permissions, regardless of whether they are modernized, that granular permission will not always reflect the state of the feature. Specifically, if the feature is disabled yet a different associated Feature Permission is enabled, the granular permission will remain enabled.

All granular permissions associated with a feature are shown in the Feature Permission Details flyout / side panel. Shared granular permissions are denoted on the Feature Permission UI via the blue link icon.

Aligning permissions with modernized features (migration tooling)

Once a Feature Permission is modernized, it is highly encouraged to update the permissions on each of your groups to align with the Feature Permission so that they are prepared for the future state of permissions. To help support changes to reach this alignment, migration tooling exists in the Permissions UI.

Identifying out-of-alignment permissions

If the group you are editing permissions for within the Permissions UI has a permissions configuration that does not align with one or more modernized Feature Permissions, a blue banner appears with a light bulb icon: "Permissions to align". Additionally, a blue light bulb icon appears in line with the modernized Feature Permission that is out of alignment.

A group is out of alignment with a Feature Permission if it is in a partially enabled state, meaning that it has some subset of the granular permissions granted but not all of them, excluding permissions used by multiple features. In order to reach alignment, the group must be granted all of the granular permissions associated with that Feature Permission or none of them (excluding permissions used by multiple features).

Aligning a group's permissions

To align the group's permissions with a modernized Feature Permission:

1. Click to enable or disable the Feature Permission(s) designated as out of alignment with the blue lightbulb .

2. Alternatively, click into "See details" for that Feature Permission to see which granular permissions are out of alignment and the changes needed to reach alignment.
   

3. Select either the Enable or Disable button at the top of the flyout / side panel in the designated section "Permissions to align". Select Enable to grant the group all the granular permissions associated with that Feature Permission or Disable to remove all granular permissions associated with that Feature Permission.

4. To complete the change in permissions, click Review and Save and then click Save.

   Once the group has their permissions updated to align with the Feature Permission, the banner at the top as well as the blue lightbulb in line with that feature will go away.

   A group is out of alignment with a modernized Feature Permission if it has some subset of the permissions granted, excluding permissions used by multiple features. This should be addressed by enabling or disabling the feature and thus granting or removing all granular permissions.
   

Scenarios

• Changing a specific permission under the Object Security, Tab Visibility, and Other Settings tab associated with an enabled feature will result in the feature being disabled.

• Disabling a feature on the Features tab disables its associated granular permissions for that feature. However, if a granular feature is part of another enabled feature, then it will remain enabled (blue check mark) on the disabled feature’s See Details panel.

• Disabling a feature revokes access to all granular permissions associated with the feature that are not currently granted as part of a different enabled feature. Therefore, enabling and then disabling a feature will not necessarily return the group to the state it was previously in. Be sure to examine the Review Permissions Changes dialog to confirm all permissions changes are as expected.

Frequently asked questions

Instance-level permissions

Set administrator permissions at the feature level. The tables below show the specific permission settings included in each feature at the Instance-level.

For more details on setting feature permissions, refer to Setting instance permissions.

None stands for Not Applicable

Workspace-level permissions

Set administrator or user permissions at the feature level. The tables below show the specific permission settings included in each feature at the workspace-level.

For more details on setting feature permissions, refer to Setting workspace permissions.

None stands for Not Applicable