---
title: "Get started with Reporting (Beta)"
slug: "get-started-with-reporting-beta"
description: "What is Fullcast Reporting (Beta), how is it different from classic reports, and where do I start?"
tags: ["use reporting", "reports (beta)", "revops admin", "create a report", "Tenant Admin", "Reporting", "reporting beta", "orientation", "get startedreports v2"]
status: "update"
updated: 2026-11-14T20:18:20Z
published: 2026-11-14T20:18:20Z
canonical: "support.fullcast.com/get-started-with-reporting-beta"
---

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

# Get started with Reporting (Beta)

> [!NOTE]
> Early access feature
> 
> This feature is currently available for early access. Contact your CSM for more information.

Reporting (Beta) is the new Fullcast reporting experience: you start from the data, then choose how to show it. This article gives you the mental model and the order to build in, with a link for each step.

## Turn on Reporting (Beta)

Reporting (Beta) is off by default. A Tenant Admin turns it on for the whole tenant:

1. Click the **Settings** gear in the top navigation.
2. Click **Application Settings**.
3. Under **Reporting**, turn on **Enable Reporting (Beta)**.

Once it's on, a **Reports** item with a **BETA** badge appears in the top navigation, next to the classic **Reports** item. Your classic reports and dashboards keep working, and Reporting (Beta) doesn't change or move them.

