In compliance with Good Laboratory Practise (GLP) and according to CFR 21 part 11, protocol drafts can be signed and locked upon publishing.
By default, eLabJournal is configured to allow users to publish protocol versions without requiring a signature. If a users organization requires them to sign off on their SOPs, the group administrator can activate the signature setting on the group policies page. It is also possible to require a witness to counter-sign a protocol before publishing it.
Note: while published protocols are locked to prevent further modification, they can still be opened and run with any embedded variables/formulas
To sign a protocol, open the protocol and click the Sign button.
The user must enter their credentials and click Sign Protocol.
Note: Users can also sign their protocols with a two-step verification code
Signed protocols are locked into a run-only mode with any embedded variable/formula fields, and a digital signature, including a time stamp, is visible in the protocol header.
Note: users can create a new draft version of the published protocol to make changes to the content
Signing Protocols with Two-Factor code
If a user's organization uses an organization-specific login (i.e. LDAP / AD / SSO), passwords are not stored within the eLabJournal system. For this reason, experiments can only be signed using a generated two-step verification code. To sign a protocol with a two-step verification code, users must first set up two-step verification for their account.
After clicking on the sign icon, users can enter the two-step verification code in the pop-up window and click the Sign Protocol button.
To access the 6-digit verification code, users can either open the eLabJournal app on their phone and go to the Two-Step Verification code or set it up in the authentication app of their choice.