> 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/core-concepts/workspace-project-and-megaproject.md).

# Workspace, project and megaproject

What each term means and how they relate to one another.

Supria Workspaces organizes your data using three related concepts: **workspace**, **project**, and **megaproject**. But what does each term mean, and how do they relate to each other?

***

### Workspace

A workspace is an isolated environment that contains your organization's projects, users, and settings. Each tenant can have one or more workspaces.

{% hint style="info" %}
Data within a workspace, such as projects, groups, and settings, is never shared with another workspace, even within the same organization.
{% endhint %}

You configure workspace-level settings once, before creating any projects. These settings include metadata, project types, units of measure, currencies, and connections to external tools.

***

### Project

A project is the fundamental unit of work within a workspace. Every project belongs to exactly one workspace.

Projects can be organized hierarchically: a project can have child projects. This structure supports two common patterns:

* A **standalone project** with no child projects.
* A **megaproject** that uses child projects to represent its areas.

***

### Megaproject

A megaproject is a project flagged to represent a large capital investment initiative that spans multiple areas. Structurally, a megaproject is a standard project record. There's no separate "megaproject" entity in the system. What makes it a megaproject is a flag on the project record that identifies it as a large investment project.

#### Areas

An area is a child project of a megaproject. Areas let you split a megaproject into manageable segments, each with its own:

* Work breakdown structure (WBS) elements.
* Assigned vendor.
* Code and weight, used to consolidate progress and costs at the megaproject level.

Because areas are themselves projects, they inherit the same project-level capabilities (schedule, cost, risk, and so on), while also rolling their data up into the parent megaproject.

***

### How the concepts relate

The hierarchy, from broadest to most specific, is:

```mermaid
flowchart TD
    A("`**Workspace**`")
    B("`**Project**`")
    C("`**Megaproject**`")
    D("`**Area A**`")
    E("`**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
    style E fill:#7f7f7f, stroke-width:0px

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

When you set up a megaproject, you first configure workspace-level settings (metadata, permissions, currencies), then create the megaproject, and then define megaproject-level settings, such as WBS (work breakdown structure) levels, schedule phases, vendors, disciplines, activities, and approval levels.