Understand Insights Hub data, access, and limitations

Mariia Korostashevych

Updated August 20, 2026 23:50

Purpose	Understand how Insights Hubs display reporting data, control access, select available charts, and protect report dependencies.
Best for	Property owners, property admins, managers, accounting or finance teams, and revenue or reporting users who review or maintain Insights Hubs.
Use this when	You are planning a Hub, comparing Hub values with source reports, managing user access, or troubleshooting why a report or chart is unavailable or cannot be deleted.
Requirements	Access to the source reports and datasets used by the Hub. A paid Cloudbeds Insights subscription is required to create Saved Reports and add tables from Saved Reports.
Expected result	You can interpret Hub values, identify eligible report content, understand what each user can view, and maintain Hub dependencies without disrupting active cards.
Limitations	Each Hub supports a maximum of 15 charts. A source report must already contain a chart before that chart becomes available in the Hub chart selector.

Introduction

Insights Hubs bring charts and report tables together on a customizable page in Reporting. A Hub can support a specific role, workflow, or recurring review by keeping related revenue, occupancy, reservation, or operational information in one place.

Hub cards preserve important behavior from their source reports. The selected dataset determines how values and dates are interpreted, report-level currency settings determine how converted values appear, and dataset permissions determine which cards each user can access.

Use this article to understand those data, access, availability, and maintenance rules before building or changing a Hub.

The following example shows an Insights Hub with several reporting cards and the controls used to refresh, add, save, or manage its content:

Who this affects and how
When to use an Insights Hub
Understand Insights Hub data
Manage Hub access and available charts
Remove Hub chart dependencies
Review Hub limits and ownership

Who this affects and how

Insights Hubs can support several property roles, but each role uses the displayed information differently. Use the following table to find the sections most relevant to your work.

Role	What to know
Property admin	Confirm that users have access to every dataset used by the Hub. Before deleting a report or chart, review the Hub dependency rules.
Manager or general manager	Use Hubs to keep frequently reviewed operational and performance visuals together. When two cards show different revenue results, review how the dataset and date method affect each source report.
Property owner	Use Hubs for recurring property or portfolio reviews. Review multi-property currency behavior before comparing properties that use different base currencies.
Accounting, finance, or revenue user	Confirm what Total Revenue includes and whether each source report uses Service Date or Transaction Date. Hub cards follow the data logic and configuration of their source reports.

When to use an Insights Hub

Use an Insights Hub when you want to review related reporting visuals or tables from one customizable page. Common uses include monitoring revenue and occupancy, reviewing reservation trends, comparing operational metrics, or assembling information for a recurring management review.

Create separate Hubs when different roles or workflows require different information. Keeping each Hub focused makes its purpose clearer and helps users avoid scanning cards that are unrelated to their work.

For instructions to create, populate, arrange, export, and manage a Hub, see How to build Insights Hubs.

Understand Insights Hub data

Each Hub card displays data from its source report. Expand the sections below to review how revenue, dates, currencies, and the Occupancy dataset affect the values shown in a Hub.

Understand Total Revenue in Hub charts

In Cloudbeds Insights, Total Revenue is the sum of Total Room Revenue and Total Other Revenue.

Total Revenue excludes inclusive and exclusive taxes and fees.
Total Other Revenue can include items and services, add-ons, cancellation fees, and adjustments.
Commissions are tracked in a separate field and are not deducted from Total Revenue.

The Hub does not apply a separate revenue calculation. To confirm a metric used by a Hub card, review its definition in Cloudbeds Data Fields (CDFs): definitions and calculations.

Compare Service Date and Transaction Date

The dataset and date field used by a source report determine when revenue is attributed in its Hub card:

Occupancy datasets: Revenue is attributed by Service Date, also called Stay Date. This is the date when the stay or service occurs.
Financial datasets: A report can use Service Date or Transaction Date. Transaction Date is the date when the financial transaction is recorded.

Two Hub cards can show different results for the same date range when their source reports use different datasets or date fields. Compare the source report configuration before treating the difference as a reporting error.

Use Hubs across properties and currencies

A Hub uses the currency configuration of its source report. To show normalized values for properties with different base currencies, configure Currency Conversion in the Saved Report before adding its chart or table to the Hub.

Add the applicable Converted Currency Cloudbeds Data Fields to the report.
Select the converted currency in the report settings.
Use the Conversion Rate field when you need to review the rate applied to Converted Currency fields.

Past transactions use the historical exchange rate for the transaction date. Future transactions use the current exchange rate available when the report runs. The Hub displays the converted values as configured in the source report.

For multi-property reporting, standardize the source reports and converted currency before comparing properties in one Hub. Multi-property reporting and report-level currency conversion require Cloudbeds Insights.

