Configure your approval task for better feedback
When you configure an Approval task, you can set comment behavior for each approval option individually. Approvers then receive a comment prompt only on the approval paths that need one.
Users can add comments from their open tasks in the portal. If you enable approval by email, they can also add comments on the browser confirmation page after they select an option from the email notification.
Configuring comments for approval options
Starting with version 8.11.0, you configure comment settings individually for each approval option rather than globally for the entire task. Each option can show the comments box as optional or required, or hide it.
To configure comments for an approval option:
- Select Configure Task from the task menu of the Approval task.
- Navigate to the Approval Options section.
- For each approval option, you’ll see an Allow users to enter comments setting.
For each approval option, you can choose:
- No — No comments box will appear when this option is selected
- Optional — Comments box that’s optional when completing the task with this option
- Required — Comments box that must contain text to complete the task with this option
Use cases for conditional comments
This per-option configuration supports several scenarios:
- Rejection paths — Require comments when an approval is denied (e.g. Reject requires comments, but Approve makes them optional)
- Rework requests — Mandate detailed feedback when asking for revisions (e.g. Request Changes requires comments)
- Fast approvals — Allow approval without comments for routine approvals while requiring explanations for special cases
- Audit requirements — Enforce comment requirements only on specific approval paths that need documentation
How comments appear to users
The following image shows how the Comments box appears to a user completing an approval task with comments configured.

Whether the comment field appears and whether it’s required depends on the selected approval option. Before you publish a process, test each option. An Optional option should accept an empty comment, and a Required option should prevent completion without one. A No option should hide the field. When approval by email is enabled, test the browser confirmation page as well as the portal task.