An overview of the most important new functionality, changes and resolved issues in ValidSign between 1 and 7 October 2026.
Changed functionality
The table below lists existing functionality that has been changed in this release.
| Change | Component | Description |
|---|---|---|
| Two-factor authentication mandatory again | FRONTEND All users |
Before: setting up two-factor authentication (2FA) was temporarily not mandatory. Now: users without 2FA see a notice and have to set up 2FA. The setup can be postponed once. |
| Disabling two-factor authentication with a warning | FRONTEND All users |
Before: the Two-Factor Authentication page showed the verification code field for disabling 2FA right away, so users sometimes disabled 2FA by accident straight after setting it up. Now: the page first shows the status and a clear button to disable 2FA. A warning with a confirmation follows, and only then the field for the code. |
Bug fixes
The table below lists the issues resolved in this period.
| Subject | Component | Description |
|---|---|---|
| Text box: text does not fit the box | PLATFORM | A text box containing more text than fits was not displayed properly inside the box in the signed PDF. The text is now wrapped and the font size is reduced to fit (minimum 4 pt), so the text stays inside the box. The box itself does not grow and stays where it was designed. This applies to multi-line text boxes. |
| 2FA setup screen after switching back from a delegation | FRONTEND | Users who sign in with SSO got the screen to set up two-factor authentication every time they stopped a delegation (switched back to their own account). This has been fixed. |
| Invalid date for a signer | FRONTEND | An invalid date entered by a signer was still saved. An invalid date is no longer saved. |
