# Save views and build dashboards

Use Save as view on analytics pages to keep query settings, then add the view in Dashboards. Members can create their own views and layouts. A studio holds up to 200 saved views and 50 dashboards, with at most 24 widgets per dashboard. Explore and Funnels save the query behind the displayed result, so unapplied form edits do not change it. Explore saves its selected relative range, which moves forward with time. Absolute Explore ranges supplied through the website API preserve a fixed window.

Start empty or from Overview, Monetization and Health presets. A game dashboard accepts views for that game. Portfolio dashboards use the existing studio metrics, monetization, funnel and property-breakdown endpoints; unsupported portfolio view types are refused. Those studio readers retain their existing game limits and aggregation semantics. Widgets do not introduce a new query engine or price.

Move widgets with labelled buttons or focus a widget and use arrow keys. Full width and Half width reflow the layout. Save changes explicitly; phone layouts use one column. Tables show up to 100 scalar values per widget and say when capped. Saved queries retain the original endpoint's data limits and units.

Dashboards start private to their creator. Only owners and admins can share them with the studio. Other members can read a shared dashboard or duplicate it, but cannot edit it. Saved views are studio-readable and creator-editable. A referenced view cannot be removed or change its game or kind until removed from dashboards; duplicate it instead. Deleting a game removes its saved views and dashboards.

MCP `list_views`, `list_dashboards` and `get_dashboard` read saved definitions at the standard programmatic rate. These reads do not execute widgets or change sharing. Dashboard writes stay in the authenticated website API.

Source: https://ravensight.io/docs/dashboards/
Last updated: 2026-11-15
