← Back to Knowledge Base
Affect Performance Team
|Analytics|Nov 17, 2026

PostHog Introduces Cross-Project Dashboards for Unified Product Analytics

On November 6, 2026, PostHog introduced cross-project dashboards, a new way to combine insights from several projects within one organization. Each dashboard tile reads data from its own project, while a shared date range, time interval, and supported property filters can apply across the entire dashboard. PostHog announced the feature in its changelog and published detailed setup and access rules in its dashboard documentation.

Compare Multiple Projects Without Switching Dashboards

PostHog typically stores insights and dashboards at the project level. Organizations may keep different products, geographic markets, or environments in separate projects, so comparing their performance has traditionally required switching between projects or copying dashboards and templates. A copied dashboard is an independent object: later changes to the original are not automatically reflected in the copy.

A cross-project dashboard removes the need for that duplication. Each tile remains associated with its source project, and its header identifies the project by name. Teams can place comparable metrics from different products, regions, or environments on one screen while retaining the underlying project boundaries.

How to Create a Cross-Project Dashboard

The feature is available through a dedicated tab on PostHog's Dashboards page. The setup process is straightforward:

  1. Open Dashboards and select Cross-project dashboards.
  2. Click New cross-project dashboard, enter a name, and select Create.
  3. Click Add insight, choose a source Project, and select an Insight from that project.
  4. Click Add to dashboard and repeat the selection for other insights.

Users can add insights from projects they have permission to access. An insight can appear only once on a given cross-project dashboard, which supports up to 100 tiles. To change the layout, click Customize, move or resize the tiles, and save with Save layout. If a tile is removed accidentally, the Undo action in the notification can restore it.

Shared Filters, Tile Overrides, and Data Comparability

The dashboard-level date range and interval apply across its tiles. Teams can also filter by event properties, person properties, and event metadata; each source project evaluates those filters against its own data. This supports side-by-side analysis of comparable user behaviors without manually configuring every project dashboard.

Cohort, group, and feature flag filters are not supported across projects because their underlying identifiers can refer to different things in different projects. Individual tiles can still use a different date range or interval through Set override in the tile menu. The Clear all overrides action restores the dashboard-wide settings.

PostHog also highlights conditions that could make metrics appear inconsistent. A Time zone indicator identifies tiles from projects with different time zones; their calendar days begin at different times, so daily totals may not align perfectly. A Filter not in this project indicator means the selected project has never recorded the property used by a shared dashboard filter. The filter therefore matches no events in that project. These warnings are especially useful when teams compare daily results from different regions or applications.

Who Can View and Edit a Cross-Project Dashboard?

Any member of the organization can open a cross-project dashboard, but each person sees only tiles from projects they are authorized to access. Two colleagues may therefore see different subsets of the same dashboard. An organization member cannot edit or delete a dashboard if it contains a tile from a project that member cannot access, preventing changes to tiles the user cannot see.

Deleting a cross-project dashboard removes that dashboard for the organization, but it does not delete the original insights. They remain in their respective projects.

Managing Dashboards Through API and MCP

PostHog provides a dedicated API for creating and updating cross-project dashboards and their tiles. API access requires a personal API key with organization-wide access and the cross_project_dashboard scope. Keys limited to individual projects cannot use these endpoints. This distinction matters for reporting workflows that span multiple PostHog projects.

The PostHog MCP server can list cross-project dashboards and read their tiles, allowing connected AI assistants to retrieve these summaries. The original announcement and documentation do not specify separate plan-level availability conditions for the feature, so organizations should confirm any subscription or access requirements in their own accounts.

How Cross-Project Dashboards Fit Into PostHog

PostHog positions itself as a platform for building and operating products, bringing together event analytics, web analytics, session replay, feature flags, A/B testing, error tracking, surveys, AI observability, and data warehouse capabilities. Its product and engineering tools also use event streams, logs, and session data to help teams identify problems and improve applications.

Cross-project dashboards add an organization-level reporting layer without merging source projects or duplicating their insights. They are useful when teams need consistent visibility into the same key performance indicators across products, markets, and environments, while respecting project-specific permissions and differences in how data is collected.

Trust Us Transform Your Performance Marketing.

Connect product analytics with acquisition and revenue outcomes. We help teams audit event tracking, conversion measurement, and cross-channel reporting so insights from different products and markets support better marketing decisions.

Audit Your Marketing Analytics

Sources