

This page contains information on the security permissions required for creating and interacting with the Review Center application.
As of February 2025, the new Feature Permissions redefines Relativity's security management by shifting the focus from Object Types and Tab Visibility to feature-based permissions. This new method is simply another option; any feature-specific permissions information already in this topic is still applicable. This new interface enables administrators to manage permissions at the feature level, offering a more intuitive experience. By viewing granular permissions associated with each feature, administrators can ensure comprehensive control, ultimately reducing complexity and minimizing errors. For details see
To create a Review Center template or queue, you need the following permissions:
Object Security | Tab Visibility |
---|---|
|
|
To edit an existing Review Center queue and use dashboard controls such as Prepare or Start, you need the following permissions:
Object Security | Tab Visibility |
---|---|
|
|
Note: The Workspace - Edit Security permission is only required to edit the assigned reviewer group.
To delete a Review Center template or queue, you need the following permissions:
Object Security | Tab Visibility | Mass Operation |
---|---|---|
|
|
|
To view the Review Center dashboard, you need the following permissions:
Object Security | Tab Visibility |
---|---|
|
|
If you want a user group to only see specific queues on the dashboard, you can restrict a queue using item-level security on the Review Library tab. For more information, see Levels of Security in Relativity.
To create a saved model from a Review Center queue, you need the following permissions:
Object Security | Tab Visibility |
---|---|
|
|
To copy a saved model to another workspace, you must have access to the destination workspace. You also need the following permissions in the origin workspace:
Object Security | Tab Visibility |
---|---|
|
|
To delete a saved model, you need the following permissions:
Object Security | Tab Visibility |
---|---|
|
|
To track reviewer coding decisions using the Documents tab or the Field Tree, you need the following permissions:
Object Security | Tab Visibility |
Browsers |
---|---|---|
|
|
|
Users with access to the Review Center dashboard can also track reviewer decisions using the Reviewed Documents table. For more information, see Tracking reviewer decisions.
A reviewer group accessing a Review Center queue and coding documents must have the following permissions:
Object Security | Tab Visibility |
---|---|
|
|
Make sure the reviewer groups have permissions to the documents they need to review. Reviewers will only see documents they have access to. If any documents in the queue are in a secured documents folder, and a reviewer does not have permissions for it, those documents will not be checked out to the reviewer.
If a reviewer sees a message that there are no more documents to review in a queue, but there are uncoded documents left, check the document permissions.
For more information on document security, see Securing a folder for selected groups.
For more information on assigning reviewer groups to a queue, see:
On this page
Why was this not helpful?
Check one that applies.
Thank you for your feedback.
Want to tell us more?
Great!