There is going to be a major update to the fundamental service for the Reviews tool. This update is being implemented to lay the foundation for more powerful feature development in the future.
The new service will be gradually rolled out to customers between October 9 and October 31, 2025.
After the rollout, there will be a 6-month transition period until April 30, 2026.
After April 30, 2026, reviews created before October 31, 2025 (old reviews) will experience a downgrade. No reviewers will be able to claim or submit review tasks for old reviews, and these reviews will remain at their current steps and status.
You should close out all old reviews created before October 31, 2025 by the April 30, 2026 transition deadline.
If old reviews remain open beyond the April 30, 2026 transition deadline, you'll need to create a new review using the new workflow service and add the same file versions as the old review.
No. We do not anticipate any service interruptions. The transition will be managed in the background.
All existing review features and functions will remain unchanged. This update is being implemented to lay the foundation for more powerful feature development in the future.
No. This upgrade is a platform-wide improvement and will replace the legacy workflow service after the transition period.
Find answers to general frequently asked questions about working with reviews.
Yes.
Markups will also copy to the target folder if Include all published markups on approved files is selected in the approval workflow. However, this can be overridden if Allow approvers to change whether or not markups are included is also selected and the approver chooses not to include markups.
Currently, members with View permission or above can add markups to files in a review. These markups are private by default which means that only the creator can view them. Members with Create permissions or higher can publish their private markups to make them available to all project members to view. See Work With Markups help topic for more information.
Yes, anyone who is part of a group review can see comments added by the other reviewers.
You can check the review status of a file by viewing the Review status attribute in the Document Management. This will show the review status of the current version of the file.
You can also see the review status of a previous version by opening the version history panel of that file.
If the Review status attribute is not showing, see Document Attributes for more information.
There are two default review statuses for the outcome of a review, and an in review status.
Approved: File is approved after final review.
Rejected: File is rejected after final review.
These usually display as Approved or Rejected in the Review status attribute, however you may see other values such as Approved w/ comments. This is because project administrators can edit approval workflows to change the Approved and Rejected label and also create values.
See the Document review status section of Create and Edit Approval Workflows for more information.
In Review
The In review status shows when a file is still in the review process, including when a file is submitted for multiple reviews and is awaiting approval or rejection.
Hover over the In review status to display the relevant review links and the review status.
Project administrators can click the review links to open the reviews in the Docs Reviews tool. Project members can only access the links they have permission for.