../_images/banner-signatures.svg

Signature process

The signature of your data can be set on both experiment and study detail windows. It aims to sign all the related data in two steps: signature level 1 and signature level 2.

What is going to be signed?

Test

Experiment

Study

Name, code, dates

Name, code, dates

Name, code, dates

Notes

Hypothesis, Conclusion/ Discussion

Hypothesis, Conclusion/ Discussion

Document(s)

Document(s)

Document(s)

Table results

Report

Report

Item(s)

Equipment(s)

Quality document(s) link


General process of the signature:

The signature can be applied on the experiment and study levels.

All related test must be completed, before starting the process. Start and End dates must be defined on all of the tests included in the experiments.

Signature level 1

The signature level 1 will lock your data and generate the necessary folders for the digital signature authentication.

Note

Condition to sign level 1.

  • Not be in read only mode.

  • All data must be saved previously.

  • For the study level, a report is mandatory.

  • All related tests (and experiment(s) for the study signature) need to be locked.

  • The user must confirm the action using his password.


Follow these 2 steps to sign the experiment on level 1:

  1. If not done, lock the tests (experiments if you are locking a study).

../_images/lock_xp1.png

Signatures page, located inside an experiment.


  1. Click on the “sign” button and confirm with your password.

../_images/sign_xp1.png

Confirmation window, where you need to include your password.


Signature level 2

The signer on Level 2 must be different from the first signer. To sign it, you need to click on the sign button and confirm it with your password.

../_images/sign_xp3.png

Signatures window, showing that both signature were done.


Danger

The signature level 2 is definitive. Impossible to reset.


What’s behind the signature?

Signature authentication

In Laby, the signature generates a folder containing all the data and documents linked to the entity. The date are hashed, generating an alpha-numeric key. This key is then timestamped by an external company server.

Note

Confidential and non-confidential data are not sent or shared with the external service.

../_images/signature_process.png

Flow representation the signature process.

Signature verification

During an audit, we can access to all the signed data. Laby ensures the integrity using an algorithm which checks that the data and documents have not been changed.

../_images/signature_verification.png

Flow representing the verification process.