# SciShield application guide

Practical documentation for researchers, lab members, principal investigators, and compliance staff using the SciShield Scientific Management Platform.

This guide was verified on **12 November 2026**, using the logged-in local application at `http://earth.127.0.0.1.nip.io:8083`. The footer identifies the build as **v3.10.3.20261103.2621**. Examples use the available Bruxner Lab Group and the current member account. Your institution, enabled modules, memberships, and permissions determine what you see.

## Start with your task

| I want to… | Read |
| --- | --- |
| Understand the home page and navigation | [Getting started](getting-started.md) |
| Find my lab, members, rooms, or documents | [Labs, members, and spaces](labs.md) |
| Find overdue work and compliance requirements | [Compliance dashboard](compliance.md) |
| Take training or find a certificate | [Training and courses](training.md) |
| Check equipment status or audit dates | [Equipment](equipment.md) |
| Read inspection history and required checks | [Inspections](inspections.md) |
| Track approvals or submit a lab form | [Lab forms](forms.md) |
| Review biological registrations and certification | [Biological safety](biological-safety.md) |
| Find isotope authorizations, vials, or pickup tools | [Radiological management](radiological-management.md) |
| Find an SOP, SDS, document, or contact | [Research resources and SOPs](research-resources.md) |
| Report a safety concern, incident, or near miss | [Safety reporting](safety-reporting.md) |
| Review my profile and messages | [My account and messages](account.md) |
| Resolve missing menus, records, or integrations | [Troubleshooting](troubleshooting.md) |
| Run or host this documentation | [Hosting and maintenance](README.md) |

## A useful daily routine

1. Open the home page and review **Needs Attention**, **Required Training**, and **Messages**.
2. Select the correct lab in **Compliance Summary for**.
3. Open **View Dashboard** and review training delinquencies, equipment audit dates, and authorization status.
4. Use the lab's **Requirements**, **Lab Inspections**, and **Self Inspections** pages for detailed follow-up.
5. Open the relevant source record before acting. A summary count is a starting point; the record contains the context.

![SciShield home page with required training and lab compliance summary](assets/screenshots/home.jpg)

Screenshots are expandable: select an image to view the original. Names, dates, counts, and sample records belong to this local dataset and will change.

## Read as Markdown or HTML

Every guide has a **View Markdown** link above its HTML content. The Markdown files are the canonical source; the server renders them at request time.

Agents can start from [the AI index](/llms.txt), [the JSON index](/api/pages), or [the complete Markdown corpus](/all.md). Individual files are available directly, for example [training.md](/training.md). No browser JavaScript is needed to retrieve guides or search results.

## Search behavior

Search checks the full Markdown source of each page, including its title. Every space-separated word must occur somewhere in the same page. Matching ignores case and uses literal substrings; word order and adjacency do not matter.

- `training overdue` and `overdue training` return the same pages.
- `bio` can match `biological`.
- Quotes, `%`, and `*` are literal characters, not special operators.
- A blank query asks for search words rather than returning every page.

See [scope and verification](coverage.md) for what was inspected and which downstream actions remain unverified.


---

# Getting started

## Open the application

The inspected development instance is at `http://earth.127.0.0.1.nip.io:8083/frontpage_panel`. It is already signed in for this documentation capture. On another deployment, use the address and sign-in process provided by your institution. Sign-in and account recovery were not exercised in this session.

The home page is titled **Scientific Management Platform**. The SciShield logo in the header links home. **Toggle navigation** expands or collapses the sidebar. The header also contains **Notifications** and **User menu** controls.

## Use the sidebar

Select a section's button to expand its links. Each lab has its own section. The inspected account belongs to three labs, so checking the lab name before opening a record matters.

| Section | Available links |
| --- | --- |
| A lab, such as Bruxner Lab Group | View Lab Profile, Compliance Dashboard, View Members, Send Lab Message, View Lab Spaces, Bio Summary, Rad Summary, Rad Request, Rad Waste Pickup, Self Inspections, Manage Lab Forms |
| SOPs | Organizational SOPs |
| Research Tools | Announcements, Document Library, External Links, Important Contacts, SDS Search |
| Training | My Training, Course Directory |
| Equipment | My Equipment |
| My Account | Account Settings, individual lab links, Messages, Log out |

Some links depend on the lab: the third lab's menu had fewer entries than the first two. Absence of a link does not establish that the feature is disabled institution-wide.

## Read the home page

![Home page and navigation](assets/screenshots/home.jpg)

**Report choices.** The top of the home content provides **ObservNow™ Safety Concern**, **Incident or Near Miss**, and **Visit Knowledge Base** links. Reporting forms are explained in [Safety reporting](safety-reporting.md). The knowledge base is a separate integration and was not followed.

**Needs Attention.** A personal setup item may appear with **Start Now**. The captured example concerns an incomplete Animal Contact Review Wizard. It is specific to the account; its questions and submission were not inspected.

**Announcements.** Select an announcement title or **[more]** to read it. **View All Announcements** opens the announcement list. Announcement dates and instructions reflect institutional content.

**Required Training.** Each row contains a status, course name, and renewal date. The captured page shows both **Overdue!** and completed rows. **Never** appears as the renewal value on some completed courses; it is not the same as a course never having been completed. Use [My Training](training.md) to inspect completion dates.

**Messages.** Subject links open individual messages; **View Entire Inbox** opens messaging. The captured home page and the separate inbox did not agree on the number of messages. See [Troubleshooting](troubleshooting.md).

**Compliance Summary for.** Choose a lab and use the Biological, Radiological, Training, and Equipment status links or **View Dashboard**. Confirm the displayed lab heading before following an issue.

**SDS Search.** The home page offers a chemical name or CAS number field. Research Tools also provides an SDS screen with advanced filters.

## Work with tables

Many tables offer sortable column headers, filters, and pagination. Sortable headers are links or have a sorting label. A result count such as “Showing 1–25 of 34 results” means additional records are on another page.

An empty table can mean no matching records, no records for this context, or a loading/integration problem. Clear filters and confirm the lab before concluding that nothing exists.

## Accessible navigation

