Experimental

Admin → Experimental holds features that are available but not enabled by default. Each flag is off until someone turns it on.

What lives here

Dashboards — configurable, self-service dashboard views built from scope metrics. Off by default; the product’s built-in boards do not depend on it.

Platform analytics — product usage telemetry for the tenant: who is active, what features are used, how it is being adopted. Off by default.

Caution

Both are tenant-level switches. Enabling a feature makes it available to the whole tenant, so it is a product decision rather than a per-user one.

Why these are flagged

These are the parts of the product that are useful to some deployments and unnecessary for others. Putting them behind flags means a small team is not presented with dashboards and usage analytics they did not ask for, and a large one can turn them on without a configuration change.

The main documentation deliberately does not cover either in depth while they are off. If you have enabled one, the in-app surface is where its behaviour is described.

Platform analytics

A lightweight, self-hosted alternative to third-party product analytics: the telemetry stays in your deployment rather than being sent out. See multi-tenancy and isolation for the wider self-hosting model.

Dashboard availability

The scope board is a core surface and is always available. The Experimental dashboard feature is something different: a configurable, self-service view you build yourself. If you are looking for the scope board, you already have it.