Use the Occupancy dataset with Saved Reports

Properties with paid Cloudbeds Insights can create Saved Reports using the Occupancy dataset and add supported content from those reports to an Insights Hub.

The Occupancy dataset uses Service Date for revenue attribution. Review the Saved Report's fields and configuration before comparing it with a Financial report that may use Transaction Date.

Manage Hub access and available charts

A user must have access to the underlying dataset to view its Hub cards. A source report must also contain a chart before that chart appears in the Hub chart selector. Expand the sections below for detailed permission and chart-availability behavior.

Understand Hub permissions

Hub cards respect each user's access to their underlying datasets. A user can view a Hub card only when their role provides access to the dataset used by that card.

Each chart or table is connected to a specific report and dataset.
If a user loses access to that dataset, the user can no longer access the related Hub content.
Permission changes are reflected automatically.

If one user cannot access a card that other users can view, a property admin should compare their dataset and Reporting permissions before changing the Hub.

Identify charts available to add

The Hub chart selector shows eligible charts from Cloudbeds Reports and customer-created Saved Reports. A report must already contain a chart before that chart becomes available in the selector. Reports without charts do not appear as available chart options.

The available choices can vary by property, report configuration, and user access. Use the report search and the Report Type, Tags, and Chart Type filters to narrow the eligible charts.

The Add chart window displays eligible charts and the filters available to narrow the results:

Cloudbeds Insights supports nine chart types:

Line
Bar
Area
Combo
Pie
Sunburst
Treemap
Geomap
Calendar heatmap

If a custom report does not appear in the Hub chart selector, add and save a chart in that report first. See Create and edit charts in Cloudbeds Insights.

Remove Hub chart dependencies

When you add a chart to a Hub, the Hub card remains linked to that chart in its Saved Report. While the chart is used in at least one Hub, Cloudbeds prevents you from deleting either the source chart or the entire Saved Report.

A Saved Report that contains charts can normally be deleted when none of those charts is used in a Hub. If a deletion is blocked, remove the affected chart card from every Hub that uses it and save each Hub before trying again.

Cloudbeds does not identify which Hub contains the chart card. Manually review your Hubs and remove the card from every Hub where it appears.

If you try to delete the source chart while it is still used by a Hub card, Cloudbeds displays the following alert:

If you try to delete the Saved Report while one of its charts is still used in a Hub, Cloudbeds displays this warning:

Remove a chart from every Hub

Complete this workflow first, whether you plan to delete only the source chart or the entire Saved Report.

Open the Main Menu
Select Reporting
Select the Hubs tab.
Open a Hub and find the card created from the chart you want to delete.
Open the three-dot menu on the card and select Delete.
Click Save.
Manually check the remaining Hubs. Repeat steps 4-6 in every Hub that contains the same chart card.

On each affected Hub card, open the three-dot menu and select Delete:

After the chart card is removed from every Hub and each Hub is saved, choose the workflow that matches what you want to delete.

Delete a chart and keep the Saved Report

Use this workflow when you want to keep the Saved Report but no longer need one of its charts.

Open the Main Menu
Select Reporting
Select the Reports tab and open the Saved Report.
Open the three-dot menu on the chart and select Delete chart.
Confirm the deletion.

In the Saved Report, open the chart's three-dot menu and select Delete chart:

The Delete chart confirmation identifies the source report and requires you to confirm the action:

The Saved Report remains available without the deleted chart.

Delete the entire Saved Report

Use this workflow when you no longer need the Saved Report. The report can contain other charts, provided that none of its charts is still used in a Hub.

Open the Main Menu
Select Reporting
Select the Reports tab.
Find the Saved Report, open its three-dot menu, and select Delete.
Review the subscriptions and favorites listed in the confirmation, and then confirm the deletion.

On the Reports tab, open the Saved Report's three-dot menu and select Delete:

The confirmation identifies the Saved Report, notes that its subscriptions and favorites are included, and warns that the action cannot be undone:

Deleting a Saved Report cannot be undone. Confirm that the report and all of its charts are no longer needed before completing the deletion.

The Saved Report and its remaining charts are permanently removed from the property.

Review Hub limits and ownership

Use the documented limits and ownership behavior to plan Hubs that remain easy for the property to maintain.

Each Hub supports a maximum of 15 charts.
There is no separate published maximum for the total number of Hubs a property can create.
Hubs are not tied exclusively to the user who created them.
Deactivating the Hub creator does not automatically remove the property's Hubs.

Give each Hub a clear purpose and description. Periodically review whether its source reports, permissions, and cards are still relevant.

Now that you understand how Insights Hub data, access, availability, and dependencies work, review these resources for broader Cloudbeds Insights guidance and adjacent report-management tasks: