Installation
This bundle requires Pimcore Core Framework 12 / 2026.x, Studio Backend Bundle, and Studio UI Bundle. Install those first.
Bundle Installation
- Install the required dependencies:
composer require pimcore/studio-dashboards-bundle
- Enable the bundle in
config/bundles.php:
use Pimcore\Bundle\StudioDashboardsBundle\PimcoreStudioDashboardsBundle;
// ...
return [
// ...
PimcoreStudioDashboardsBundle::class => ['all' => true],
// ...
];
- Run the bundle installer to register the required user permissions:
bin/console pimcore:bundle:install PimcoreStudioDashboardsBundle
- Clear the cache:
bin/console cache:clear
Permissions
The installer registers the following user permissions in the Pimcore Studio Dashboards Bundle category:
| Permission | Description |
|---|---|
studio_dashboards_view | View dashboards |
studio_dashboards_edit | Create and edit own dashboards |
studio_dashboards_edit_all | Edit dashboards owned by other users |
studio_dashboards_share | Share dashboards with other users or globally |
studio_dashboards_export | Export dashboards as ZIP archives |
studio_dashboards_import | Import dashboard ZIP archives |
Assign these permissions to roles or users in Pimcore Studio under Settings > Users & Roles.
The navigation entry Reporting > Dashboards is also controlled by the reporting.dashboards
perspective permission (configured under Settings > Perspectives in Pimcore Studio).
Enable it for any perspective that should show the dashboards menu.
Frontend Build
The compiled Studio frontend ships as a single archive (build-dist/build-<id>.zip) rather than a
committed public/studio/build/ directory. pimcore/studio-ui-bundle extracts it into
public/studio/build/ automatically during cache warmup, so no extra step is needed for a
standard installation.
Read-only filesystem deployments must run bin/console cache:warmup (or cache:clear) during the
build/deploy phase, while the bundle directory (usually under vendor/) is still writable. When
assets:install runs in copy mode, run cache:warmup before it, otherwise no frontend assets are
copied. If the filesystem becomes read-only before the first warmup, the bundle fails with
BuildArchiveNotWritableException because there is no build to serve.