![](https://cdn.document360.io/369efcf7-66f9-4f6b-9d45-9ca24a5b06cf/Images/Documentation/image(731).png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A14%3A51Z&se=2026-11-15T01%3A14%3A51Z&sr=c&sp=r&sig=vtoFTwCX6Nn%2Bq0dfw7Fvpn6FTr%2BIpAzIiLbGPHplO2o%3D)

## How Reporting (Beta) thinks about data

Picture every report as a spreadsheet you build in two steps.

1. **Start with what you're counting.** Opportunities, accounts, people, or territories. That answer decides everything else.
2. **Build the dataset: your spreadsheet.** Pick what one row stands for, then add related data. A related list, such as the opportunities on each account, makes the rows more detailed. A linked record, such as an account's owner, adds columns without adding rows. A badge such as **Each row = 1 opportunity** always tells you what a row is.
3. **Decide which rows exist.** Choose **with**, **with or without**, or **WITHOUT** for each join, and add filters. These shape every report built on the dataset.
4. **Build the report: the summary of your spreadsheet.** Choose the numbers to total, how to group them, and how to show them. The report type is a display choice you can change at any time.
5. **Save the numbers you trust as metrics.** A total in a report is like the sum at the bottom of a spreadsheet column. Converting it to a metric saves that definition so everyone uses the same one.

## How Reporting (Beta) differs from classic reports

Classic reports start with a report type, such as a Basic Chart or a Coverage Report, and the type decides what data you can use. Reporting (Beta) flips that order.

| Question | Classic reports | Reporting (Beta) |
| --- | --- | --- |
| Where you start | Pick a chart or report type | Pick what each row of your dataset should be |
| Data you can combine | Set by the report type | Any related data you add to the dataset |
| Excluding records | Filters only | Filters, plus **WITHOUT** joins, such as accounts without opportunities |
| Fields | Dimensions and measures | One list of fields. Any field can be totaled or grouped. |
| Calculations | Measures with an aggregation | Measures, calculated fields, and calculated measures |
| Display | Fixed per report type | Change the **Report type** any time, from a summary table to a map |

## Build your reporting, step by step

1. **Build a dataset.** Choose what each row is, add related data, and filter it. Refer to [Build a dataset in Reporting (Beta)](/plan-and-pay/docs/build-a-dataset-in-reporting-beta).
2. **Add calculated fields** for values your data doesn't store. Refer to [Add calculated fields and measures in Reporting (Beta)](/plan-and-pay/docs/add-calculated-fields-and-measures-in-reporting-beta).
3. **Set up drill-downs** so people can zoom from a total into the detail. Refer to [Set up drill-downs in Reporting (Beta)](/plan-and-pay/docs/set-up-drill-downs-in-reporting-beta).
4. **Build, run, and save the report.** Refer to [Build and save a report in Reporting (Beta)](/plan-and-pay/docs/build-and-save-a-report-in-reporting-beta). To see whole reports built start to finish, refer to [Example: Find coverage gaps in Reporting (Beta)](/plan-and-pay/docs/example-find-coverage-gaps-in-reporting-beta), [Example: Compare territory balance in Reporting (Beta)](/plan-and-pay/docs/example-compare-territory-balance-in-reporting-beta), and [Example: Report on commissions earned in Reporting (Beta)](/plan-and-pay/docs/example-report-on-commissions-earned-in-reporting-beta).
5. **Convert trusted totals to metrics, pin reports to dashboards, and share them,** all from the report's **⋮** menu. To turn a total into a metric, refer to [Create and validate a metric in Reporting (Beta)](/plan-and-pay/docs/create-and-validate-a-metric-in-reporting-beta). To change or delete one, refer to [Manage metrics in Reporting (Beta)](/plan-and-pay/docs/manage-metrics-in-reporting-beta). To work with dashboards, refer to [Use a dashboard in Reporting (Beta)](/plan-and-pay/docs/use-a-dashboard-in-reporting-beta) and [Edit a dashboard in Reporting (Beta)](/plan-and-pay/docs/edit-a-dashboard-in-reporting-beta). To give people access, refer to [Share reports, dashboards, and folders in Reporting (Beta)](/plan-and-pay/docs/share-reports-dashboards-and-folders-in-reporting-beta).
6. **If something looks off,** refer to [Troubleshoot Reporting (Beta)](/plan-and-pay/docs/troubleshoot-reporting-beta). If someone can't open or change something, refer to [Reporting (Beta) permissions](/plan-and-pay/docs/reporting-beta-permissions).

## Key terms

- **Dataset:** the data a report reads. It starts from a hierarchy (**Territories**, **Teams**, **Product groups**) or a record type (**Accounts**, **People**, **Products**), plus any related data you add.
- **Row:** what one line of the dataset stands for, shown in the **Each row =** badge.
- **Related list:** related data where each record can have several, such as opportunities on an account. It makes rows more detailed.
- **Linked record:** related data with one match per record, such as an account's owner. It adds fields, not rows.
- **Metrics shelf vs. saved metric:** the **METRICS** shelf in the report builder holds any number you total. It becomes a saved, reusable metric only when you use **Convert to metric…**.
- **View by:** the fields a report groups by, up to three.
- **Calculated field / calculated measure:** a formula you write. A calculated field works on each row. A calculated measure works on the report's totals.
- **Drill-down:** a path people can click through in a report, such as fiscal year, then quarter, then month.

## How security works in Reporting (Beta)

Every dataset is secured by a hierarchy, and the starting points say which one, such as **Secured by Territories**. A report includes only the parts of that hierarchy you have access to, so two people can open the same report and see different numbers. **Users** and **Audit Logs** are marked **Administrators only**. Tenant Admins and Reporting users see every node.

## Use Reporting (Beta) from your AI client

With the Fullcast MCP (Model Context Protocol) connector, your AI client can work with Reporting (Beta) too. Reports you save in the app show up there, and what your AI client can do depends on your tenant and your role. For details, refer to [Use Reporting (Beta) through the Fullcast MCP](/plan-and-pay/docs/use-reporting-beta-through-the-fullcast-mcp).

## Related

- [Build a dataset in Reporting (Beta)](/build-a-dataset-in-reporting-beta.md)
- [Build and save a report in Reporting (Beta)](/build-and-save-a-report-in-reporting-beta.md)
- [Troubleshoot Reporting (Beta)](/troubleshoot-reporting-beta.md)