The application exposes **Skip to navigation** and **Skip to main content** links. The documentation also has a keyboard-accessible skip link, a labeled search input, visible focus styles, and text links to all guides. Screenshots supplement the written steps.

Next: [Labs, members, and spaces](labs.md) or [Training and courses](training.md).


---

# Labs, members, and spaces

## Open a lab profile

1. Expand the lab's name in the sidebar.
2. Select **View Lab Profile**.
3. Check the main heading to confirm the lab.

The profile shows the principal investigator, group compliance liaisons, department, building and rooms, safety contacts, research focus, lab categories, major hazard categories, and the last PI hazard certification date. A compact compliance summary links to the dashboard.

![Lab profile with contacts and research focus](assets/screenshots/lab-profile.jpg)

The inspected example resolves to `/node/19939`. The sidebar uses `/raft/group_page/19939/view`; the application may redirect to a canonical node URL. Numeric IDs are specific to this dataset. Navigate through menus on another institution's deployment.

## Understand the two tab levels

The upper lab navigation provides **View**, **Dashboard**, **Members**, **Requirements**, **Bio**, and **Rad**. Under **View**, another row provides **Spaces**, **Documents**, **Forms**, **Equipment**, **Lab Inspections**, and **Self Inspections**.

Use the upper navigation to switch between lab-wide functions. Use the second row for records associated with the profile.

## Find members

Select **View Members** in the lab menu or **Members** in the upper navigation. The member table contains **Name**, **Group Role**, **Email**, and **Designation**.

![Lab member directory](assets/screenshots/members.jpg)

The captured roles include **Owner**, **Group Administrator**, and **Member**. Designations include roles such as PI, Lab Manager, and Research Associate. Group role and designation are separate fields; a job designation alone does not establish editing permissions.

Select a person's name to open their profile. Membership editing, invitation, removal, and permission changes were not exposed on the inspected member list and are not documented as available actions.

## Find a lab space

1. Select **View Lab Spaces**, or open **View → Spaces**.
2. Use the **Hazards** filter if relevant.
3. Read the space name, description, contact, associated labs, hazard update date, and door sign date.
4. Select the space name to open its detail record.

![Spaces table with hazard and door sign dates](assets/screenshots/spaces.jpg)

Multiple labs can be associated with one room. A room's appearance in your lab list does not mean it is used exclusively by that lab. **Space Hazards Updated** and **Door Sign Last Created** represent different events; compare them when investigating an outdated sign.

The captured table has sortable **Space Name** and **Space Hazards Updated** headings. Space detail editing and door sign generation were not exercised.

## Documents, forms, and equipment

**Documents** in the lab profile is distinct from the institution-wide **Research Tools → Document Library**. Its tab was observed, but its contents and upload workflow were not inspected.

**Forms** opens the lab's review and submission list. See [Lab forms](forms.md).

**Equipment** provides a lab context for assets. **My Equipment** may contain assets from several labs and spaces. See [Equipment](equipment.md).

## Contact the lab

Use the profile's compliance liaison and safety contacts to identify the right person. The lab menu also exposes **Send Lab Message**. Its compose and delivery workflow was not exercised; verify recipients before sending a real message.

Next: [Compliance dashboard](compliance.md).


---

# Compliance dashboard and requirements

## Review the correct lab

Open **Compliance Dashboard** under a lab in the sidebar, or select a lab in the home page's **Compliance Summary for** control and use **View Dashboard**. The dashboard heading identifies the lab.

![Compliance dashboard with authorizations, training, equipment, and inspection summaries](assets/screenshots/compliance.jpg)

## Read dashboard sections

| Section | What to inspect | Useful next action |
| --- | --- | --- |
| Authorizations & Licenses | IBC authorization submission and renewal information; radioactive material license issue and renewal information | Use the relevant **(view/update)** link to inspect the source record |
| Member Summary | People, designations, and job activities grouped into Biological, Animals, Chemical, Radiological, Physical, Vehicles, and General tabs | Check the person's applicable activities before investigating requirements |
| Training Summary | Members audited, total training requirements, members delinquent, number of delinquencies, and compliance score | Read the Delinquency Report |
| Delinquency Report | Person, course, completion, and expiration | Open the person or course to investigate |
| Equipment Summary | Asset identity, location, and audit expiration | Open **View** or the serial number |
| Hazard Summary | Lab hazards organized by category and last PI certification date | Review the appropriate lab registration or contact the PI |
| Inspection Summary | Recent inspections, findings, ratings, status, and finding frequency | Open the inspection or full history |
| Self Inspection Summary | Recent self inspections and finding frequency | Open the full self inspection history |

The captured dashboard reports 15 members audited, 89 training requirements, 5 delinquent members, and a 94.38% training compliance score. These are examples of the displayed metrics, not current targets or a guarantee that all aspects of the lab are compliant.

## Investigate overdue training

1. Read the **Delinquency Report**.
2. Identify the person and course.
3. Open the source record and compare completion and expiration dates.
4. Use the [Course Directory](training.md) to find the relevant learning or classroom option.
5. After completion is recorded, re-open the source record and dashboard to confirm the status changed.

In the captured report, **never** appears in the completion column for some delinquent courses and **N/A** appears in the expiration column. Interpret each value in its column context.

## Review the Requirement Summary

Open **Requirements** in the upper lab navigation. This provides a separate list containing **Requirement Name**, **Requirement Type**, **Applies To**, **Required For**, and **Next Required**.

![Lab Requirement Summary and filters](assets/screenshots/requirements.jpg)

Filters include **Applies To**, **Requirement Name**, **Requirement Type**, **Required For**, and **Next Required Between**. The **Include "Never Completed"** checkbox lets you include requirements that do not have a completion date when using date-oriented filtering.

The inspected list includes both inspection and equipment requirements. For equipment, the **Required For** value identifies the particular asset. For inspections, it identifies the lab. Use that distinction to route follow-up correctly.

## Dates, missing values, and conflicts

