> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/help/workspace-and-organisation/workspace-organisation.md).

# Workspace Organisation

This article explains how workspaces are structured in Model Reef and how to organise models at the top level.

You will learn:

* What a workspace is and what it contains.
* How workspaces relate to models, scenarios and templates.
* How to organise workspaces for firms, teams and clients.

{% stepper %}
{% step %}

### What a workspace is

A workspace is a top level container for all of your modelling assets. A workspace can contain:

* Models.
* Scenario models (which are just separate models).
* Folders.
* Model templates.
* Archived models.

Workspaces control **organisation** and **access**, not modelling logic. All of the financial rules live inside each model.

Typical workspace patterns:

* One workspace per firm or business.
* Separate workspaces for different business units if needed.
* Separate workspaces for internal vs client facing work.
  {% endstep %}

{% step %}

### Models and scenarios inside a workspace

Inside a workspace you will see a list or folder tree of models.

Key points:

* Each **scenario** is simply its own model in the workspace.
* Versions such as `Base Case`, `Downside` and `Upside` are all models.
* You can group related models in folders, for example by client, project or year.

Nothing special happens to a model when you decide to treat it as a scenario or a version. That is a workflow convention, not a technical type.
{% endstep %}

{% step %}

### Templates inside a workspace

Workspaces also hold **model templates**.

Templates are models that have been marked as reusable starting points. They usually contain:

* A standard branch structure.
* Variable stubs and categories.
* Preconfigured dashboards and reports.
* Optional example assumptions.

You can store templates:

* In a dedicated `Templates` folder.
* By client or sector if you have specialised structures.

Using templates keeps new models consistent across the workspace.
{% endstep %}

{% step %}

### Archived models in a workspace

When you archive a model it moves into an archive area of the workspace.

From the workspace perspective:

* Archived models are hidden from day to day working lists.
* They still exist in full, including data, notes, tags and attachments.
* Owners can restore archived models when needed.

Archiving is covered in more detail in the **Model Archiving** article.
{% endstep %}

{% step %}

### Organising a workspace for scale

For small teams you can start with a simple layout, for example:

* A single workspace.
* Folders per client or business line.
* A shared templates folder.

As the organisation grows you can:

* Split work into multiple workspaces if needed for access separation.
* Create more structured folder trees (by client, entity, year, project).
* Establish naming conventions for models and templates.

The goal is for anyone joining the team to quickly find the right model without guessing.
{% endstep %}
{% endstepper %}

## Related articles

* [CFO-for-Hire Monthly Close Package](/use-cases/accounting-firms-and-advisors/cfo-for-hire-monthly-close-package.md)
* [Scenarios & Planning](/how-tos/scenarios-and-planning.md)
* [Unit Detection](/help/importing-and-data-inputs/unit-detection.md)
* [KPI Cards](/syntax/chart-and-table-syntax/kpi-cards.md)