Use case: Clients keep replying on requests that are already finished. That reopens conversations and leads to unplanned revisions. Locking comments keeps finished work closed and nudges clients to open a new request instead.
What happens when comments are locked
When the setting is on, these rules apply to every request in your Completed or Closed status:
Clients and team members can no longer post comments. Instead of the comment box, they see Comments are closed for completed requests.
Everyone can still open the request and read the full conversation, files and activity.
Admins and portal admins can still comment, for example to add a last note.
Comments sent through Zapier on a locked request are refused too.
How to turn on comment locking
Go to Settings > Modules and extensions.
Click Requests.
Turn on Disable comments on completed requests.
Click Save changes.
The lock applies right away to all requests already in a Completed or Closed status, and to every request that moves there later.
How it fits your workflow
Move a request to Completed when the work is delivered, or to Closed when you archive it.
The client can review the final files, but cannot reply on the request.
If more work is needed, the client creates a new request. If you want to reopen the conversation instead, change the request back to another status: comments open again.
When to use it
You want to avoid scope creep after delivery.
Your team works on fixed-scope requests.
You prefer new requests over reopening old ones, so your reports stay clean.
Related articles