Review Assignments
Assigning a teammate to a review is how you say "this person is part of the working group on this study." Assignment is what drives the review's appearance in their dashboard, the notifications they receive, and the audit-log scope they can see.
When to assign
- When you start a new review and you already know who is on the team
- When you bring in an extra reviewer for adjudication
- When you hand off a review (e.g. the original Reviewer leaves the project)
- When you bring in an Auditor for a methodology check
You do not need to assign teammates just so they can read the review — Reviewers and Admins can already read every review in the workspace. Assignment is about declaring active participation.
How to assign
From the review settings panel
- Open the review (
/slror the matching hub for Rapid / Scoping / Umbrella / Evidence Map). - Open the Settings drawer (gear icon in the header).
- Scroll to Assignments.
- Click Add reviewer.
- Pick a teammate from the dropdown (the dropdown lists everyone in your Team Hub who is not already assigned).
- Optional: pick a role-on-this-review (lead reviewer, second reviewer, adjudicator, observer).
- Click Assign.
The assigned teammate immediately:
- Sees the review highlighted on their dashboard.
- Receives an in-app notification ("You were assigned to <review title>").
- Sees the review in their personal My Reviews table.
From Team Hub
Each member row in Team Hub shows their currently assigned reviews. You can also assign from there: click a member, click Assign to review, pick a review.
How to unassign
In the same Assignments panel, click the trash icon next to the teammate's name. They will lose the dashboard highlight and stop receiving notifications for the review. Their prior contributions (screening decisions, extracted fields, comments) are preserved.
What assignment changes
- Visibility on dashboard. Assigned reviews surface to the top of the assignee's dashboard.
- Notifications. Assignees receive notifications for that review (new comments, phase locks, bundle exports, mentions).
- Audit-log scope. Reviewers and Auditors can see the audit trail for reviews they are assigned to. Owners and Admins see all audit trails regardless of assignment.
- Mention autocomplete. Other teammates can
@-mention assignees in review comments.
What assignment does not change
- It does not change the underlying role permissions. A Reviewer who is not assigned can still read the review; assigning only adds notifications and dashboard prominence. An Auditor who is not assigned cannot read the review at all.
- It does not change ownership. The review's owner — the person whose actions appear as the original author — does not change when you assign.
Common patterns
| Scenario | Recommended assignment |
|---|---|
| Two-reviewer screening | Assign reviewer 1 + reviewer 2 |
| Add an adjudicator after disagreement | Assign reviewer 3 (adjudicator role) |
| External methodology review before submission | Assign as Auditor, not Reviewer |
| Hand-off when a teammate leaves | Assign the new teammate, then unassign the leaver |
| Solo review | Assign yourself (so notifications still fire) |
Best practices
- Assign early. Assign as soon as you know who is on the working group — it's the simplest way to drive the right notifications without having to remember to email anybody.
- Unassign when done. Once a phase is closed and a teammate is no longer involved, unassign them so notifications stop and the review drops off their dashboard.
- Don't assign as a substitute for inviting. If somebody is not yet in your workspace, invite them in Team Hub first; the assignment picker will then list them.