A structural element that organizes features within a product. Components group related features together to create a logical product structure.
What is a Component?
A Component is a folder that organizes your features within a product. Components are broad buckets for categorizing your different feature ideas — for example, "Mobile App", "Billing", or "Onboarding".
Components should be defined around stable concepts that rarely change — user needs, product areas, or technical domains — rather than short-term projects or initiatives. Since components are the primary way of organizing features, they should help you and your colleagues gain a holistic view of your product.
In the Productboard UI, components can also contain subcomponents for additional structure. The API treats subcomponents as components with a parent component relationship.
When to use it
- Organizing features — Group features by product area, team ownership, or functional domain.
- Building product structure — When setting up a workspace programmatically, create components after products and before features.
- Area-based reporting — Query components to break down roadmap progress or feedback volume by product area.
- Team alignment — Map components to the teams responsible for each area of the product.
Hierarchy
Product
└─ Component ← you are here
└─ Feature
└─ SubfeatureA component belongs to exactly one product (parent). It can contain one or more features as children.
Key fields
| Field | Description |
|---|---|
name | Display name of the component |
description | Rich-text description of what this area covers |
status | Current status |
owner | The member responsible for this component |
archived | Whether the component has been archived |
Field availability depends on your workspace configuration. Use the Configuration endpoint to discover which fields are available for the component type in your workspace.
Relationships
Features support several relationship types:
| Relationship | Description |
|---|---|
parent | The product or component this component belongs to |
When creating a component, you must specify a parent product using a relationship.
Related objects
- Product — parent of a component
- Feature — child of a component
- Subfeature — grandchild, nested under features