cube-js · igorlukanin · Aug 11, 2026 · Aug 11, 2026 · Aug 11, 2026 · Aug 11, 2026
@@ -68,9 +68,9 @@ The Base Role is required. Save is disabled until one is selected.
 
 #### Auto-bump to Developer
 
-If you check any deployment-scoped action stronger than **Access deployment** (`DeploymentRead`) — for example, **Edit deployment** or **Edit data model** — the Base Role is automatically forced to **Developer**, and the Viewer and Explorer options are disabled with a tooltip:
+If you check any deployment-scoped action other than **Access deployment** (`DeploymentRead`), **Access AI agents** (`DeploymentAgentRead`), and **Download data** (`DownloadData`) — for example, **Edit deployment** or **Edit data model** — the Base Role is automatically forced to **Developer**, and the Viewer and Explorer options are disabled with a tooltip:
 
-> Selected actions require Developer role
+> Selected permissions require Developer access
 
 Removing the elevated action re-enables the lower tiers. This mirrors the server-side rule that any deployment write or data-model write requires the Developer license tier.
 
@@ -118,16 +118,19 @@ Either grant **Full access** (a shortcut that enables every current and future d
 | Data Model  | View data model                     | Read data model files and dev branches.                                                                                                                                   |
 | Data Model  | Edit data model                     | Edit the data model on any branch, including the main/deploy branch. Allows committing and merging to main, force-syncing main, and starting dev mode against main.       |
 | Data Model  | Edit data model on dev branches     | Edit the data model only on non-default branches. Blocks any write that targets the main/deploy branch (including merging to main).                                       |
-| Monitoring  | Access query history                | View deployment query history, performance, and traces.                                                                                                                   |
+| Data Model  | Access SQL Runner                   | Open the SQL Runner and run queries in it.                                                                                                                                |
+| AI          | Access AI agents                    | Use the AI agent in Analytics Chat, workbooks, the IDE, and dashboards.                                                                                                   |
 | Data Export | Download data                       | Download query results as CSV from workbooks, Analytics Chat, and published dashboards. Granted by default to the built-in Viewer, Explorer, and Developer roles. See [Data download controls][ref-data-download-controls]. |
+| Monitoring  | Access query history                | View deployment query history, performance, and traces.                                                                                                                   |
+| Pre-aggregations | Build pre-aggregations         | Trigger pre-aggregation builds, including **Build all** and bulk builds. Removing it prevents accidental large builds.                                                     |
 
 When **Full access** is checked, the granular checkboxes appear checked and disabled — granting Full access today also covers any deployment-scoped permissions added in the future.
 
 {/* TODO: Upload screenshot of a deployment policy card with "Full access" checked, granular checkboxes shown checked + disabled */}
 
 <Tip>
 
-**Access deployment** (`DeploymentRead`) and **Download data** (`DownloadData`) are special. They are the only deployment actions that do **not** auto-bump the Base Role to Developer, because Viewers also need them just to open a deployment and download data from it.
+**Access deployment** (`DeploymentRead`), **Access AI agents** (`DeploymentAgentRead`), and **Download data** (`DownloadData`) are special. They are the only deployment actions that do **not** auto-bump the Base Role to Developer, because Viewers also need them to open a deployment, use AI chat, and download data from it.
 
 </Tip>
 
@@ -169,7 +172,7 @@ For an analyst who works in one deployment.
     Add a deployment policy, switch **Scope** to **Specific deployments**, and pick the relevant deployment(s) from the picker.
   </Step>
   <Step title="Pick actions">
-    Check **Access deployment** so the user can open the deployment, and add **Access query history** if they should see query performance.
+    Check **Access deployment** so the user can open the deployment. Add **Access AI agents** or **Download data** if they need them — those three are the actions an Explorer can hold. Anything else, **Access query history** included, forces the Base Role up to Developer.
   </Step>
   <Step title="Save">
     Click **Create**.
@@ -254,5 +257,8 @@ This section lists every action a custom role can grant. The internal action nam
 | `SchemaRead`              | View data model                                             |
 | `SchemaUpdate`            | Edit data model                                             |
 | `SchemaUpdateDevBranches` | Edit data model on dev branches                             |
-| `APMRead`                 | Access query history                                        |
+| `SqlRunnerRead`           | Access SQL Runner                                           |
+| `DeploymentAgentRead`     | Access AI agents                                            |
 | `DownloadData`            | Download data                                               |
+| `APMRead`                 | Access query history                                        |
+| `PreAggregationBuild`     | Build pre-aggregations                                      |
@@ -41,7 +41,7 @@ All three vertical variants are also available horizontally. Horizontal bars wor
 
 ### Composite (bar + line)
 
-Assign one series to the right Y axis and set its mark type to **Line** in [series configuration](/docs/explore-analyze/charts/configuration/series-configuration). This creates a dual-axis chart — useful for overlaying a rate on top of volume data (e.g. order count as bars, revenue per order as a line).
+Press **+ Y Axis** on the Fields tab to add a second layer, assign it to the right Y axis, and set its mark type to **Line** in [series configuration](/docs/explore-analyze/charts/configuration/series-configuration). This creates a dual-axis chart — useful for overlaying a rate on top of volume data (e.g. order count as bars, revenue per order as a line).
 
 {/* Screenshot: composite bar+line chart with dual Y axes — order count (bars, left axis) and average order value (line, right axis). Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 

@@ -15,7 +15,7 @@ One measure plotted against a time or ordered dimension. The simplest and most c
 
 ### Multi-series
 
-Multiple lines plotted on the same axes. Map a second dimension to the **Color** channel to split one measure into one line per dimension value, or add multiple measures to the Y axis to plot them as separate series.
+Multiple lines plotted on the same axes. Map a second dimension to the **Color** channel to split one measure into one line per dimension value, or query several measures to plot each as its own series.
 
 {/* Screenshot: multi-series line chart — order count by week, split by order status (3–4 colored lines). Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 
@@ -39,4 +39,4 @@ Line charts use a temporal X axis for time dimensions — continuous, time-aware
 
 ## Combining with bars
 
-To layer a line on top of a bar chart, add a second series to the Y axis, set its mark type to **Line** in [series configuration](/docs/explore-analyze/charts/configuration/series-configuration), and assign it to the right Y axis for a dual-axis layout.
+To layer a line on top of a bar chart, press **+ Y Axis** on the Fields tab to add a second layer, set its mark type to **Line** in [series configuration](/docs/explore-analyze/charts/configuration/series-configuration), and assign it to the right Y axis for a dual-axis layout.
@@ -39,7 +39,7 @@ A point map requires:
 
 Optional:
 
-- **Size** — numeric measure that scales point radius proportionally.
+- **Custom size** — numeric measure that scales point radius proportionally.
 - **Color** — dimension or measure that colors points by category or value.
 
 ### Point color
@@ -48,7 +48,7 @@ When no **Color** field is assigned, all points render in the configurable **Def
 
 ### Point size
 
-Assign a numeric measure to the **Size** channel to scale point radius by value. The size range (minimum and maximum radius in pixels) is configurable in the settings panel.
+When no **Custom size** measure is assigned, every point renders at the configurable **Default size**. Assign a measure to **Custom size** to scale each point's radius by its value instead.
 
 ### Clustering
 

@@ -25,6 +25,18 @@ Drag the **Inner radius** slider in the Style tab or enter a pixel value. Settin
 
 {/* Screenshot: Style tab with the Inner radius control highlighted. Place inline, 50% width, right-aligned. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 
+## Rings
+
+A pie's **Fields** tab is its own panel, not the X/Y/Color channels the other chart types use. It has three controls:
+
+| Control | What it sets |
+|---|---|
+| **Rings** | The dimensions the circle is divided by, innermost first. With one dimension you get a plain pie; add more and each becomes an outer ring, subdividing the ring inside it. Drag to reorder |
+| **Measure** | The measure whose values set each slice's arc length |
+| **Tooltips** | The fields shown on hover — see [tooltips](/docs/explore-analyze/charts/configuration/tooltips) |
+
+The innermost ring doubles as the color dimension, so reordering the rings also changes what the slices are colored by.
+
 ## Color and slice ordering
 
 Slices are colored using the active [color palette](/docs/explore-analyze/charts/configuration/color-and-stacking) in palette order, matched to the sort order of your query results. To change which slice appears first, adjust the sort in the results table.
@@ -19,17 +19,13 @@ Map a dimension to the **Color** channel to assign each point a color by categor
 
 {/* Screenshot: scatter chart — same axes, points colored by traffic source (4–5 colors). Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 
-### With size encoding
-
-Map a third numeric measure to the **Size** channel to scale each point's radius by value. Use this to encode a third variable without adding a new axis.
-
-{/* Screenshot: scatter chart with sized and colored points — average order value (X), return rate (Y), total revenue as size, colored by category. Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
-
 ## Size encoding
 
-Assign a measure to the **Size** channel in the Fields tab. Points scale proportionally to the measure value. Configure the minimum and maximum radius in the Style tab.
+The Fields tab has no **Size** channel: it offers X, Y, Color, tooltips, data labels, and small multiples. To scale each point's radius by a third measure, add a `size` encoding to the chart's Vega specification with the spec editor.
+
+Once the specification has a `size` encoding, a **Size** section appears on the Style tab, where its legend can be configured like the color legend.
 
-{/* Screenshot: Fields tab with Size channel assigned — showing the size field token. Place inline, 50% width, right-aligned. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
+{/* Screenshot: scatter chart with sized and colored points — average order value (X), return rate (Y), total revenue as size, colored by category. Place directly below this heading, full-width. (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 
 ## Tooltips
 

@@ -36,7 +36,7 @@ The **Axes** section in the Style tab controls the appearance and behavior of th
 Add a second Y axis on the right side of the chart to plot a series on a different scale. This is useful for combining measures with different units or magnitudes — for example, showing order count on the left axis and average order value on the right.
 
 To use the right axis:
-1. In the **Series configuration** for a specific series, change the **Y axis** assignment from **Left** to **Right**.
+1. Press **+ Y Axis** on the Fields tab to add a [Y-axis layer](/docs/explore-analyze/charts/configuration/series-configuration), then change its **Y axis** assignment from **Left** to **Right**.
 2. The right axis settings appear in the Style tab — configure its title, labels, and scale independently from the left axis.
 
 {/* TODO screenshot: dual-axis chart with bar on left axis and line on right axis (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}

@@ -47,9 +47,11 @@ If none of the provided palettes fit your needs, you can build a custom palette
 
 To reuse a custom palette across charts, copy the hex codes and paste them into the custom palette editor of another chart.
 
-## Series color controls
+## Mark color
 
-When no Color channel is assigned (single measure, no color-by), each series gets an individual color picker in the **Series** section of the Style tab. Click the color swatch next to a series to change its color.
+When no Color channel is assigned (a single measure, no color-by dimension), the **Style** tab offers a color swatch for the chart's mark on bar and line charts. Click it to pick a color.
+
+Once a Color channel is active the swatch is not shown — including in [multi-series mode](/docs/explore-analyze/charts/configuration/series-mapping), where the channel is pinned to **Series**. Colors then come from the palette above, assigned to each series by its position in the list.
 
 ## Stacking options
 

@@ -7,8 +7,8 @@ The chart configuration panel has two tabs — **Fields** and **Style** — avai
 
 | Page | What it covers |
 |---|---|
-| [Series mapping](/docs/explore-analyze/charts/configuration/series-mapping) | Assigning query columns to chart channels (X, Y, color, size, tooltip) |
-| [Series configuration](/docs/explore-analyze/charts/configuration/series-configuration) | Per-series mark type, color, and individual display options |
+| [Series mapping](/docs/explore-analyze/charts/configuration/series-mapping) | Assigning query columns to chart channels (X, Y, color, small multiples, tooltip) |
+| [Series configuration](/docs/explore-analyze/charts/configuration/series-configuration) | Mark type, axis assignment, and display options per Y-axis layer |
 | [Color & stacking](/docs/explore-analyze/charts/configuration/color-and-stacking) | Color palettes, stacking mode, stacked segment sorting, and legend placement |
 | [Small multiples](/docs/explore-analyze/charts/configuration/small-multiples) | Splitting a chart into a grid of panels, one per value of a dimension |
 | [Axes](/docs/explore-analyze/charts/configuration/axes) | Axis titles, grid lines, label formatting, dual Y-axis, and reference lines |

@@ -1,9 +1,11 @@
 ---
 title: Series configuration
-description: Configure individual series — mark type, color, and display options — independently from the global chart settings.
+description: Configure Y-axis layers — mark type, axis assignment, stacking, and data labels — independently from the global chart settings.
 ---
 
-Series configuration lets you override chart settings on a per-series basis. Access it from the **Fields** tab by expanding an individual series in the Y-axis section.
+Series configuration applies to a chart built from **Y-axis layers**. Below the Y channel on the **Fields** tab there is a **+ Y Axis** button; each press adds a layer with its own fields, mark type, and axis assignment. It is not a channel dropdown, and it is offered only when the X axis is categorical or time-based and the chart is neither a heatmap, a boxplot, nor [split into small multiples](/docs/explore-analyze/charts/configuration/small-multiples).
+
+A chart can also carry several series without layers, when the query itself returns more than one measure. That is [multi-series mode](/docs/explore-analyze/charts/configuration/series-mapping), and its measures are listed in a **Series** section whose rows carry no settings of their own — so the settings on this page are never per-measure. With no layers there is nothing to override: data labels, stacking, and color come from the global [data labels](/docs/explore-analyze/charts/configuration/data-labels) and [color & stacking](/docs/explore-analyze/charts/configuration/color-and-stacking) settings, and mark type and axis assignment do not apply at all — every series is drawn with the chart's own mark, on its one Y axis. Add a layer and it gets its own mark type, Y axis assignment, data labels, and stacking. **Which one you are in is visible on the Fields tab**: a layer is a repeat of the whole set of Fields controls, with its own mark type and axis assignment, while multi-series is a **Series** list inside one such set. The two can coexist, so a layer can itself be in multi-series mode.
 
 {/* TODO screenshot: series configuration panel expanded for one series (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 
@@ -18,18 +20,16 @@ Available mark types per series:
 - **Scatter** (point)
 
 To create a bar + line chart:
-1. Add two measures to the Y axis.
-2. Expand the second series in the Fields tab.
+1. Click **+ Y Axis** on the Fields tab to add a second layer.
+2. Pick the measure it should plot.
 3. Set its mark type to **Line**.
 4. Optionally assign it to the **Right Y axis** in the same panel (see [Axes](/docs/explore-analyze/charts/configuration/axes)).
 
 {/* TODO screenshot: second series with mark type set to Line (hidden — replace this comment with <Frame><img src="..." /></Frame> when image is ready) */}
 
-## Series color
-
-When no **Color** channel is assigned (single-color charts with no color-by dimension), each series has an individual color picker. Click the color swatch to open the picker and set a custom color for that series.
+## Color
 
-This setting has no effect when a Color channel is active — in that case, colors are managed by the palette in [Color & stacking](/docs/explore-analyze/charts/configuration/color-and-stacking).
+Color is not set per layer. It is a chart-level control on the **Style** tab, and only when no Color channel is assigned — see [mark color](/docs/explore-analyze/charts/configuration/color-and-stacking).
 
 ## Y axis assignment