Managing Project Components
Learn how to create, edit, and organize project components to structure large projects into meaningful domains and subsystems.
Last updated: February 23, 2026Managing Project Components
Project Components help you organize large projects into meaningful domains or subsystems. Components sit between Projects and PRDs in the hierarchy, making it easier to track and report on related work.
What are Components?
A Component represents a distinct area or module within your project. For example:
- User Authentication - Login, registration, password reset
- Billing & Payments - Subscriptions, invoices, payment methods
- API Gateway - REST endpoints, rate limiting, authentication
- Admin Dashboard - User management, analytics, settings
Components can be nested to create hierarchies. For instance, you might have a "Backend" component with child components for "API" and "Database".
Creating a Component
From the Project Settings
Best Practices for Components
- Keep it focused: Each component should represent a single domain or subsystem
- Use clear names: Choose names that make sense to your whole team
- Assign owners: Having a clear owner improves accountability
- Don't over-structure: Start with a few key components and add more as needed
Editing Components
To update a component:
You can change:
- Name and description
- Parent component (to restructure the hierarchy)
- Owner assignment
- Status (active, deprecated, archived)
Archiving Components
When a component is no longer active but you want to preserve its history:
Archived components:
- Are hidden from most views by default
- Cannot have new PRDs or tasks assigned
- Preserve all historical data
- Can be restored if needed
Restoring Archived Components
Component Permissions
| Action | Viewer | Member | Admin | Owner |
|---|---|---|---|---|
| View components | ✓ | ✓ | ✓ | ✓ |
| Assign to PRD/Task | ✓ | ✓ | ✓ | |
| Create components | ✓ | ✓ | ||
| Edit components | Own | ✓ | ✓ | |
| Archive/restore | ✓ | ✓ | ||
| Delete components | ✓ |
Members can edit components they own. Admins and Owners can edit any component.
Tips for Organizing Components
Starting a New Project
Large Projects
For complex projects, consider:
- Using parent-child relationships to group related components
- Having a "Core" or "Shared" component for cross-cutting concerns
- Creating an "Infrastructure" component for DevOps-related work
Microservices Architecture
If you're building microservices:
- Create a component for each service
- Use a "Gateway" or "API" component for shared interface work
- Consider a "Platform" component for shared infrastructure
See Also
- Component Progress Views - Track delivery by component
- Assigning PRDs to Components - Link work to components