Laboratory settings reorganised, session number, Otto-built modules put into service

2026.11.11-reglages-laboratoire-et-modules-construits · 2026-11-11

Delivered build : 1e847e52564e85335821eb514913eb35e9d6f235

Changes

• Settings: two spaces, “My account” and “Laboratory”, organised by question, with a search. “Rights” and “GLP controls” are now two separate tabs.
• Laboratory: laboratory identity (name, address, phone, logo, legal entity), date format, default language for new members and number prefixes; full export of the laboratory's data as one archive; “Where your data goes” page; “Documents and retention” tab; public API keys.
• Member access: access end date per member, signed periodic access review, password and signature policy, sign-in lockout after several failures. These controls stay off until the laboratory turns them on.
• Notifications: choice per notification type (in the app, by email), required alerts set by the laboratory, new alerts for deviations, requested signatures, approvals and equipment maintenance; optional delivery to a team messaging channel.
• Enterprise sign-in and work calendar: available behind a setting, off by default.
• Runs: each session gets a readable number, shown in the PDF report; reloading the page resumes the run in progress instead of creating a second one; a finished session can be attached to a study, an objective or a project with a traced reason.
• Protocols: “All protocols” also shows those filed in a folder; “Move to folder” in a card's menu.
• Otto-built modules: an approved module now really goes into service (its writes were refused); a module in service can be reopened to prepare a new version, the current one staying in use until approval; the declared bounds of a field are enforced on entry, with the unit and the allowed range shown in the form; an entered value can be copied onto the linked record; a view can list only the records that pass a filter, and the tile that cites it counts them.
• Dashboard: the tile of a built module shows its figures and, from medium size up, its chart. A draft's preview shows its tiles and charts as they will appear in service.
• Module approval: the screen says who can approve and flags when nobody else in the laboratory can.
• Registers: exporting a list contains all its records (it used to stop at the first page) and list order is stable from one page to the next.
• Privacy policy updated on the artificial intelligence providers actually used depending on the laboratory's configuration.

Known limitations

• Only a laboratory superadministrator who neither wrote nor submitted a module can approve it; designating a second superadministrator goes through support.
• Automatic creation of linked records by a module action is not executed: it is refused at build time and is done by a separate action.
• Mandatory enterprise sign-in is stored but not yet enforced at sign-in.
• The new alerts send no email by default: the choice is made in the notification settings.