- **Never Completed** means the requirement list has no completion recorded for that requirement.
- **N/A** or **--** should not be interpreted as approval. Inspect the underlying record if the meaning matters.
- Dashboard inspection summaries use a displayed **last 18 months** window. Older inspection history can exist even when the recent summary is empty.
- A captured radioactive license date differed by one day between the compliance dashboard and Rad Summary. Compare source records and ask compliance staff to resolve discrepancies; do not infer which date governs.

The dashboard summarizes recorded application data. Authorization decisions and edits were not performed for this guide.

Related: [Inspections](inspections.md), [Equipment](equipment.md), [Biological safety](biological-safety.md), [Radiological management](radiological-management.md).


---

# Training and courses

## Check required training

The home page's **Required Training** table shows course status and renewal dates. Select a course name to open its sessions or course page. An **Overdue!** entry calls attention to a required course; open its details before deciding how to complete it.

The home page also links **Training History** and **Course Directory**. The sidebar provides the same general workflows under **Training**.

## Review completion history

1. Expand **Training**.
2. Select **My Training**.
3. Confirm the person's name in the heading.
4. Use **Filter Records By** to choose **`<All>`** or **Most Recent Only**.
5. Compare **Course**, **Date Taken**, **Expires**, and **Certificate**.

![Personal training records](assets/screenshots/training.jpg)

The list has sortable course, completion-date, and expiration-date columns. **Most Recent Only** is useful when repeated completions make the history difficult to scan; **`<All>`** provides historical context.

Select **Certificate** on a row where that link is present. Some records have no certificate link. A missing link does not itself prove that the course was not completed: check **Date Taken**. Certificate generation and downloading were not tested during capture.

The secondary **Training Requirements** link was observed in the training navigation. Its detailed contents were not inspected; the home page and lab dashboard provide verified entry points for required or delinquent training.

## Find a course

Select **Training → Course Directory**. The captured directory groups courses into **Biosafety**, **Facilities**, **General Lab Safety**, and **Radiation Safety**.

![Course directory with Launch Course and Sign up actions](assets/screenshots/courses.jpg)

| Action | Intended next step |
| --- | --- |
| Course name | Read the course detail |
| Launch Course | Open the online learning workflow |
| Sign up | Open classroom session information |

Online courses and classroom courses have different entry actions. This guide inspected the directory and a classroom sessions page, but did not launch learning content, register attendance, take an assessment, or record a completion.

## Classroom sessions

1. Find the classroom course in the directory.
2. Select **Sign up**.
3. Read the course description and prerequisites.
4. Review **Upcoming Sessions**.
5. If no sessions are scheduled, use the course manager information shown on that page.

![Classroom course with no upcoming sessions](assets/screenshots/course-sessions.jpg)

The inspected BSL2 classroom course had no upcoming sessions. Its page explicitly directs users to the course manager for scheduling. The registration controls for a scheduled session therefore remain unverified.

## Resolve a missing completion

Compare the course title, training history, and required course entry. A similarly named course may be a different record or delivery format. If a completion or certificate is absent after you expect it to be recorded, contact the course manager or your institution's training team with the course and completion details.

Do not treat a historical certificate alone as proof that the current requirement is satisfied; compare renewal or expiration information as well.

Related: [Compliance dashboard](compliance.md), [Troubleshooting](troubleshooting.md).


---

# Equipment

## Find equipment available to you

Open **Equipment → My Equipment**. The page explains that it includes equipment you can access directly and equipment recorded for a lab or space you are assigned to.

![My Equipment list with audit expiration and pagination](assets/screenshots/equipment.jpg)

The captured account has 34 results, with 25 shown on the first page. Use the numbered pages, **next**, or **last** to inspect the remaining results.

| Column | Use |
| --- | --- |
| Type | Identify the category, such as freezer, hood, or biosafety cabinet |
| Manufacturer / Model | Distinguish similar assets |
| Serial Number | Open the equipment detail record |
| Building / Room # | Confirm physical location |
| Audit Expiration | Identify recorded audit deadlines or missing applicability |

**Type**, **Manufacturer**, and **Audit Expiration** are sortable in the inspected list. A lab's profile also has an **Equipment** tab, and its dashboard includes an equipment summary.

## Inspect an asset

Select the serial number. Check identity and location before using the record for follow-up.

![Equipment detail record with notes, documentation, and audit reports](assets/screenshots/equipment-detail.jpg)

The inspected freezer record contains:

- **Equipment Details:** serial number, manufacturer, model, configuration, temperature, and liquid nitrogen usage.
- **Location & Owner:** building, room, and labs using the asset.
- **Additional Information:** asset tag, status, and additional details.
- **Notes on this equipment:** note titles, submitters, and dates.
- **Documentation:** attached files, or an explicit empty state.
- **Audit Reports:** audit type, last completed, and next due.

Fields vary by equipment type. The freezer's details should not be assumed to be the form for a laser or radiation device.

## Review audit status

Use **Audit Expiration** in the list and **Audit Reports** in the detail record together. Some rows show **N/A**, while others have dated expirations. One captured biosafety cabinet is explicitly **Out of Service**. An asset's presence in the list does not establish that it is available for use.

The lab's **Requirements** page provides equipment-specific requirements such as calibration, certification, and tests, including the asset to which each applies. See [Compliance dashboard](compliance.md).

## Request a correction

If the model, serial number, location, status, or audit history appears wrong, record the asset identity and contact the responsible lab or equipment/compliance staff. Asset creation, editing, service status changes, audit submission, and document uploads were not exercised or verified for this account.

Related: [Labs, members, and spaces](labs.md), [Inspections](inspections.md).


---

# Inspections and self inspections

## Choose the right inspection list

Open the lab profile and select **Lab Inspections** or **Self Inspections**. The lab menu also offers **Self Inspections** directly. These are separate histories with their own required checks.

The compliance dashboard summarizes recent inspections over the displayed **last 18 months**. The full logs include older records. An empty recent summary does not imply the lab has never been inspected.

## Lab inspections

![Lab Inspection Log with required inspections and status filters](assets/screenshots/lab-inspections.jpg)

The page starts with **Required Inspections**, showing the inspection type, relevant requirement, and next required date. A **Never Completed** value calls attention to a missing recorded completion for that requirement.

