Security settings and team two-factor authentication

2026.10.12-securite · 2026-10-13

Delivered build : 0b7753bda3bb66bbaf5e39dfec213b9c389dcc49

Changes

• The inactivity lock setting now sits directly below two-factor authentication in Security and uses the application’s fields, buttons and colours. The unlock screen follows the same presentation.
• Administrators can require two-factor authentication for their team with a single click on a switch in the same section. Save results and errors are displayed.
• Late responses when loading or saving security settings are ignored after an account or team change, keeping the displayed settings bound to the active identity.
• Update detection resumes after an initial download fails. The fifteen-minute check, five-second idle grace period and deferral during an execution or recording are retained; activating a new worker causes a single controlled reload.
• Settings, Profile and Appearance use the full available width. The laboratory permissions matrix uses the application’s colours, translated role names and a horizontally scrollable table on mobile.
• Protocol approval actions open the Versions tab: prepare an exact state, submit it, then have it signed by a reviewer distinct from the author and submitter. Signed approval makes that version current and activates the protocol. A change after preparation requires a new version to be prepared before signing.
• The Approvals queue shows protocol versions actually awaiting review alongside accessible historical requests. Each pending version opens its own decision workflow; a failed read is shown and can be retried.

Known limitations

• An administrator must enable their own two-factor authentication before requiring it for their team.
• The team requirement does not set up members’ authenticators: each person must complete enrolment using their own device.
• The shared service does not yet support an independent complete client, API and database release per laboratory. DocuSign remains unconnected: no provider account is available and no embedded signing view is delivered.
• A tab already stuck on an older version may require a manual reload to load this fix.
• Historical approvals are not converted into signatures of exact versions. For an older protocol without a usable retained state, a new preparation explicitly retains its current content with the actual preparation date.