Twind Product Team · July 28, 2026
Critical agreements come first.
When a contractor accesses Requirements > Upload, if they have critical agreements in Pending upload, Expired, or Rejected status, a Pending Critical Agreements modal appears before they can manage anything else. The contractor can't upload documentation for that client until they accept them.
The modal only blocks requirements for the affected client. Requirements for other clients remain fully manageable in the same list. Closing the modal with the X doesn't lift the block — the only way to unblock it is to accept the pending agreements.
Add-on. Off by default.
The block is an add-on activated from the admin panel. The default state is OFF for all clients — existing and new. It's only activated when the client requests it.
Why does it exist? In Spain, critical agreements are the mechanism client companies use to document the duty of information and instruction under RD 171/2004. Others use them for confidentiality agreements and personal data transfer. Without a block at the upload point, contractors would upload all additional requirements first and leave the agreements pending — a potential compliance gap.
Dependents no longer get stuck.
In self-contracts with automatic approval, when a primary requirement is automatically approved, its dependent requirements are now also approved in the same process. Previously, the cascade logic only ran during manual review — dependents got stuck in Pending upload with no manual intervention.
The dependents approved are exactly the ones a reviewer could have cascade-approved during manual review.
Each approved dependent is attributed to automatic approval, not to a reviewer.
If the primary requirement has no eligible dependents, automatic approval works exactly as before.
Need help?
🟩 WhatsApp: +34 664 281 487
❓ Twind Chat: click the chat icon in the bottom-right corner of your screen. A window will open and you can chat with us.