What the tenant sees

These three pages are orientation, not an API reference. They exist so you know what happens to a view you declare in an analytics.json, and so you can have a sensible conversation with an operator about what they are looking at.

Everything described here is a Cockpit feature. There is no endpoint behind any of it that you can call — see What does not exist yet.

The pages

• Studio overview — the shape of the surface, and what it means for your integration that it is Cockpit-only.
• Datasets and charts — where a declared view lands, and how your title, roles and column choices show up.
• Cohorts — the one feature with a hard requirement on your declaration.

Why a partner should care at all

Two reasons, and neither is "so you can integrate with it":

1. It is where your analytics.json lands. Design decisions in your declaration — a missing time role, a UUID as a dimension, a title that does not state the grain — show up here as a dataset an operator cannot use.
2. It sets expectations. A customer who has seen charts in Cockpit will ask you for the same charts in your product. Knowing what is and is not available saves that conversation going the wrong way.