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

# Products

> Organising multi-product engineering programs

<style>
  {`
      p, li {
        text-align: justify;
        text-justify: inter-word;
      }
    `}
</style>

## Why products exist

A real automotive program is rarely a single product. A typical Tier-1
supplier engagement is a **program** (e.g. "Volvo Powertrain Platform 2027")
containing **5–15 distinct products** — Battery ECU, Inverter, BMS, Charger,
DC-DC converter, and so on. Each product has its own complete V-Model
chain: its own requirements, its own architecture, its own tests. They
need to be tracked independently.

Conformly's products feature is the answer. A product is a discrete
engineering item inside a workspace, with its own:

* ASIL classification (QM, A, B, C, or D — from ISO 26262)
* Document set (work products are tagged with their product on upload)
* Findings (each gap inherits the product from the document it came from)
* Audit-readiness score
* V-Model traceability chain

If your program has just one product, you can ignore this feature
entirely — Conformly works perfectly without any products defined. The
multi-product machinery only kicks in when you create the first product.

## Creating a product

<Steps>
  <Step title="Open Workspaces and expand a workspace">
    Sidebar → Workspaces → click the chevron on a workspace row.
  </Step>

  <Step title="Find the Products panel">
    It's between the Members panel and the Activity feed.
  </Step>

  <Step title="Click 'New product'">
    A small inline form appears.
  </Step>

  <Step title="Enter name, description (optional), and ASIL">
    Pick a name your engineers will recognise. The ASIL field is optional
    but strongly recommended for safety-relevant products — it drives
    the safety-aware severity logic in the AI evaluation.
  </Step>

  <Step title="Click Create">
    The product appears immediately in the panel and is ready for documents.
  </Step>
</Steps>

You need at least Editor role on the workspace to create a product.
Viewers see the panel but get no Create button.

## Tagging documents with a product

Once you have at least one product in a workspace, the
[New Analysis](/user-guide/uploading) page automatically shows a
**"Tag uploads with product"** picker above the file dropzone. Pick a
product (or leave it as "Unassigned" if you don't yet know), then drag
your files. Every uploaded document gets the selected product attached.

Documents tagged with a product produce findings tagged with the same
product, so when you open Findings → filter by product → you see only
the gaps for that specific component.

If you forgot to tag some documents earlier, that's fine — they show
up in an "Unassigned" bucket in Audit Readiness. You can also delete
the document and re-upload it with the right tag. (Re-tagging in place
is a planned feature.)

## ASIL classification

The ASIL field on a product expresses its required safety integrity
level under ISO 26262. The five values are:

| ASIL   | Meaning                                            | When to use it                                                                                      |
| ------ | -------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| **QM** | Quality Management — no safety integrity required. | Non-safety components like infotainment, comfort features.                                          |
| **A**  | Lowest safety level.                               | Components whose failure could cause minor injury.                                                  |
| **B**  |                                                    | Components whose failure could cause moderate injury.                                               |
| **C**  |                                                    | Components whose failure could cause severe but survivable injury.                                  |
| **D**  | Highest safety level.                              | Components whose failure could cause fatal injury. Examples: brake controllers, BMS, steering ECUs. |

Conformly uses ASIL to escalate severity on safety-relevant findings.
A traceability gap on an ASIL D component is automatically critical,
even if the same gap on a QM component would be merely high. This
mirrors how a real ISO 26262 audit works.

## Editing or deleting a product

In the same Products panel, click the pencil icon to rename or change
ASIL. Click the trash icon to delete the product. **Deleting a product
does not delete its documents** — they revert to "Unassigned" status,
which keeps the data safe.

You need Admin role or above to delete a product.

## How this scales

A workspace with one or two products renders identically to a workspace
with no products defined — you just see one or two collapsible product
chains in Audit Readiness instead of a single workspace-wide chain.

A workspace with 12 products renders as 12 collapsible chains, sorted
worst-first. The first one is expanded by default; the others are
one-click expand. Conformly's traceability math runs once per product,
all batched in a single API round-trip, so the page stays responsive.

For programs much larger than that (50+ products in one workspace),
the system still works correctly, but the visual scan becomes hard.
That's the threshold at which the [Portfolio](/user-guide/portfolio) view
starts to make more sense — split the program into multiple workspaces,
one per major subsystem.