The inspection log shows **Date**, **Inspection Type**, **Inspected By**, **Resolved Findings**, **Status**, **Rating**, and **View**. Use **Inspection Type**, **Status**, **Performed After**, and **Performed Before** to narrow the list. The captured list has 81 results across four pages.

1. Confirm the lab name.
2. Set a type or status filter if investigating a particular issue.
3. Open **View** beside the relevant inspection.
4. Review the findings in that inspection before arranging follow-up.

Inspection detail and finding resolution controls were not inspected. Do not assume the captured account can finalize an inspection or resolve a finding.

## Interpret status and findings separately

Observed status options include **Pending Resolution**, **Needs Assistance**, **Pending Inspector Review**, and **Finalized**. They describe workflow states shown by the application.

The captured list includes a finalized inspection with **0 / 3** resolved findings. Therefore, **Finalized** alone does not establish that every finding has been resolved. Read **Resolved Findings** and the inspection record together.

The finding-frequency section below the history summarizes categories over the displayed 18-month window. Use it to identify recurring issues, then open the source inspections for context.

## Self inspections

![Self Inspection Log and required self inspections](assets/screenshots/self-inspections.jpg)

The self inspection log has an **Inspection Type** filter and a **Performed Between** date range. Rows list the date, inspected groups, inspection type, findings count, and **View**.

Below the history, **Required Self Inspections** lists inspection types, relevant requirements, and next required dates. The captured lab has two historical self inspections, no findings within the recent summary window, and several required checks. These facts can coexist because history, recent summaries, and requirements answer different questions.

## Follow up on a requirement

Compare **Required Inspections**, **Required Self Inspections**, and the lab's [Requirement Summary](compliance.md). Confirm which inspection type applies and whether its deadline is dated or **Never Completed**. If the lists disagree, bring the requirement and inspection names to compliance staff rather than treating one summary as decisive.

Creating an inspection, submitting answers, attaching evidence, resolving findings, and final approval were not performed for this guide.


---

# Lab forms and approval states

## Open the lab's forms

Expand the lab menu and choose **Manage Lab Forms**, or open **View → Forms** in the lab profile. Confirm the lab heading before reading or submitting records.

![Lab forms table, pending requirement, and submission link](assets/screenshots/lab-forms.jpg)

The captured page has a **Pending Requirement Incomplete: Chemical Safety Form** notice. That notice includes a link to the required form. It is distinct from existing submitted forms listed below it.

## Filter existing forms

Use **Type** and **State** to narrow the list. Observed form types include Biological Research Project, Chemical Safety Form, Chemicals In Animals, Incident Report Form, Pathogen Registration Form, Permission to Work Alone, and Viral Vector Registration Form.

The table shows **Form Title**, **Submitted By**, **Lab**, **Submission Date**, **Last Updated**, and **State**. Sortable headings help locate recent work. Select a form title to inspect that submission. **View Archived Forms** opens a separate history.

## Read the exact state

The state filter presents broad options such as **Awaiting Review**, **Approved**, and **Not Approved**, while individual rows can display more specific labels:

| Observed label | What to check next |
| --- | --- |
| Awaiting PI Certification | Check whether the PI certification step is outstanding |
| Awaiting EHS Review | Check with the responsible reviewing staff |
| Amended Awaiting Review | Check the amended record and its review status |
| Approved | Read the approved record and any applicable dates or conditions |
| Expired | Check whether a new submission or renewal is needed |

These labels were observed in the list; the complete transition rules were not tested. A submission timestamp or recent update is not itself an approval.

## Start a new form

1. Open the correct lab's forms list.
2. Check for a linked pending requirement before creating a duplicate.
3. Select **Submit New Form**, or the linked required form where appropriate.
4. Read the selected form's instructions and required fields.
5. Verify the lab, information, and intended submission before using its final action.

The submission entry links were verified, but the downstream selection screen, form fields, save behavior, and final submission were not inspected. Different form types can have different requirements and review steps.

For the separate home-page incident workflow, see [Safety reporting](safety-reporting.md). For biological registration and certification context, see [Biological safety](biological-safety.md).


---

# Biological safety and registrations

## Open the biological summary

Select **Bio Summary** under a lab in the sidebar, or **Bio** in the upper lab navigation. The inspected lab page is headed **Bruxner Lab Group Biologicals**.

![Biological summary, materials, and registration history](assets/screenshots/bio.jpg)

## Review the summary

The summary identifies the **Principal Investigator**, **Delegate(s)**, **Assigned Biosafety Level**, **Review Frequency**, and whether the lab **Ships Biomaterials**. A count table lists projects and biological records, including viral vector forms, pathogen forms, cell lines, tissues, plants, microbes, biological toxins, and rDNA.

In the captured example, the assigned level is BSL 2 and the review frequency is one year. These values describe this lab's record; they are not general guidance for other labs or materials.

## Navigate biological records

Observed secondary navigation includes **Biological Summary**, **Projects**, **Cell Lines**, **Tissues**, **Plants**, **Microbes**, **Biological Toxins**, and **NIH Guidelines**. The page also provides **View or Update Biological Usage Summary**.

The **Biological Materials** section lists categories in use, such as human source materials, lab animals, microorganisms, plants, toxins, recombinant or synthetic nucleotides, and viral vectors. Use those categories to identify which part of the registration needs review.

Detailed material forms, project editing, and their validation were not inspected. The existence of an update link does not establish which changes this account can certify.

## Distinguish changes, certification, and approval

The captured page warns that changes to the biological usage summary **have not been certified** and asks that the PI be notified when changes are ready for review. It provides a changes-since-date link and **Amendment Summary**.

Use those links to review changes before involving the PI. A saved change, PI certification, submission for review, and approval are separate concepts; do not treat a current record count as evidence of completed approval.

## Review registration history

The **Registration Summary** includes a **Submission** selector with **Current** and historical dates. It displays **Registration Started**, **PI Last Certified**, **Registration Approved**, **Research Last Confirmed**, and **Next Review Date**. A certification row offers **Download PDF** and **View**.

