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

# Product families

> Add, edit and archive the product lines you ship. SBOMs, API tokens, matches, support periods and your plan all follow the product family.

<Info>
  **Plans:** Every plan; how many families can be active depends on the plan. **Who:** owners and admins add, edit, archive and restore families; every member can see them.
</Info>

A product family is a product line you ship, such as "Gateway G3". Pharus tracks SBOMs, vulnerability matches and incidents per family, and it prices plans per product family, never per seat.

## What belongs to a product family

| What | Where you find it |
| - | - |
| SBOMs and their components | **SBOMs**, one card per family |
| API tokens for pipelines | **Settings → API tokens**. Each token uploads SBOMs to one family. |
| Vulnerability matches and incidents | **Vulnerabilities** and **Incidents**, filtered or labelled by family |
| Member states and reporting route | The family's page under **Settings → Product families** |
| Support periods per release line | The family's page, in the **Support period** card |
| Technical documentation (Annex VII) | **Reports → Technical documentation (Annex VII)**, one per family. Core and Plus, the free trial, or an add-on on Starter. |
| CSAF advisories | Each advisory names the family as the product, with the versions from its SBOMs |

The family's page also shows its **Current version**, the number of **Components** and when the **Last SBOM** arrived. Pharus sets the current version for you: it is the highest product version among the SBOMs the family has received. The component count is the number of distinct components across the family's active SBOMs.

## Plan limits and extra families

Only active families count. Archived families don't.

| Plan | Product families included | Extra families you can add |
| - | - | - |
| Starter | 1 | Up to 2, at 1 900 NOK / month each, excl. VAT |
| Core | 5 | Up to 5, at 1 500 NOK / month each, excl. VAT |
| Plus | No limit | None needed |
| Free trial | No limit | None needed |

On yearly billing an extra family costs ten months. The workspace owner adds and removes extra families under **Settings → Billing**, in the **Extra product families** card. Extras are billed with the plan.

The subtitle on **Settings → Product families** shows how many families are in use and how many your plan covers. When the plan is full, **Add product family** is disabled and the page says what to do, for example: "Your Starter plan covers 1 product family. Add an extra one or change plan under Settings → Billing."

<Note>
  The trial has no limit on product families. To choose a plan when it ends, your active families must fit in that plan with its extras. If they don't, archive some first. See [billing](/workspace/billing).
</Note>

## Add a product family

<Steps>
  <Step title="Open the families page">
    Go to **Settings → Product families** and select **Add product family**.
  </Step>

  <Step title="Name the family">
    Enter a **Name**, up to 80 characters, and an optional **Description**. The name must differ from your other active families; Pharus ignores upper and lower case when it compares them.
  </Step>

  <Step title="Choose the member states">
    Tick the **Member states** where the product is made available: any EU state, Iceland, Liechtenstein or Norway. Use **Select all EU states** or **Clear selection** to go faster. The member states go into the early warning.
  </Step>

  <Step title="Save">
    Select **Add product family**. Pharus opens the new family's page, where you can set its reporting route and support periods.
  </Step>
</Steps>

Next, send the family its first SBOM: [upload one or connect a pipeline](/monitoring/sboms). A pipeline needs an [API token](/api-reference/introduction) for the family.

## Edit a product family

Open the family from **Settings → Product families**. Its page has these cards:

* **Details**: **Name**, **Description** and **Made available in the EU**. Turn the switch off for a product that isn't on the EU market: CRA reporting applies to products on the EU market, and the families list then shows "Not on the EU market".
* **Member states**: where the product is made available.
* **Reporting route**: where the family's reports go under CRA Art. 14(7). If your company is established in an EU state, every product family reports to the CSIRT there. Otherwise a family can use **Inherit company route** or set its own route. See [routing](/incidents/routing).
* **Support period**: the end of security updates for each release line. See [support periods](/monitoring/support-periods).

Select **Save product family** to keep your changes to the details, member states and route.

The families list shows each active family with its **Version**, **Components**, **Last SBOM**, **Security updates**, **Reports to** and **Member states**.

## Archive a product family

Archive a family you no longer ship, or to make room on your plan. You can't delete a product family.

<Steps>
  <Step title="Open the family">
    Go to **Settings → Product families** and open the family.
  </Step>

  <Step title="Archive it">
    At the bottom of the page, select **Archive product family**, then **Archive family** to confirm.
  </Step>
</Steps>

An archived family:

* stops counting towards your plan and is hidden from pickers;
* keeps its SBOMs, matches, incidents and audit trail;
* is no longer matched against vulnerabilities, and its matches leave the **Vulnerabilities** list (a vulnerability's own page still shows them, marked "Archived family");
* drops off the **SBOMs** page and the **Settings → API tokens** list, and its tokens stop working: pipelines get 401;
* keeps its technical documentation readable and downloadable, but not editable.

Archived families are listed under **Archived** at the bottom of **Settings → Product families**.

<Note>
  Archiving also works while the workspace is read-only, so you can shrink to fit a smaller plan. Adding, editing and restoring families need an active trial or subscription.
</Note>

## Restore a product family

Open the family under **Archived** and select **Restore product family**. The family counts towards your plan again, so the plan needs room for it, and its name must not clash with an active family. Its API tokens work again unless they have expired or been revoked.

## Related

<CardGroup cols={2}>
  <Card title="SBOMs" icon="package" href="/monitoring/sboms" />

  <Card title="Support periods" icon="calendar-clock" href="/monitoring/support-periods" />

  <Card title="API tokens" icon="key-round" href="/api-reference/introduction" />

  <Card title="Billing" icon="credit-card" href="/workspace/billing" />
</CardGroup>


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