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

# Global Reports & Dashboards

> Create a report once and propagate it to every workspace while keeping each workspace’s data isolated.

## Overview

<Info>
  Enterprises and MSPs with many workspaces can build a single “source-of-truth” report or dashboard and have Pelanor automatically spin up an identical copy inside every workspace.\
  This avoids manual duplication and keeps formatting, filters, and grouping logic perfectly consistent.
</Info>

***

## How It Works

### Report Configuration

When you set a report to **Visible in all workspaces**, Pelanor creates a separate instance of that report in each workspace.\
Every instance shares the same configuration (date range, grouping, filters) but queries only the data that belongs to its workspace.

> **Example**\
> A global report grouped by **Service** for the **last 30 days** will appear in every workspace.\
> Workspace A will show its own service costs; Workspace B will show a different set—yet both use the exact same layout.

### Data Isolation

Only the configuration is global. Actual spend and usage remain scoped to the workspace the user is in, so permissions and data boundaries stay intact.

***

## Creating Global Reports

<Steps>
  <Step title="Start in the Default Workspace">
    Global content can be created **only** from the **Default Workspace**.\
    You’ll need **Admin** or **Advanced** permissions there.
  </Step>

  <Step title="Build Your Report">
    Design the report as usual—select metrics, groupings, filters, and date range.
  </Step>

  <Step title="Set Visibility">
    Click **Save Report** and choose **Visible in all workspaces** from the dropdown.\
    That’s it—Pelanor propagates the report everywhere.
  </Step>
</Steps>

***

## Creating Global Dashboards

Dashboards follow the same visibility control: select **Visible in all workspaces** when saving.

<Warning>
  Build global dashboards <strong>only</strong> from global reports.\
  If a widget references a local-only report, it will show an error in workspaces where the underlying report doesn’t exist.
</Warning>

***

## Best Practices

| Tip                                          | Why It Matters                                                                             |
| -------------------------------------------- | ------------------------------------------------------------------------------------------ |
| **Plan your global strategy**                | Decide which views truly benefit every workspace before enabling global visibility.        |
| **Use global reports for global dashboards** | Ensures every widget renders correctly everywhere.                                         |
| **Standardise naming**                       | A clear convention (e.g. “Global – Cost by Service”) helps users recognise shared content. |