Part Documents

A reviewer opens a 40-page catalog cut sheet and flips pages looking for your model. Attach the datasheet to the part once, and every compiled package ships with your catalog number highlighted right on the sheet.

Attach a document

On the part page, the Documents section is one table with a row for each role: Datasheet, Manual, Warranty, and Other when the part has one. Drop PDFs on a role's row to add them as that role, or open Add document to upload a datasheet, a manual or a warranty, or Link from your library to reuse a file already in your Document Library. An empty role shows a drop zone of its own: drag files onto it or browse files. View opens the file in a pane beside the table on a wide screen, with Open, Download, Full screen, Annotate and Unlink, and in the preview window on a narrow one. Uploading the exact file you already have lands on the existing library entry instead of creating a copy. When a new upload merely reads the same as an existing document (a vendor re-download, typically), a Possible duplicate notice shows what it matched, lets you open both, and offers to link this part to the existing file instead, or keep both.

Highlights: your catalog number, found and checked

When a datasheet is attached, the pages are scanned for the part's catalog number and each match becomes a highlight. From the datasheet's card under its row you can go further:

1. Analyze datasheet reads the pages to find the ones relevant to this part, which is what drives Relevant Pages Only packages.
2. Verify highlights double-checks every found highlight against the page and rejects false positives, each with a written reason.
3. Review highlights opens the evidence list: every highlight with its page, the matched text, and its verdict. Reject a bad one or restore a rejected one; a rejected highlight draws no mark and pulls no page.

When a package compiles, confirmed highlights are drawn on the datasheet, so the reviewer's eye lands on your model immediately. Every highlighted page opens with a legend band naming the part number and tags each highlight marks. When several parts share one datasheet, each part gets its own color in that legend, and highlights two parts share are drawn gray. The vendor page is scaled slightly to sit below the band, so nothing on it is covered. See Compile a submittal.

Always full sheet

By default, a submittal scoped to Relevant Pages Only ships just the pages that carry highlights. Check Always full sheet on a document to ship it complete every time, highlights still drawn. It's a per-document setting; see Choose equipment scope for how scope is set per submittal.

Annotate by hand

Annotate opens the markup editor, where you highlight, note, or draw directly on the document. Manual marks live with the part and appear in every submittal and O&M manual that contains it.

Select a mark to restyle or delete it from the bar just above it; the colors there are named, and the color menu in the toolbar picks the next highlight's color. Arrow keys move the selected mark, and Cmd or Ctrl+Z undoes. Every mark is also a row under Marks, which you can reach from the keyboard.

When found highlights are waiting on a verdict, the editor opens Marks on them and counts them beside it, for example 2 of 5 to check. Select one, or press N, to see its source with Confirm and Reject above it. C and R do the same and move on to the next. Checked ones fold into Checked, where a rejected one can be restored.

Redact, in the toolbar, deletes an area from the document instead of marking it. What sits under the box is removed when the document compiles, for every part that links it, not just this one. As compiled switches the editor to the document with its redactions applied. See the Document Library for more.

A shared document notes how many other parts link to it. Its category and Always Full Sheet setting live on the file itself, so changing them from the Document Library warns you first with the affected counts.