> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bowerlabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Electronic signatures

> Sign finished protocol runs and whole collections with your Bower password, ask a colleague to review or witness, and lock, unlock and export a signed record.

Electronic signatures let members sign a finished [protocol run](https://docs.bowerlabs.ai/organisation/protocols.md#protocol-runs), or a whole [collection](#sign-a-collection) as one record. A signed run is locked, so its record can't change, until it's [reopened](#withdraw-reject-or-unlock). Every signature, request and unlock is kept in the record's audit trail.

> [!NOTE]
>
> Electronic signatures are available to workspaces they are enabled for. If **Settings** doesn't list **Electronic signatures**, they aren't enabled for your workspace yet. [Contact us](mailto:support@bowerlabs.ai) to ask about them.

## Turn on electronic signatures

In a workspace electronic signatures are enabled for, Owners and Admins turn signing on for the whole workspace.

**1. Open Settings > Electronic signatures**

**2. Switch on Electronic signatures**

Finished protocol runs can now be signed by anyone with a [signing privilege](#choose-who-can-sign).

**3. Choose whether runs need a review signature**

With **Runs need a review signature** on, a finished run counts as closed only once the person who ran it and a reviewer have both signed. Until then it shows **Awaiting signature** in the protocol library.

Turning signing off later keeps every signed run locked and visible. Unlock a run to change it.

## Choose who can sign

There are two signing privileges:

| Privilege | What it allows |
| - | - |
| **Can sign** | Sign a run they performed, as its performer. |
| **Can review** | Sign someone else's run as a reviewer or witness. |

Owners and Admins have both unless someone turns them off, except Bower Support members (marked **Bower Support** in the member list), who have only what they are given. Members have only what an Owner or Admin gives them, under **Signing members** in **Settings > Electronic signatures**. You can't change your own privileges. If an Owner or Admin becomes a Member, they keep only the privileges they were given explicitly. A Bower Support member's privileges can only come from an Owner or Admin of your workspace who isn't Bower Support. Bower Support also can't change who signs or reviews, for anyone, except in a workspace Bower set up for you while Bower still owns it.

Before a privilege is granted, Bower asks you to **Confirm their identity**. Click **I verified their identity** only once you know the person is who their account says. Bower records your name and the date with the grant.

Guests can't sign, so their switches are unavailable.

### Find a member in a long list

* **Search by name or email** narrows the list as you type.
* The filter next to it shows only members who **Can sign**, members who **Can review**, or members with **No Bower password**. Choose **Clear selection** to show everyone again.

The list shows 50 members at a time. When there are more, a line under it says how many are shown; search to find the others.

### Members with no Bower password

A **No Bower password** label means the member signs in only with another account, such as Google or Microsoft, and hasn't set a Bower password yet. They can't sign until they do. Ask them to [set a Bower password](#set-your-bower-password) before their first signature.

If Bower can't check every member's password, the filter says the list may be incomplete.

## Your Bower password

You sign with your **Bower password**, the same password you can sign in with. There's no separate signing password.

### Set your Bower password

If you sign in with Google or Microsoft, you may not have a Bower password yet. You can set one in either place:

* **Settings > Security**: see [Change your email or password](https://docs.bowerlabs.ai/workspaces-and-account/manage-account.md#change-your-email-or-password).
* The first time you sign a run: the signing dialog asks you to set one first, with **New Bower password** and **Confirm password**, then **Set password**. It works the same way as in **Settings > Security**.

### If your password is refused several times

After 5 wrong passwords within 15 minutes, you can't sign, withdraw, reject or unlock for 30 minutes, in any workspace. Every Owner and Admin of the workspace where it happened is told.

## Sign a run

Signing works only in the Bower web app, not in the mobile app.

**1. Open the run's record**

Click the run in the protocol library. The **Signatures** section is below the record's **Summary**.

**2. Click Sign**

The section lists the run's signatures as steps, in order: performed, reviewed, witnessed. It shows how many are signed, such as **1 of 3 signed**, and each step says who signed it, who is asked, or that it is not signed yet. Every step open for signing shows its button to everyone: **Sign** for the performer, and **Sign as reviewer** or **Sign as witness** once the performer has signed (**Sign** when you were asked). The person who performed the run signs first. If you can't sign a step, its button is grayed out: hover over it, move to it with the keyboard or tap it to see why, for example who has to sign first.

**3. Enter your Bower password and click Sign**

The first time you sign a run in a workspace, Bower also asks for **Your full name**. It prints on your signatures in that workspace and becomes your profile name.

The dialog shows a **Content fingerprint**: a short code for the exact content you're signing. It also shows the statement you agree to by signing: "Your electronic signature is the legally binding equivalent of your handwritten signature."

### When can a run be signed?

A run can be signed once it has ended, **Completed** or **Ended early**, and Bower has everything from it:

* Usually, signing opens 15 minutes after the run finishes, so late photos and videos can arrive. A run that recorded a missing capture can be signed without the wait.
* Every capture has finished uploading and processing.
* The run's transcript, if it has one, is finished.

A run that **Ended early** can be signed too, so a run stopped part way, by a failed sample or an instrument that went down, still gets a signed record. Before you enter your password, the dialog warns you that the run ended early and how many of its steps were done. The signed record and its PDF say so plainly, for example "Abandoned, 2 of 5 steps done (1 skipped)", so no one can take it for a completed run. A run that ended early stays as it stopped: unlocking or rejecting its record does not reopen it for changes.

## Sign a collection

You can sign a collection as one record: its name and description, and every note, file, link, protocol and spreadsheet in it and in its sub-collections. Signing a collection locks everything in it, so nothing in it can be edited, moved or deleted until it's [unlocked](#withdraw-reject-or-unlock).

**1. Open the collection and click Signatures**

**Signatures** is at the top of the collection. It reads **Signed** once the collection is signed.

**2. Click Sign**

The person who created the collection signs first. Others then review or witness it, as for a run.

**3. Check what you are signing**

The dialog lists every item the signature covers, under **What you are signing**. Anything that stops the collection from being signed is listed first, with the reason.

**4. Enter your Bower password and click Sign**

### What can't be signed in a collection

A collection can't be signed while it holds:

* equipment;
* a file that is still uploading or processing;
* a protocol with no approved version yet;
* a protocol run's folder. Sign the run itself instead.

A collection with more than 2,000 items, or more than 10 spreadsheets, can't be signed either. To sign a collection, you need to be able to open everything in it.

A spreadsheet in a collection is signed as it looked in the signing dialog. Once the collection is signed, the spreadsheet can't be edited.

## Ask someone to review or witness

Once the performer has signed, the performer, an Owner or an Admin can ask a colleague for a second signature. Click **Ask someone** under the review or witness step, then pick a member in the dialog that opens. The person you ask needs **Can review**. The person who performed the run can't also review or witness it.

The person asked can sign, or decline the request with a reason. Declining leaves the run and its signatures as they are. A request expires after 30 days. If the person asked leaves the lab, loses **Can review**, or loses review with a role change, their open requests are canceled, and the audit trail records who made the change.

### Requests waiting for you

When someone asks you to review or witness a run, it appears under **Waiting for your signature** in the sidebar, above **Favorites**. Each row shows the protocol, what you're asked to do and when the run started. Click a row to open the run and sign it there.

A row goes away once you sign or decline, or when the request is canceled or expires. The section is hidden when nothing is waiting, and it lists only runs you can open. If more than 100 requests are waiting, it shows the newest 100 and says so.

## Withdraw, reject or unlock

Once a record is signed, these are buttons in a row at the bottom of the **Signatures** section, next to **Export signed record**. A button you can't use is grayed out: hover over it, move to it with the keyboard or tap it to see why, for example who signed after you. Each asks for your Bower password and a reason of at least 10 characters, which is kept in the audit trail.

| Action | Who | What happens |
| - | - | - |
| **Withdraw my signature** | The person who signed, as long as nobody has signed after them | **Performer:** the run unlocks and any open requests for signatures are canceled. **Reviewer or witness:** the run stays locked, and you can't sign it again until it's reopened. Either way, your signature stays in the audit trail as **Withdrawn**. |
| **Reject** | The person asked to review it | The run goes back to the performer for correction. Signatures in this round are marked **Superseded** and stay in the audit trail. |
| **Unlock** | An Owner or Admin with **Can review** who hasn't signed this round | The run reopens for changes and must be signed again. Its signatures are marked **Superseded** and stay in the audit trail. |

## What a signature covers

A signature covers the run's content and every capture signed with it, including the exact bytes of each photo, video and file. A photo or recording taken under a note during the run is covered too: while the run is locked, it can't be edited, replaced or deleted.

A run signed with an earlier version of Bower is the exception. Its signature covers each note but not the photos and recordings under it, and its export says **hashVersion 1: attachments nested under notes are not covered**. Bower still stops those photos and recordings from being edited, replaced or deleted while the run is locked. To bring them under the signature, unlock the run and sign it again.

## See what was signed

If a signed run changes after it was signed, the **Signatures** section says **Record changed after signing**. Open **What was signed** to see the signed version and **Changes since signing**: captures added, changed or removed.

## Export a signed record

You can export a signed run or a signed collection. Click **Export signed record** at the bottom of the **Signatures** section. Bower builds the export in the background, which takes a few seconds for most records, then downloads a ZIP file. For a run, it holds:

* **record.pdf**, the signed record to print or file: every signature first (name, email, meaning, the time in UTC and in the signer's time zone, how they confirmed who they were, and any comment), then the run and its steps, the files in the export, the run's history, and last anything added after signing, marked as outside the signature;
* **record.html**, the same page to open in a browser without Bower;
* a **files** folder with every note captured during the run and its transcript as a PDF, the protocol as a PDF at the version the run used, and every photo, video and file exactly as it was uploaded;
* **manifest.json**, which lists every item and file in the export with its fingerprint (a SHA-256 hash). For an uploaded file it gives both the fingerprint the signature covers and the fingerprint of the file in the ZIP, so you can confirm they match;
* **VERIFY.txt**, which explains how to check the export yourself, with a short script that does it;
* the signed content of every signing round as it was signed, every signature and request, and the record's audit trail as a CSV file.

For a signed collection, the ZIP holds the same files, with two differences:

* **record.pdf** shows the collection's name and description and lists every item the signature covers, with its place in the collection and its fingerprint. A collection can't have anything added after signing, so there is no section for that;
* the **files** folder keeps the collection's layout, with a folder for each sub-collection. Notes are PDFs, protocols are PDFs at the version that was signed, uploads are exactly as they were uploaded, and links are listed in **links.csv**. Each spreadsheet has a folder of its own with its data exactly as it was signed and, when one can be made, an Excel copy that Bower checks against that data.

Every item in the export is the item as it was signed. If the collection was unlocked and changed afterwards, the export still holds what was signed, not what is in the collection now.

You need to be able to open every item in the run or collection to export it. An export is never partial: if a record has more than 2,000 items or more than 2 GB of files, or an item can't be included, Bower says so and doesn't download anything.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.