Current behavior
When a recipient rejects a document/signature request, DocuSeal sends notifications only to the remaining workflow participants/signers.
However, the original requester/applicant (the person who initially submitted or started the process) does not receive a notification about the rejection.
Expected behavior
The original requester/applicant should also receive a rejection notification, ideally including:
- information that the document was rejected
- the rejection reason/comment
- who rejected the document
Why this is important
This is especially problematic in administrative workflows (e.g. schools, public administration, approval processes), where:
- the applicant expects feedback about the status,
- rejected requests otherwise remain unclear,
- and additional manual communication becomes necessary.
Tested on
- DocuSeal v2.5.2
- Docker / Portainer deployment
- PostgreSQL backend
Additional note
The current tooltip text ("The notification with the rejection reason will be sent to the requester of the signature") is somewhat misleading, because the original applicant/requester is apparently not notified.
Current behavior
When a recipient rejects a document/signature request, DocuSeal sends notifications only to the remaining workflow participants/signers.
However, the original requester/applicant (the person who initially submitted or started the process) does not receive a notification about the rejection.
Expected behavior
The original requester/applicant should also receive a rejection notification, ideally including:
Why this is important
This is especially problematic in administrative workflows (e.g. schools, public administration, approval processes), where:
Tested on
Additional note
The current tooltip text ("The notification with the rejection reason will be sent to the requester of the signature") is somewhat misleading, because the original applicant/requester is apparently not notified.