> For AI agents: the complete Sanity documentation index is available at [https://www.sanity.io/docs/llms.txt](https://www.sanity.io/docs/llms.txt).

# How the beta works

What Dashboard 2.0 is, how it differs from the current Dashboard, and what using the beta commits you to.

Dashboard 2.0 is in beta. It runs alongside your current Dashboard, so you can try it without switching anything over. The extension API and application Blueprints can change in minor releases. To start building, see [Get started](https://www.sanity.io/docs/dashboard-beta/get-started).

## What Dashboard 2.0 is

Dashboard 2.0 is the next version of the Sanity Dashboard. It's one place for your organization's studios, custom apps, and Sanity apps such as Canvas and Media Library.

Your organization can now customize it. Your apps can add their own views to the Dashboard, not only a full-page window:

- Window: the app's main, full-page view.
- Panel: a column beside the dock that stays open while you work in the window.
- Tile: a compact view on the Dashboard home page.
- Asset source: a picker the Dashboard opens when someone selects an asset source.
- Web worker: code that runs in the background while the Dashboard is open.

Apps can read Dashboard state, navigate, and open panels with hooks from `@sanity/sdk-react/dashboard`. You can also define an application as a Blueprint resource. See [Extend the Dashboard](https://www.sanity.io/docs/dashboard-beta/extension-api).

## Why it exists

Dashboard 2.0 lets your organization shape the Dashboard and its applications around how your business works. Your own code runs in its own isolated view inside the Dashboard, beside your studios and Sanity's apps. That gives you more ways to make Sanity the content operating system for your business.

## How it compares with the current Dashboard

|  | Current Dashboard | Dashboard 2.0 beta |
| --- | --- | --- |
| Address | `https://www.sanity.io/@<organization-id>` | `https://<organization-id>.sanity.run` |
| Where your app shows up | One full-page view | Window, panels, home page tiles, asset source pickers, and background web workers |
| App configuration | `app` in `sanity.cli.ts` | `defineApplication` in `sanity.cli.ts` |
| Local development | `sanity dev --load-in-dashboard` | `sanity dev` starts a local Dashboard that all your local apps share |
| Talking to the Dashboard | Not available | Hooks in `@sanity/sdk-react/dashboard`: read state, navigate, open panels, follow the color scheme |
| Deploy as code | Not available | Applications as Blueprint resources |

## Use the beta alongside your current Dashboard

The beta doesn't replace your current Dashboard. Open it at `https://<organization-id>.sanity.run` whenever you want to use it, and keep using your current Dashboard the rest of the time. You don't need to switch your organization over to try it.

## Versions and breaking changes

The whole extension API is in beta, including `defineApplication` and the view helpers. A minor release can include breaking changes, so read the changelogs for `sanity` and `@sanity/sdk-react` before you upgrade.

- `unstable_` helpers: `unstable_defineView`, `unstable_defineService`, and `unstable_defineMediaLibrary` can change without notice.
- Blueprint resources: Applications and singleton configs as Blueprint resources are in beta. Their fields can change in a future release of `@sanity/blueprints`.

SDK apps need `@sanity/sdk-react` 3.9.0 or later and React 19.2 or later.

## Migrating an app creates a new application

You can't convert an app you've already deployed. Deploying with `defineApplication` creates a new application at a new URL. Your existing app keeps working and stays in your organization until you undeploy it, but it won't get new Dashboard features. See [Migrate an SDK app to Dashboard 2.0](https://www.sanity.io/docs/dashboard-beta/migrate-an-app-sdk-app).

Choose the app's `name` carefully: it's the application's stable identity, and you can't change it after the first deploy. You can change `slug` later, but slugs are currently unique across all organizations, so pick one specific to your app.

## Share feedback

Tell us what works and what doesn't. In the Dashboard, select **Help & feedback** at the bottom of the dock, then select **Share feedback**.