# Project Management

Project Management on the Infraon platform is used to plan, execute, and track projects by organizing work into structured components, including **projects, tasks, teams, workflows, and milestones.** It provides a centralized workspace where users can manage the full lifecycle of a project, from creation through execution and monitoring, while maintaining visibility and control over progress, ownership, and timelines.

To access the module, navigate to **Workspace → Project Management**. This opens the project workspace where projects are listed in the left panel, and key sections such as **Summary, Tasks, Teams & Roles, Notifications, Project Settings, and Audits** are available for the selected project.

The module is designed to support controlled project execution by **combining** task management, workflow-driven status transitions, role-based access, and real-time updates.

## **How does it work**

Projects can be created using a **blank configuration** or an existing **project template**. During creation, users define project details, select a workflow, configure teams and roles, and set up tasks.

After creation, tasks can be **added, edited, deleted, cloned, or imported via CSV.** Tasks can be updated directly from the table view and linked with milestones and dependencies.

Project progress can be tracked using:

* **Dashboard** for summary and insights
* **Table view for** status tracking
* **Gantt Chart** for timeline and dependencies

Teams, roles, and workflows can be configured to control access, ownership, and status transitions, including approval and review stages.

![](/files/ee0abe812e11a133ca6f26b3017fe26505620ae0)

In the left panel of the Project Management module, you can access the sections described below.

### **Project Workflow Lifecycle**

The **Project Workflow** defines the end-to-end lifecycle of a project—from initiation to closure. It ensures structured progression, stakeholder validation, and controlled execution across all project phases.

#### **How the Project Workflow Operates**

The workflow progresses through a sequence of predefined states:

1. **Initiation**

* The project is created and enters an initial/open state.
* Basic details such as scope, owner, and objectives are defined.

2. **Planning**

* Project scope, timelines, resources, and deliverables are finalized.
* Dependencies and milestones are configured.

3. **Approval**

* Stakeholders review the project plan.
* Approval mechanisms include:
  * All members' approval
  * Percentage-based approval

4. **Execution**

* Project activities are actively carried out.
* Tasks are assigned and tracked.

5. **Review**

* Project outcomes are evaluated.
* Validation ensures deliverables meet expectations.

6. **Closure**

* The project is formally completed and closed.
* Final documentation and sign-offs are completed.

<figure><img src="/files/2gCU0tv1eLaxiYNmGbXP" alt=""><figcaption></figcaption></figure>

Project Workflow **| Status / State Options**

<table><thead><tr><th width="153">Status / State</th><th width="381.800048828125">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Open / Initiation</strong></td><td>The project is created and initialized</td><td>New project created</td></tr><tr><td><strong>Planning</strong></td><td>Project details and execution plan are defined</td><td>Scope finalization</td></tr><tr><td><strong>Approval</strong></td><td>Stakeholders validate the project</td><td>Manager approval</td></tr><tr><td><strong>Execution</strong></td><td>Project work is actively in progress</td><td>Tasks being executed</td></tr><tr><td><strong>Review</strong></td><td>Output is evaluated and validated</td><td>QA / stakeholder review</td></tr><tr><td><strong>On Hold</strong></td><td>The project is temporarily paused</td><td>Waiting for dependency</td></tr><tr><td><strong>Closure / Closed</strong></td><td>The project is completed and archived</td><td>Project delivered</td></tr></tbody></table>

{% hint style="info" %}

* Supports **approval workflows** with configurable rules
* Enables **conditional transitions** using “If Conditions.”
* Automates actions like:
  * Email notifications
  * SMS alerts
  * State transitions
* Ensures **audit tracking and traceability**
  {% endhint %}

### **Project Task Workflow Lifecycle**

The **Project Task Workflow** defines how individual tasks move from creation to completion within a project. It ensures clear task tracking, execution control, and validation.

**How the Task Workflow Operates**

1. **To Do**

* Task is created and awaits execution.
* Assigned to a user or team.

2. **In Progress**

* Work begins on the task.
* Active execution phase.

3. **On Hold**

* Task is temporarily paused.
* Typically due to blockers or dependencies.

4. **Review**

* Completed task is validated.
* Ensures quality and correctness.

5. **Done**

* Task is successfully completed.
* Ready for closure.

6. **Closed**

* Task is finalized and archived.
* No further changes allowed.

<figure><img src="/files/TVK8pR8RswkIfwrkzcp0" alt=""><figcaption></figcaption></figure>

**Task Workflow | Status / State Options**

<table><thead><tr><th width="165.79998779296875">Status / State</th><th>Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>To Do / Open</strong></td><td>Task is created and pending execution</td><td>New task assigned</td></tr><tr><td><strong>In Progress</strong></td><td>Task is actively being worked on</td><td>Development started</td></tr><tr><td><strong>On Hold</strong></td><td>Task is paused due to blockers</td><td>Waiting for approval</td></tr><tr><td><strong>Blocked</strong></td><td>Task cannot proceed due to issues</td><td>Dependency missing</td></tr><tr><td><strong>Review</strong></td><td>Task is under validation</td><td>QA review</td></tr><tr><td><strong>Done</strong></td><td>Task is completed</td><td>Work finished</td></tr><tr><td><strong>Closed</strong></td><td>Task is finalized</td><td>Task archived</td></tr></tbody></table>

{% hint style="info" %}

* Enables **granular task tracking** within projects
* Supports:
  * Automated notifications
  * Conditional logic
  * Re-triggerable actions (Is Resend)
* Ensures **structured execution and visibility**
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.infraon.io/infraon-help/infinity-user-guide/workspace/project-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.