1. Choose the submission version relevant to your question.
2. Compare certification and approval information.
3. If the record is awaiting submission or shows a missing approval date, contact the PI/delegate or biosafety staff.
4. Use the lab dashboard for a broader compliance view, then return here for registration detail.

Historical version switching, PDF generation, changes review, certification, and submission were not executed. The guide documents the visible entry points and summary state.

Related: [Lab forms](forms.md), [Compliance dashboard](compliance.md), [Research resources](research-resources.md).


---

# Radiological management

## Open the lab's Rad Summary

Expand the lab section and select **Rad Summary**, or select **Rad** in the lab's upper navigation.

![Rad Summary with license, member status, authorized isotopes, and current vials](assets/screenshots/radiation.jpg)

The captured summary shows the lab for which the license is valid, license expiration, and receiving area. Check the lab identity before interpreting the inventory or authorization.

## Review people and isotope authorizations

**Lab Member Status** lists **Enabled**, **Trained**, **Name**, and **Badges**. The inspected record uses Y/N indicators for enabled and trained. They are separate columns; verify both and consult the responsible staff if a status appears wrong.

**Authorized Isotopes** shows the isotope name, maximum activity allowed, consumed activity, and remaining activity. The captured table labels maximum activity in **mCi**. Preserve the displayed units when discussing a record.

These values are application records. This guide does not establish authority to order, receive, use, or dispose of radioactive material.

## Find current vials

The summary's **Current Vials** table shows **Vial Number**, **Isotope**, **Compound**, **Ordered By**, **Date Received**, **Initial Activity**, and **Current Activity**. Vial numbers are links. The page exposes **Log Use** text and **See all Current Vials**; the navigation also includes **Current Vials**.

Open the appropriate vial record before recording any use. The log-use form, calculation rules, decay behavior, and save/confirmation flow were not inspected or tested.

## Orders and requests

The summary has a **Pending Orders** section and **View RAD Request history** links. The captured lab had no pending RAD requests. The sidebar exposes **Rad Request** as an entry point.

Order creation, supplier selection, delivery handling, approvals, and request cancellation were not inspected. Use the live form and institutional workflow when carrying out those tasks.

## Waste pickup and disposal navigation

Observed tabs include:

| Tab or link | Purpose indicated by the UI |
| --- | --- |
| Summary | Current lab overview |
| Snapshot | Separate inventory snapshot view |
| Current Vials | Vial listing |
| Waste Pickup Request | Request entry point |
| Pending Pickup Requests | Pending pickup list |
| Completed Pickup Requests | Completed pickup history |
| Sewer Disposal Records | Disposal record list |

The lab sidebar also has **Rad Waste Pickup**. The underlying request fields, disposal controls, and final actions were not exercised.

## Resolve conflicting license dates

The captured compliance dashboard and Rad Summary displayed license dates one day apart. This is recorded as a documentation observation, not a diagnosed cause. Ask radiological compliance staff to confirm the authoritative source if a date affects your work.

Related: [Compliance dashboard](compliance.md), [Equipment](equipment.md), [Important Contacts](research-resources.md).


---

# Research resources and SOPs

## Find institutional information

Expand **Research Tools** to access **Announcements**, **Document Library**, **External Links**, **Important Contacts**, and **SDS Search**. These resources complement the documents and contacts attached to a particular lab.

## Document Library

![Document Library filters and empty state](assets/screenshots/documents.jpg)

The library provides **Document Type** and **Filename/Description** filters. The filename/description control asks for **at least 3 characters**. The table has **File Name**, **File Type**, **Description**, **Date Uploaded**, and **Submitted By** headings with sorting controls.

1. Open **Research Tools → Document Library**.
2. Choose a document type if relevant.
3. Enter at least three characters of a filename or description.
4. Review the filtered table and sort as needed.

The captured library displayed **There are currently no documents to list**, and its Document Type control was disabled. No document download or upload was verified. If a document is expected, clear available filters and confirm whether it belongs in the institutional library or the lab's own Documents tab.

## SDS Search

Open **Research Tools → SDS Search**. Enter the chemical name. Expand **Advanced** to reveal **CAS Number** and **Manufacturer**. Select **Search** to request results.

![SDS search with advanced CAS and manufacturer filters](assets/screenshots/sds.jpg)

Use the chemical identifier and manufacturer to distinguish similarly named products. The home page also includes a compact SDS search field labeled **Chemical Name or CAS Number**.

The search form and advanced fields were inspected, but no SDS result, external data provider, or document retrieval was verified. If the result is ambiguous or unavailable, use your institution's designated chemical safety resources and contacts.

## Important Contacts

![Institutional compliance and emergency contact directory](assets/screenshots/contacts.jpg)

The inspected directory groups **Topic/Issue**, **Contact**, and **Phone** under sections such as **Emergency Contacts**, **Animal Resource Center**, and **EH&S**. EH&S entries distinguish biological, chemical, and radiological topics, including waste and deliveries.

Use the live directory on your institution's deployment. The screenshot contains development dataset contacts; do not use its sample numbers as a current directory. For an actual emergency, follow your local emergency procedure.

## Organizational SOPs

Expand **SOPs** and select **Organizational SOPs**.

![Organizational SOPs integration entry page](assets/screenshots/sops.jpg)

The page provides two integration links:

- **View Organizational SOPs**, pointing to `/members/protocols/?scope=public`.
- **Create Protocol**, pointing to `/members/protocols/?scope=user`.

The linked protocol system was not inspected, so this guide does not claim that its editor, revision history, approval workflow, or acknowledgements are available or working in this local environment.

## Announcements, external links, and knowledge base

The home page displays announcement previews and a **View All Announcements** link. Research Tools exposes **Announcements** and **External Links**. The home page's **Visit Knowledge Base** link opens a separate help integration.

Those entry points were observed; the full announcement list, external destination contents, and knowledge base were not reviewed. Institutional content and destination access can vary.

Related: [Labs and spaces](labs.md), [Troubleshooting](troubleshooting.md).


---

# Safety observations, incidents, and near misses

