We released the ability for Admins to force senders and recipients to provide a reason for canceling, declining, deleting, or revising a signature request within Box Sign. This capability is accessible and configured via a setting within the Admin console enables Admins to determine whether to force senders to provide a reason for canceling, revising, or deleting a signature request.
Additionally, Admins can configure the option to force signers to provide a reason for declining signature requests. These control were designed to meet stringent compliance needs, especially for 21 CFR Part 11 and GxP validation environments, and provides organizations with greater control over the types of actions that take place on signature requests managed by users on behalf of their enterprise. This feature provides the auditability and visibility that highly regulated companies need to stay in compliance.
This feature introduces two new enterprise toggles:
- Enforce reasons for sender actions
- Enforce reasons for signer actions.
Enforcement is applied at the moment the action is performed. With this setting enabled:
- When a signature request is canceled or deleted, the reasons provided are captured in the User Activity Report.
- When a signature request is revised or declined, the reasons provided are captures in the signing log provided at the end of the transaction.
The provided reasons are also surfaced in notification emails where applicable.
Any time a sender or signer declines or revises a signature request, that action and the reason provided will generate a signing log entry that include the reason and timestamp. Email notifications for signer actions include the reason at the top. If a sender cancels or deletes a signature request, that action and the reason provided are included in the User Activity Report generated by the Admin of the enterprise.
To learn more about this release, please see Enabling Sender Controls, Enabling Recipient Controls, and Viewing the Signing Log.