> For the complete documentation index, see [llms.txt](https://docs.supria.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.supria.com/home/get-started/megaprojects/what-is-a-megaproject.md).

# What is a megaproject?

Learn about megaprojects and why they exist.

A megaproject is the highest organizational level for an initiative in Supria Workspaces. It brings every area, schedule, and supplier of a large-scale build or deployment into one governance structure.

***

### Why does this term exist?

In project management, a **megaproject** is a large-scale, high-cost, complex initiative. It involves multiple workstreams, suppliers, and teams working in parallel for years. Typical examples include industrial plants, pulp mills, and major infrastructure works.

This type of initiative cannot be managed as a single project. Each workstream has its own schedule, budget, and team. At the same time, initiative leadership needs a consolidated view.

Supria Workspaces resolves this with the **Megaproject** object. This organizational level sits above areas. It consolidates progress, weights, approvals, and permissions. Each area keeps its own structure.

***

### Hierarchical structure

Within a workspace, a megaproject organizes work into four layers. Each layer has its own WBS (work breakdown structure). All layers contribute to the same total.

```mermaid
flowchart TD
    A("`**Supria Workspace**`")
    B("`**Megaproject**`")
    C("`**Area A**`")
    D("`**Area B**`")


    style A fill:#1dd19b, stroke-width:0px
    style B fill:#8b69fd, stroke-width:0px
    style C fill:#ffca18, stroke-width:0px
    style D fill:#ff5840, stroke-width:0px


    A --> B
    B --> C
    B --> D
```

Where:

* **Supria Workspaces**: The customer's single environment. It contains metadata, users, all megaprojects, and standard projects.
* **Megaproject**: Has its own WBS (Project → Group → Process), schedule phases, suppliers, disciplines, and approval authorities shared by every area.
* **Area**: A workstream with its own schedule, supplier, and weights.

Each area's weight determines its contribution to the megaproject's total physical progress. Weight configuration is therefore a critical governance task.

***

### When to use a megaproject

Use a megaproject when an initiative has **more than one independent workstream**. Those workstreams must still be reported together. These signs indicate that a customer needs a megaproject, rather than a standard project:

* Several areas have their own suppliers, disciplines, and schedules. Examples include site preparation, buildings, and process EPC.
* Initiative leadership needs consolidated status and physical-progress reports across areas.
* Approval workflows for changes, baselines, and payments share approval authorities across all areas.
* Different access roles need to view the full portfolio without editing every area.

***

### Roles and permissions

Standard groups control access to a megaproject. They are created automatically when the megaproject is configured.

<table><thead><tr><th width="283">Group</th><th>Permissions</th></tr></thead><tbody><tr><td><strong>Megaproject administrator</strong></td><td>Creates, edits, and deletes the megaproject and its areas. Accesses settings and approves megaproject workflows.</td></tr><tr><td><strong>Portfolio manager</strong></td><td>Has the same permissions as an administrator, except access to settings and workflow approvals.</td></tr><tr><td><strong>Portfolio viewer</strong></td><td>Views all areas and their items. Cannot create, edit, or delete.</td></tr><tr><td><strong>Risk administrator</strong></td><td>Manages the megaproject's Risks module and views all areas.</td></tr><tr><td><strong>Risk viewer</strong></td><td>Views only megaproject risks. Cannot take action.</td></tr></tbody></table>

Within each area, a second group set controls access to that workstream: Owner, Contributor, and Viewer.

***

### Related terms

* **Area**: A workstream within a megaproject. It has its own schedule, supplier, and weight. It is equivalent to a project within the megaproject.
* **Megaproject WBS**: The work breakdown structure that organizes the megaproject into groups and processes. It is used when creating areas.
* **Area WBS**: The schedule phase and stage structure for each area. It is used in status reports and baseline requests.
* **Approval authority**: A sequence of roles, such as planner, coordinator, and manager. These roles must approve workflows such as changes, payments, and baselines.
* **Area weight**: The percentage that defines how an area's physical progress affects the megaproject's total physical progress.