The home page provides two separate reporting entry points: **ObservNow™ Safety Concern** and **Incident or Near Miss**. The incident form states that it is for events involving injury or property damage, or events where those nearly occurred. Follow your institution's reporting guidance when selecting a workflow.

The incident page explicitly directs users needing urgent medical attention or other emergency response to contact local emergency services immediately.

## ObservNow safety observations

Select **ObservNow™ Safety Concern** on the home page to open **Submit A Safety Observation**.

![Safety observation form as rendered in the inspected environment](assets/screenshots/observnow.jpg)

The captured page exposes an observation type selector, photo upload, description area, location controls, another selector, a checkbox, and **Submit**. Its photo instructions specify **a maximum of 5 photos**, a displayed **20M** file-size limit, and `.jpeg`, `.png`, and `.gif` formats.

Some labels and selector options did not populate correctly in the inspected environment. Observation type, building, and status selectors displayed only placeholders, and the anonymous-submission checkbox lacked a visible label. This guide therefore does not assign unverified meanings to the unlabeled controls or claim that the workflow is ready to submit.

If the same incomplete form appears, reload once and contact support if the labels/options remain missing. Describe what you see rather than guessing values. No observation was entered or submitted during documentation capture.

## Incident or Near Miss

Select **Incident or Near Miss** on the home page. The page is titled **Submit an Incident Report**. Wait for the full form to appear: its heading and Submit button can render before the questions finish loading.

![Complete incident report form](assets/screenshots/incident.jpg)

## Prepare incident information

The inspected form contains these fields:

| Area | Fields and choices observed |
| --- | --- |
| Event type | Incident Report or Near Miss |
| Timing | When did this happen?; Time |
| Injury or illness | No, Yes, or Unknown |
| Initial medical treatment | None, First Aid Only, Emergency Medical Care, Doctor or Other Medical Professional Visit, or Unknown |
| Property | Whether property damage or loss occurred |
| Location | Site/Campus, Building, Space/Room, Location Specifics |
| People | Who was involved?, Supervisor Name, Any witnesses? |
| Narrative | What happened? |
| Evidence | Upload Photos |
| Reporter | Submit anonymously?; Best phone number to reach you |

The form marks required fields with an asterisk. In the captured initial state, Incident Report is selected, property damage is set to No, anonymous submission is set to No, and the date is populated. Review defaults carefully; they may not describe the event.

**Space/Room** is initially disabled until the relevant location selection is made. Available buildings and campuses belong to the institution's configuration.

## Complete and review a report

1. Select Incident Report or Near Miss to match the event.
2. Confirm the event date and time, replacing any inappropriate defaults.
3. Answer the injury, treatment, and property questions.
4. Identify the location and people involved as requested.
5. Describe what happened and add relevant photographs if appropriate.
6. Review the anonymous-submission choice and contact information.
7. Check required fields and the content before choosing **Submit**.

The visible controls and fields were inspected without entering or submitting a report. Validation messages, photo limits for this incident form, anonymity behavior, delivery, confirmation, editing, and follow-up processing remain unverified. The observation form's upload limits should not be assumed to apply to the incident form.

The page also exposes **Cancel**. Its destination was a page fragment in the inspected DOM; cancellation behavior was not tested.


---

# My account and messages

## Review your account

Expand **My Account** and select **Account Settings**. Confirm the profile name. The inspected page contains **Directory Information**, **Academic Sections**, and **Labs**.

![Account profile and associated academic sections and labs](assets/screenshots/account.jpg)

Directory fields include first name, middle initial, last name, display name, and phone number. Lab and academic-section names are links to their respective records.

The page's **Edit Profile Details** link points to `https://localhost:5301/account/profile` in this local environment. It is a separate local service. Editing was not followed or tested. If that destination is unavailable, check the profile service configuration with the development team.

## Other account navigation

Observed navigation includes **Medical Surveillance**, **Animal Contact**, **Training**, and **Messages**, with additional profile links for **Chemical Safety Forms**, **My Jobs**, **Equipment**, **My Alerts**, and **Vaccination Records**.

Those labels establish entry points only. The contents, permissions, and workflows of health-related and job-related pages were not inspected. An account-specific Animal Contact setup reminder also appears on the captured home page.

## Read messages

The home page shows a Messages block with dated subjects and **View Entire Inbox**. Select a subject to open an individual message. The sidebar also offers **My Account → Messages**.

![Messages page with filtering and sorting controls](assets/screenshots/messages.jpg)

The inspected Messages page has filters for **Subject**, **Sender**, **Recipient**, **Message Type**, **Sent After**, and **Sent Before**. Its columns are **Subject**, **Sender**, **Recipient**, **Date Sent**, and **Message Type**, with sortable headings.

The captured page displayed **There are currently no messages to list**, although the home page had recent messages. This discrepancy is recorded as an environment observation. If you see it, clear filters and try the original home-page subject link. It does not prove that the messages were deleted.

Individual message contents, read/unread behavior, attachments, composing, delivery, and deletion were not inspected or tested.

## Notifications and signing out

The header contains **Notifications** and **User menu** controls. The sidebar's My Account section exposes **Log out**. The menu contents and logout outcome were not exercised because the authenticated session was needed for capture.

Related: [Getting started](getting-started.md), [Training](training.md), [Troubleshooting](troubleshooting.md).


---

# Troubleshooting

## I cannot find a menu or action

Expand the correct sidebar section and confirm the lab. Different labs exposed different menu entries in the inspected account. Check the secondary tabs inside a lab profile as well as the sidebar. If an action remains unavailable, ask the lab administrator or compliance team whether your role and institutional configuration include it.

This guide describes the captured member account. It does not establish the menus available to system administrators, inspectors, or other roles.

## A page initially looks incomplete

Some pages load their questions or records after the outer layout. The incident page initially showed its heading and buttons before its full form appeared. Allow the page to finish rendering before deciding that fields are missing. If the form remains incomplete after a reload, report the page address and visible behavior to support.

## A table is empty

Clear filters, check date ranges, confirm the lab or person, and look for pagination. Distinguish these cases:

| Screen | Observed condition |
| --- | --- |
| Document Library | No documents listed; the Document Type control was disabled |
| Messages | No messages listed despite home-page message subjects |
| Classroom sessions | An explicit message that no sessions were scheduled, with course manager contact details |
| Self inspection summary | No findings in the recent 18-month window, while older inspections were present in history |

The cause of the first two empty states was not diagnosed. They should not be presented as proof that the institution has no documents or messages.

## Training is overdue but I have a certificate

Compare the exact course, completion date, expiration date, and current requirement. Use **My Training → `<All>`** to inspect history, then check the current required course entry. Related titles or different delivery formats may be separate records. Contact the course manager if the recorded history is wrong.

## The ObservNow form has blank labels or no options

The captured form had placeholder-only selectors and incomplete visible labels. Reload once. If the problem persists, contact the application's support/development team. Do not guess the meaning of unlabeled controls or submit an incomplete observation.

## Profile editing does not open

The local **Edit Profile Details** link targets `https://localhost:5301/account/profile`. That requires a separate service and appropriate local configuration. The service was not tested as part of this documentation task. Ask the development team to verify the destination and its availability.

## The SOP or knowledge-base destination is unavailable

Those features use linked integrations. The SOP gateway points to `/members/protocols/`; the knowledge-base link uses a separate help entry point. Verify the destination service and permissions with support. Their downstream behavior is outside this capture's verified scope.

## Summary dates or counts disagree

Open the underlying record and compare context, date window, and filters. The captured dashboard and Rad Summary differed by one day on a license date. The inbox and home-page message block also disagreed. Record both locations when asking staff to investigate; the capture does not establish a root cause.

## An inspection says Finalized but findings remain

Read **Resolved Findings** separately from **Status**. The captured log included a finalized inspection with unresolved findings. Open the inspection and ask the responsible staff about follow-up. Do not use status alone as evidence that all findings were resolved.

## Documentation site problems

- **Port already in use:** choose another `PORT`; see [Hosting and maintenance](README.md).
- **Module not found:** run `npm ci` inside `documentation`.
- **Guide returns 404:** check the Markdown filename and its capitalization, especially on Linux.
- **Screenshot missing:** check that its path exists under `assets/screenshots` and that the assets folder was deployed.
- **Search finds nothing:** every word must occur in the same page. Try fewer terms or a shorter spelling.
- **Changes do not appear:** reload the page. Markdown is read on each request, so a server restart is not needed for prose edits.


---

# Scope and verification

## Source and date

This documentation was prepared from read-only exploration of the authenticated SciShield local application on **12 November 2026**. The observed footer version is **v3.10.3.20261103.2621**. The application base URL was `http://earth.127.0.0.1.nip.io:8083`.

The account identifies itself as Twila T Burris and has Bruxner Lab Group, Demuth Lab, and Jared Lab menu sections. Most lab-level examples use Bruxner Lab Group. Numeric record IDs, names, contact information, dates, and counts are local dataset examples.

## Inspected screens

| Screen | Inspected route | Screenshot |
| --- | --- | --- |
| Home | `/frontpage_panel` | [Home](assets/screenshots/home.jpg) |
| Lab profile | `/raft/group_page/19939/view` | [Profile](assets/screenshots/lab-profile.jpg) |
| Compliance dashboard | `/raft/group_page/19939/lab_compliance` | [Dashboard](assets/screenshots/compliance.jpg) |
| Members | `/raft/group_page/19939/users` | [Members](assets/screenshots/members.jpg) |
| Spaces | `/raft/group_page/19939/group-spaces` | [Spaces](assets/screenshots/spaces.jpg) |
| Requirements | `/node/19939/requirements` | [Requirements](assets/screenshots/requirements.jpg) |
| My Training | `/raft/training/trainingRecords` | [Training](assets/screenshots/training.jpg) |
| Course Directory | `/raft/training/courses` | [Courses](assets/screenshots/courses.jpg) |
| Classroom sessions | `/node/53168/sessions` | [Sessions](assets/screenshots/course-sessions.jpg) |
| My Equipment | `/raft/equipment/my_equipment` | [Equipment](assets/screenshots/equipment.jpg) |
| Equipment detail | `/node/151105` | [Asset detail](assets/screenshots/equipment-detail.jpg) |
| Lab Inspection Log | `/node/19939/view/lab_inspections` | [Inspections](assets/screenshots/lab-inspections.jpg) |
| Self Inspection Log | `/raft/group_page/19939/self_inspections` | [Self inspections](assets/screenshots/self-inspections.jpg) |
| Lab forms | `/raft/group_page/19939/forms` | [Forms](assets/screenshots/lab-forms.jpg) |
| Biological summary | `/raft/group_page/19939/biologicals` | [Biologicals](assets/screenshots/bio.jpg) |
| Rad Summary | `/raft/group_page/19939/radTab` | [Radiological](assets/screenshots/radiation.jpg) |
| Organizational SOPs gateway | `/raft/scisure/sops/organizational` | [SOPs](assets/screenshots/sops.jpg) |
| Document Library | `/raft/research_tools/document_library` | [Library](assets/screenshots/documents.jpg) |
| SDS Search, including Advanced | `/raft/research_tools/SDS` | [SDS](assets/screenshots/sds.jpg) |
| Important Contacts | `/raft/research_tools/important_contacts` | [Contacts](assets/screenshots/contacts.jpg) |
| Account profile | `/raft/my_account/profile` | [Account](assets/screenshots/account.jpg) |
| Messages | `/raft/my_account/messaging` | [Messages](assets/screenshots/messages.jpg) |
| ObservNow | `/ObservNow` | [Observation](assets/screenshots/observnow.jpg) |
| Incident form | `/raft/incident-management/incident-report/create` | [Incident](assets/screenshots/incident.jpg) |

Some routes redirect to canonical `/node/…` or `/user/…` pages. The table records the inspected entry route, not a portability guarantee.

## What verification means here

Screen headings, visible data columns, labels, navigation destinations, filters, empty states, and 24 application screenshots were inspected. Steps leading to untested actions are explicitly described as entry points or intended next steps in their guide.

No reports, registrations, messages, enrollments, certifications, orders, inventory changes, permissions, profile changes, uploads, or deletions were submitted. Successful end-to-end mutation workflows are therefore not claimed.

## Unverified areas

The documentation does not claim complete coverage of administrator or inspector roles, chemical inventory management, application source architecture, login/SSO, account recovery, course assessments, scheduled classroom registration, inspection detail/finding resolution, form creation fields, biological material editing, PI certification, radiological order/use/disposal forms, SOP editing, knowledge-base contents, health questionnaires, or vaccination records.

Several of those areas have visible links, documented in context. A visible link verifies an entry point; it does not verify the downstream workflow.

## Observed environment issues

- ObservNow selectors and labels did not fully populate.
- The inbox displayed an empty table while the home page showed messages.
- The Document Library was empty and its document type selector was disabled.
- Profile editing linked to a separate local HTTPS service on port 5301.
- A radioactive license date differed by one day between summary screens.
- A finalized inspection could still show unresolved findings.

These observations are not root-cause diagnoses. See [Troubleshooting](troubleshooting.md).

## Screenshots and publication

Screenshots contain the records visible in the provided authenticated development session, including names and contact information. The Node server defaults to the loopback interface. Before hosting for an audience, review the examples and apply the access controls appropriate for that audience.

The raw capture evidence JSON is retained locally for maintainers; the documentation server does not expose it. It contains extracted screen text and links, without session cookies or authentication tokens.


---

# Hosting and maintenance

This folder is a self-contained Node.js documentation site. Markdown files are the canonical content. The server renders HTML, serves screenshots, and offers plain Markdown and JSON entry points for AI agents.

## Run locally

Requirements: **Node.js 22 or newer** and npm.

```powershell
cd C:\git_repos\scishield\documentation
npm ci
npm start
```

Open `http://127.0.0.1:4173`. The application itself does not need to be running to read these guides and screenshots.

On macOS/Linux, change into the equivalent checkout's `documentation` folder and use the same npm commands. The server resolves files relative to its own location, independently of the launch directory.

## Configure host and port

The default listener is `127.0.0.1:4173`. Set `HOST` and `PORT` to change it.

```powershell
$env:HOST = '127.0.0.1'
$env:PORT = '4180'
npm start
```

```bash
HOST=127.0.0.1 PORT=4180 npm start
```

The site is read-only and has no application login. It does not reuse the SciShield session or query live application data. Its screenshots include the captured dataset; use your webserver's authentication/access controls when hosting them for a restricted audience.

## Host behind a webserver

Copy the folder to a server with Node.js, run `npm ci --omit=dev`, and run `node server.mjs` under your preferred service manager. Keep the Node listener on loopback when a reverse proxy runs on the same machine.

Example nginx location inside your existing HTTPS server block:

```nginx
location / {
    proxy_pass http://127.0.0.1:4173;
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;
}
```

The site uses root-relative URLs. Host it at the root of a dedicated hostname, for example `docs.example.org/`. Mounting it under a subpath such as `/help/` requires adapting the URL generation and asset links. Configure TLS and any required authentication at the reverse proxy.

There is no static HTML build step. A plain static file host alone will serve Markdown but will not provide this HTML renderer or search endpoints.

## Routes for readers and agents

| Route | Response |
| --- | --- |
| `/` | HTML application guide |
| `/docs/training` | HTML rendering of `training.md` |
| `/training.md` | Unwrapped UTF-8 Markdown with `text/markdown` content type |
| `/llms.txt` | Plain-text index linking every Markdown guide |
| `/api/pages` | JSON page titles, HTML URLs, and Markdown URLs |
| `/all.md` | All Markdown guides concatenated |
| `/search?q=training%20overdue` | Server-rendered HTML search results |
| `/api/search?q=training%20overdue` | JSON results with title, slug, and excerpt |
| `/assets/screenshots/home.jpg` | Original captured image |

All guide and search routes work without client-side JavaScript. The small browser script only preserves the search input value. Every rendered guide has a direct **View Markdown** link, and its links to other guides point to HTML. The original Markdown keeps its ordinary relative `.md` links for repository and agent reading.

## Search specification

Search trims the query, splits it on Unicode whitespace, lowercases and deduplicates the terms, and requires every term to occur in a single page's complete Markdown source. Matching is literal substring matching. Terms can appear in any order and in different sections of a page.

Conceptually, the predicate is `contains(word1) AND contains(word2)`. It is equivalent to the requested `LIKE '%word1%' AND LIKE '%word2%'` behavior for ordinary terms, without SQL wildcard interpretation. Percent signs, underscores, punctuation, and quotes are literal. Search does not use a database.

Results follow the guide navigation order. Blank queries return no results. Unknown words return an explicit no-results state. Screenshot pixels and live application data are not indexed.

## Update content

1. Edit an existing root-level `.md` file or add a new one with a single level-one title.
2. Link to another guide with a relative Markdown path, for example `[Training](training.md)`.
3. Put screenshots under `assets/screenshots` and use a relative image reference, for example `![Home page](assets/screenshots/home.jpg)`.
4. Review the image for the intended audience and provide written steps alongside it.
5. Update [Scope and verification](coverage.md) when adding verified screens or changing limits.
6. Reload the guide. Content and search read Markdown at request time.

New `.md` files automatically appear in navigation, search, `/api/pages`, `/llms.txt`, and `/all.md`. The ordering list in `server.mjs` places core guides first; additional guides follow alphabetically. Screenshot files are served as local assets; no CDN or external font service is required.

`capture-evidence.json` is maintainer evidence from the browser exploration. It is not a guide and is not exposed by the Node server. Refresh it only when performing another documentation capture.

## Verify changes

```bash
npm test
```

Tests cover AND search with reversed terms, case and whitespace, literal special characters, no-result queries, raw Markdown and AI indexes, HTML rendering, source links, screenshots, missing routes, request methods, path handling, sanitization, and local Markdown/image links.

The server serves only the guide routes, indexes, and approved assets. Raw HTML in Markdown is sanitized, and a Content Security Policy restricts executable assets to this origin. Dependencies are recorded in `package-lock.json`; use `npm ci` for reproducible installation.