---
title: Using Scope and View
slug: blueprint/using-scope-and-view
docTags: et-uC7z298LGf19xvaFb5,yO7XZ9PJxDCKZ-Mf4TSYB
createdAt: 2026-04-17T18:28:54.105Z
---

:::CtaButton{label="🟢 Migrator" openInNewTab="false"}

:::

Scope and View settings control what data appears in the dashboards and reports.

***

# Setting the Scope

The Scope determines which projects, folders, and processes are included in dashboard and report data.

1. Click **Change Scope** in the top right
2. Select a project, folder, or process and click **OK**

# Setting the View

The View determines how data is organized within the dashboard.

1. Click the **View** dropdown and select either **Per Process View** or **Per Call Tree View**

:::Heading{depth="2" indent="1"}
Per Process View
:::

:::Paragraph{indent="1"}
Displays only the items within the selected project, folder, or process. The data shown reflects exactly what is in the selected scope — no dependencies outside that selection are included.
:::

:::Heading{depth="2" indent="1"}
Per Call Tree View
:::

:::Paragraph{indent="1"}
Searches for dependencies of each Main or Root process and adds them to the current scope, even if they fall outside the initial selection. This lets you analyze a full automation — the Main process and everything it calls — without needing to reorganize processes into a common folder first.
:::

:::Paragraph{indent="1"}
On import, Blueprint labels each process as either a **Main** or a **Sub-Process**:
:::

:::Paragraph{listStyleType="disc" indent="2"}
**Main** — the starting point of an automation; defined differently depending on the source tool
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
**Sub-Process** — any process called by a Main
:::

:::hint{type="info" indent="1"}
ⓘ If a Main or Sub-Process has been identified incorrectly, a user with the appropriate permissions can change the designation. This affects how the process is grouped in analytics and reports only. 

The Main designation assigned at import is permanent for licensing purposes — changing the label does not affect license consumption. See [Migrator/MigrateDashboards: License Consumption](docId\:Ytu76e7qoCXu2DX1ec2-2).
:::

:::Paragraph{indent="1"}
**How Mains are identified by source tool:**
:::

:::Paragraph{listStyleType="disc" indent="2"}
**UiPath** — defined in the project.json file
:::

:::Paragraph{listStyleType="disc" listStart="2" indent="2"}
**Blue Prism** — the Main Page plus all associated and called pages of an imported process
:::

:::Paragraph{listStyleType="disc" listStart="3" indent="2"}
**A360** — all Root processes are identified as Mains
:::

***

## Include All Roots

When Per Call Tree View is active, a toggle for **Include All Roots** appears in the **Change Scope** modal. A Root is any process not referenced by another process.

- **Enabled** — all Root processes and their dependencies are included in the scope
- **Disabled** — only processes flagged as Main and their dependencies are included