Unit Explorer
Last updated on October 17, 2026
The Unit Explorer is the entry point into every Unit you have ever produced. Filter by part number, revision, batch, status, or any unit-metadata key; open a row to see the unit's lifetime: every run, every attempt, every measurement.
Open it from Inventory → Units.
Columns
Click the sliders icon at the right end of the table header to choose which columns the table shows. Columns are grouped like the filter sidebar, and your choice is saved in your browser for each organization.
| Group | Columns |
|---|---|
| Unit | Serial number, Part number, Part name, Revision, Batch, Sample, Sub-units, Parent, Run count, Created at, Created by. |
| Run | Last procedure, Last run at, Last outcome. |
| Metadata | One column per unit metadata key. |
Click the arrow in a column header to sort by that column. Every column sorts except Sub-units, which lists several units per row. Units with no value in the sorted column always come last. A metadata key that holds numbers on some units and text on others sorts numbers first, then text, then true and false values.
Filters
The filter bar combines structured filters with free-text search across serial numbers, part numbers, and metadata values.
- Part number and revision. Compare units across redesigns.
- Batch. Slice a single production cohort.
- Status. Filter to passing, failing, or never-tested units.
- Sample type. Include or exclude golden and failing reference samples.
- Contains sub-unit. Keep the units that have a sub-unit whose serial number contains the text.
- Date range. Filter by first run, last run, or unit creation date.
- Unit metadata. Any key-value pair you attach to units at creation or via the API.
Metadata
Every unit carries a free-form metadata object you can write at creation through the SDK, the REST API, or the CLI. Keys are filterable in the toolbar, exportable as columns, and matchable in workflow triggers. See Unit metadata for the schema.
Saved views
Save a filter combination as a view so the next time you open the explorer it lands on the right slice. Views live at the organization level, so anyone on your team can open the same slice from the Views menu.
Export
The Export button writes the current unit set to a file. Pick the rows and the format from the dropdown.
- CSV. Flat, one row per unit, with columns for serial number, part, revision, batch, status, last run, sample type, and metadata.
- JSON. Nested, one object per unit with the same fields plus the raw record.
- Visible vs selected. Export every visible row, or check rows in the table and export only the selection.
- Filename.
tofupilot-units-<timestamp>.<ext>so multiple exports stay distinct.
Exports honor access group scope and role permissions, so you only export the rows you can see in the table.
Permissions
The Unit Explorer respects the dashboard access model:
| Role | What they see |
|---|---|
| Owner, Admin, Developer | Every unit in the organization. |
| Viewer | Units tested on stations within their access group scope. |
| Operator | No access. |
See also
How is this guide?
Log Explorer
Search every log line across every run on TofuPilot, filter by level, source, run, station, or part, and jump from a log entry to the run that produced it.
Run Analytics
Learn how TofuPilot computes first-pass, second-pass, third-pass, and last-pass yield per unit per day from every run you upload.