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

# 6.2: Charts and dashboards API

> Review key access, OAuth consent, saved charts and Cube configuration when you upgrade to 6.2.

**Applies to:** the upgrade to 6.2. Part of the [6.2 upgrade guide](https://formbricks.com/docs/self-hosting/upgrade/versions/6.2.md).

## Before

* **Review API keys.** Workspace `write` and `manage` keys gain chart/dashboard creation and editing through
  API v3 and MCP, plus deletion through API v3. MCP has no delete tools. Reading chart data also needs
  dataset access. While a dataset remains assigned and unarchived, chart changes need dataset write access.
  After removal or archival, renaming, styling and deletion remain possible; query and type changes do not.
* **Tell MCP users to sign in again.** Migrations add `dashboards:read` for clients with an MCP read scope
  and `dashboards:write` for those with an MCP write scope. Clients that skip consent are unchanged.
  Other clients keep their old access until users approve the new scopes at the next sign-in.
* **Review long time ranges.** Time-only charts now allow at most 10,000 buckets, including empty ones.
  Shorten the range or choose a coarser interval if a saved chart returns `limit_exceeded`.

## During

Use the [standard upgrade procedure](https://formbricks.com/docs/self-hosting/advanced/upgrade.md). No new environment variables are required.

* Refresh the release's [Cube model files](https://formbricks.com/docs/self-hosting/upgrade/configuration.md#download-the-cube-model-files).
  `cube/cube.js` now accepts API-key queries. One-click refreshes the files; Helm ships them in the chart.
  A stale file causes `502` for API-key/MCP chart reads even while charts in the app still work.
* The layout migration shortens widgets to at most eight rows and moves overlaps down within their column.
  New dashboards allow at most 250 widgets. Older oversized dashboards still open and save; review the
  migration log for their IDs. Wait for all schema and data migrations to finish.

## After

Check a chart through the app and through an authorized API/MCP client, OAuth re-consent, and existing
widget layouts. To delete a chart used on dashboards, remove it from those dashboards first.
Deleting a dashboard keeps its charts.

## Recovery

Keep maintenance active after a failed migration. Follow [migration troubleshooting](https://formbricks.com/docs/self-hosting/upgrade/troubleshooting.md).
Use a coordinated backup if repair cannot complete; reverting the app image does not reverse layout changes.

Source: [charts and dashboards API](https://github.com/formbricks/formbricks/pull/9786).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.