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

# Organizing Work

> Deep dive into projects, workspaces, and portfolio view — how to structure work across your organization

# Organizing Work

thig.ai gives you three levels of organization for your PRD work. This page explains when and how to use each one.

## The Three Levels

```mermaid theme={null}
graph TD
    subgraph "Level 3: Portfolio View"
        PROD1["🏗️ Product: Mobile App v3"]
        FEAT1["Feature: Push Notifications"]
        FEAT2["Feature: Offline Mode"]
        FEAT3["Feature: Biometric Auth"]
        PROD1 --> FEAT1
        PROD1 --> FEAT2
        PROD1 --> FEAT3
    end

    subgraph "Level 2: Team Workspaces"
        WS1["👥 Mobile Team"]
        WS2["👥 Platform Team"]
    end

    subgraph "Level 1: Projects"
        P1["📁 Project A"]
        P2["📁 Project B"]
        P3["📁 Project C"]
        P4["📁 Project D"]
    end

    WS1 -.->|"groups"| P1
    WS1 -.->|"groups"| P2
    WS2 -.->|"groups"| P3
    WS2 -.->|"groups"| P4

    style PROD1 fill:#10B981,color:#fff
    style WS1 fill:#059669,color:#fff
    style WS2 fill:#059669,color:#fff
```

***

## Level 1: Projects

A **project** is the fundamental unit — one project = one PRD.

### Project Lifecycle

```mermaid theme={null}
flowchart LR
    DRAFT["Draft"] --> IP["In Progress"]
    IP --> READY["Ready for PRD"]
    READY --> REVIEW["In Review"]
    REVIEW --> APPROVED["Approved"]
    APPROVED --> COMPLETE["Completed"]

    DRAFT -.-> ARCHIVED["Archived"]
    IP -.-> ARCHIVED
    READY -.-> ARCHIVED
    REVIEW -.-> ARCHIVED

    style DRAFT fill:#6B7280,color:#fff
    style IP fill:#3B82F6,color:#fff
    style READY fill:#F59E0B,color:#fff
    style REVIEW fill:#8B5CF6,color:#fff
    style APPROVED fill:#10B981,color:#fff
    style COMPLETE fill:#059669,color:#fff
    style ARCHIVED fill:#9CA3AF,color:#fff
```

| Status            | Meaning                                 |
| ----------------- | --------------------------------------- |
| **Draft**         | Just created, gathering requirements    |
| **In Progress**   | Actively being worked on                |
| **Ready for PRD** | Enough context to generate the document |
| **In Review**     | PRD generated, stakeholders reviewing   |
| **Approved**      | Stakeholders signed off                 |
| **Completed**     | Done — archived for reference           |
| **Archived**      | No longer active                        |

### Project Types

Every project has a type:

| Type                   | Purpose                                 | When to use                              |
| ---------------------- | --------------------------------------- | ---------------------------------------- |
| **Standard** (default) | A single feature or product spec        | Most projects                            |
| **Product**            | A parent container for related features | When you have a multi-feature initiative |

Product projects don't contain a PRD themselves — they serve as the container that groups sub-feature projects in Portfolio view.

### What's Inside a Project

Each project contains:

* **AI conversation** — chat history with gathered requirements
* **PRD document** — the generated document with version history
* **Files** — uploaded documents (PDF, DOCX, TXT) and knowledge base entries
* **Comments** — threaded discussions anchored to PRD sections
* **Stakeholder views** — AI-generated perspective documents
* **Activity feed** — timeline of all events
* **Status history** — timeline of status changes with notes

***

## Level 2: Team Workspaces

Workspaces group **people and projects** by team, squad, or department.

### What Workspaces Do

<CardGroup cols={2}>
  <Card title="What they do" icon="check">
    * Group related projects together
    * Show which members work on what
    * Filter portfolio view by team
    * Provide workspace-level KB context
  </Card>

  <Card title="What they don't do" icon="xmark">
    * Create data silos or access restrictions
    * Change anyone's permissions or role
    * Hide projects from other org members
    * Limit who can edit what
  </Card>
</CardGroup>

<Warning>
  Workspaces are **organizational**, not **security** boundaries. All org members can still access all projects based on their role (Owner/Admin/Member/Viewer). If you need to restrict access, use organization roles instead.
</Warning>

### Setting Up Workspaces

<Steps>
  <Step title="Create the workspace">
    Go to **Teams** (`/admin/teams`) → **Create Team**. Give it a name, optional description, and color.
  </Step>

  <Step title="Add members">
    From the workspace detail page, add existing org members. This indicates who's part of this team.
  </Step>

  <Step title="Assign projects">
    From the project's action menu, select **Assign to Workspace** and pick the workspace. Or add projects from the workspace detail page.
  </Step>

  <Step title="Filter views">
    On the Projects page or Portfolio view, filter by workspace to see only that team's work.
  </Step>
</Steps>

### Example Setup

| Workspace         | Members                               | Projects                                         |
| ----------------- | ------------------------------------- | ------------------------------------------------ |
| **Mobile Team**   | Alice (PM), Bob (Dev), Carol (Design) | Push Notifications, Offline Mode, Biometric Auth |
| **Platform Team** | Dave (PM), Eve (Dev)                  | API Rate Limiting, Admin Dashboard               |
| **Growth Team**   | Frank (PM), Grace (Marketing)         | Onboarding Overhaul, Referral System             |

***

## Level 3: Portfolio View

Portfolio view shows your projects in a **product hierarchy** — products with their sub-features.

### How It Looks

```
📊 Portfolio View
│
├── 🏗️ Mobile App v3  [Product]  ──── 3 features, 67% complete
│   ├── 📁 Push Notifications      In Review    ████████░░ 80%
│   ├── 📁 Offline Mode            In Progress  ████░░░░░░ 40%
│   └── 📁 Biometric Auth          Completed    ██████████ 100%
│
├── 🏗️ Admin Dashboard Redesign  [Product]  ──── 2 features, 25% complete
│   ├── 📁 Analytics Overhaul      Draft        ██░░░░░░░░ 20%
│   └── 📁 Role-Based Views        In Progress  ███░░░░░░░ 30%
│
└── Standalone Projects
    ├── 📁 Quick Auth Fix           Completed
    └── 📁 API Rate Limiting        In Review
```

### Setting Up a Product Hierarchy

<Steps>
  <Step title="Create the product project">
    Create a new project and set its type to **Product**. Give it the name of the initiative (e.g., "Mobile App v3").
  </Step>

  <Step title="Create feature projects">
    Create standard projects for each feature within the initiative.
  </Step>

  <Step title="Link features to the product">
    From each feature project's action menu, select **Link to Product** and choose the parent product.
  </Step>

  <Step title="View the hierarchy">
    Go to **Projects** (`/admin/projects`) and switch to the **Portfolio** tab. Products appear as expandable cards.
  </Step>
</Steps>

### Portfolio + Workspaces

Portfolio view supports **workspace filtering**. Select a workspace from the filter dropdown to see only products and features belonging to that team.

This is powerful when combined:

```mermaid theme={null}
flowchart TD
    ORG["Organization: Acme Corp"]

    ORG --> WS1["👥 Mobile Team"]
    ORG --> WS2["👥 Platform Team"]

    WS1 --> PROD1["🏗️ Mobile App v3"]
    PROD1 --> F1["Push Notifications"]
    PROD1 --> F2["Offline Mode"]

    WS2 --> PROD2["🏗️ Admin Dashboard"]
    PROD2 --> F3["Analytics Overhaul"]
    PROD2 --> F4["Role-Based Views"]

    WS2 --> STANDALONE["API Rate Limiting"]

    style WS1 fill:#059669,color:#fff
    style WS2 fill:#3B82F6,color:#fff
    style PROD1 fill:#10B981,color:#fff
    style PROD2 fill:#60A5FA,color:#fff
```

When you filter by "Mobile Team", you only see the Mobile App v3 product and its features. When you filter by "Platform Team", you see the Admin Dashboard product plus the standalone API Rate Limiting project.

***

## Decision Guide

Not sure which organizational feature to use? Here's a quick guide:

| Situation                                       | What to use                                                               |
| ----------------------------------------------- | ------------------------------------------------------------------------- |
| "I have one feature to spec out"                | Just create a **Standard project**                                        |
| "I have a multi-feature initiative"             | Create a **Product project** + link **Standard projects** as sub-features |
| "My org has 5+ people across different squads"  | Create **Workspaces** per squad                                           |
| "I want to see progress across all initiatives" | Use **Portfolio view**                                                    |
| "I just want to write PRDs"                     | Ignore workspaces and portfolio entirely — just use projects              |

<Tip>
  Start simple. You can always add workspaces and portfolio hierarchy later. Projects work perfectly fine on their own — the organizational layers are there when you need them.
</Tip>