metabase · github-automation-metabase · Aug 28, 2026
diff --git a/_docs/latest/api.json b/_docs/latest/api.json
@@ -25315,7 +25315,7 @@
       "post" : {
         "operationId" : "post-api-ee-ai-controls-permissions-advanced",
         "summary" : "POST /api/ee/ai-controls/permissions/advanced",
-        "description" : "Switch to advanced group-level permissions. Removes any custom permissions from the All Users group.",
+        "description" : "Switch to group-level permissions. Removes the permissions of All Users and All tenant users, so nobody has\n   access until they are in a group that grants it.",
         "parameters" : [ ],
         "responses" : {
           "2XX" : {
@@ -25367,7 +25367,7 @@
       "delete" : {
         "operationId" : "delete-api-ee-ai-controls-permissions-advanced",
         "summary" : "DELETE /api/ee/ai-controls/permissions/advanced",
-        "description" : "Switch back to simple permissions. Removes any custom permissions from all specific groups, keeping only Admins and All Users.",
+        "description" : "Switch back to simple permissions. Removes the permissions of every group other than Administrators, All Users\n   and All tenant users.",
         "parameters" : [ ],
         "responses" : {
           "2XX" : {

diff --git a/_docs/latest/developers-guide/api-changelog.md b/_docs/latest/developers-guide/api-changelog.md
@@ -13,12 +13,45 @@ latest: true
 
 # Breaking changes to the API interface
 
+## Metabase 0.63.15
+
+- `POST /api/slack/bug-report` now requires bug reporting to be enabled (`MB_BUG_REPORTING_ENABLED`).
+  `diagnosticInfo.reporter` is now a boolean: `true` attributes the report to the authenticated user, `false` (or
+  omitting it) submits the report anonymously. The previous `{ "name": ..., "email": ... }` object is still accepted
+  and treated as `true`; the name and email in it are ignored. The request body is validated against a fixed set of
+  keys; undeclared keys are dropped.
+
+## Metabase 0.62.18
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
+## Metabase 0.61.20
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
 ## Metabase 0.61.0
 
 - `POST /api/metabot/describe/card` and `POST /api/metabot/describe/dashboard/:id` have been removed. These endpoints
   provided LLM-powered autodescription of cards and dashboards using the legacy OpenAI client. This functionality has
   been superseded by the Metabot agent.
 
+## Metabase 0.60.26
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
+## Metabase 0.59.30
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
+## Metabase 0.58.32
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
 ## Metabase 0.57.0
 
 - MBQL queries (in Cards and elsewhere) are now serialized as MBQL 5 as opposed to MBQL 4 (aka legacy MBQL) in the

diff --git a/_docs/latest/embedding/eajs/snippets/MetabaseBrowserAttributes.md b/_docs/latest/embedding/eajs/snippets/MetabaseBrowserAttributes.md
@@ -28,16 +28,16 @@ Pro/Enterprise
 
 <!-- [<snippet properties>] -->
 
-| Property                                                             | Type                 | Description                                                                                                                                                                                                                                                  |
-| :------------------------------------------------------------------- | :------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <a id="collection-entity-types"></a> `collection-entity-types`       | `string`[]           | An array of entity types to show in the collection browser: `collection`, `dashboard`, `question`, `model`.<br>---<br>Optional<br>Possible values: `"model"`, `"collection"`, `"dashboard"`, `"question"`                                                    |
-| <a id="collection-page-size"></a> `collection-page-size`             | `number`             | How many items to show per page in the collection browser.<br>---<br>Optional                                                                                                                                                                                |
-| <a id="collection-visible-columns"></a> `collection-visible-columns` | `string`[]           | An array of columns to show in the collection browser: `type`, `name`, `description`, `lastEditedBy`, `lastEditedAt`, `archive`.<br>---<br>Optional<br>Possible values: `"type"`, `"name"`, `"description"`, `"lastEditedBy"`, `"lastEditedAt"`, `"archive"` |
-| <a id="data-picker-entity-types"></a> `data-picker-entity-types`     | `string`[]           | An array of entity types to show in the question's data picker: `model`, `table`.<br>---<br>Optional<br>Possible values: `"model"`, `"table"`                                                                                                                |
-| <a id="enable-entity-navigation"></a> `enable-entity-navigation`     | `boolean`            | Whether to enable internal entity navigation (links to dashboards/questions).<br>---<br>Optional<br>Default: `false`                                                                                                                                         |
-| <a id="initial-collection"></a> `initial-collection`                 | `string` \| `number` | Which collection to start from. Use a collection ID (e.g., `14`) to start in a specific collection, or `"root"` for the top-level "Our Analytics" collection.                                                                                                |
-| <a id="read-only"></a> `read-only`                                   | `boolean`            | Whether the content manager is in read-only mode. When `true`, people can interact with items (filter, summarize, drill-through) but can't save. When `false`, they can create and edit items.<br>---<br>Optional<br>Default: `true`                         |
-| <a id="with-new-dashboard"></a> `with-new-dashboard`                 | `boolean`            | Whether to show the "New dashboard" button. Only applies when `read-only` is `false`.<br>---<br>Optional<br>Default: `true`                                                                                                                                  |
-| <a id="with-new-question"></a> `with-new-question`                   | `boolean`            | Whether to show the "New question" button.<br>---<br>Optional<br>Default: `true`                                                                                                                                                                             |
+| Property                                                             | Type                 | Description                                                                                                                                                                                                                                                                              |
+| :------------------------------------------------------------------- | :------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <a id="collection-entity-types"></a> `collection-entity-types`       | `string`[]           | An array of entity types to show in the collection browser: `collection`, `dashboard`, `question`, `model`.<br>---<br>Optional<br>Possible values: `"model"`, `"collection"`, `"dashboard"`, `"question"`                                                                                |
+| <a id="collection-page-size"></a> `collection-page-size`             | `number`             | How many items to show per page in the collection browser.<br>---<br>Optional                                                                                                                                                                                                            |
+| <a id="collection-visible-columns"></a> `collection-visible-columns` | `string`[]           | An array of columns to show in the collection browser: `type`, `name`, `description`, `lastEditedBy`, `lastEditedAt`, `archive`.<br>---<br>Optional<br>Possible values: `"type"`, `"name"`, `"description"`, `"lastEditedBy"`, `"lastEditedAt"`, `"archive"`                             |
+| <a id="data-picker-entity-types"></a> `data-picker-entity-types`     | `string`[]           | An array of entity types to show in the question's data picker: `model`, `table`.<br>---<br>Optional<br>Possible values: `"model"`, `"table"`                                                                                                                                            |
+| <a id="enable-entity-navigation"></a> `enable-entity-navigation`     | `boolean`            | Whether to enable internal entity navigation (links to dashboards/questions).<br>---<br>Optional<br>Default: `false`                                                                                                                                                                     |
+| <a id="initial-collection"></a> `initial-collection`                 | `string` \| `number` | Which collection to start from. Values: regular ID, entity ID, `"root"` for the top-level "Our Analytics" collection, `"personal"` for the viewer's personal collection, or `"tenant"` for the viewer's tenant collection. People who aren't tenant members get an error for `"tenant"`. |
+| <a id="read-only"></a> `read-only`                                   | `boolean`            | Whether the content manager is in read-only mode. When `true`, people can interact with items (filter, summarize, drill-through) but can't save. When `false`, they can create and edit items.<br>---<br>Optional<br>Default: `true`                                                     |
+| <a id="with-new-dashboard"></a> `with-new-dashboard`                 | `boolean`            | Whether to show the "New dashboard" button. Only applies when `read-only` is `false`.<br>---<br>Optional<br>Default: `true`                                                                                                                                                              |
+| <a id="with-new-question"></a> `with-new-question`                   | `boolean`            | Whether to show the "New question" button.<br>---<br>Optional<br>Default: `true`                                                                                                                                                                                                         |
 
 <!-- [<endsnippet properties>] -->
diff --git a/_docs/v0.62/developers-guide/api-changelog.md b/_docs/v0.62/developers-guide/api-changelog.md
@@ -11,12 +11,40 @@ layout: new-docs
 
 # Breaking changes to the API interface
 
+## Metabase 0.62.18
+
+- `POST /api/slack/bug-report` now requires bug reporting to be enabled (`MB_BUG_REPORTING_ENABLED`).
+  `diagnosticInfo.reporter` is now a boolean: `true` attributes the report to the authenticated user, `false` (or
+  omitting it) submits the report anonymously. The previous `{ "name": ..., "email": ... }` object is still accepted
+  and treated as `true`; the name and email in it are ignored. The request body is validated against a fixed set of
+  keys; undeclared keys are dropped.
+
+## Metabase 0.61.20
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.62.18 entry.
+
 ## Metabase 0.61.0
 
 - `POST /api/metabot/describe/card` and `POST /api/metabot/describe/dashboard/:id` have been removed. These endpoints
   provided LLM-powered autodescription of cards and dashboards using the legacy OpenAI client. This functionality has
   been superseded by the Metabot agent.
 
+## Metabase 0.60.26
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.62.18 entry.
+
+## Metabase 0.59.30
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.62.18 entry.
+
+## Metabase 0.58.32
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.62.18 entry.
+
 ## Metabase 0.57.0
 
 - MBQL queries (in Cards and elsewhere) are now serialized as MBQL 5 as opposed to MBQL 4 (aka legacy MBQL) in the

diff --git a/_docs/v0.63/api.json b/_docs/v0.63/api.json
@@ -25315,7 +25315,7 @@
       "post" : {
         "operationId" : "post-api-ee-ai-controls-permissions-advanced",
         "summary" : "POST /api/ee/ai-controls/permissions/advanced",
-        "description" : "Switch to advanced group-level permissions. Removes any custom permissions from the All Users group.",
+        "description" : "Switch to group-level permissions. Removes the permissions of All Users and All tenant users, so nobody has\n   access until they are in a group that grants it.",
         "parameters" : [ ],
         "responses" : {
           "2XX" : {
@@ -25367,7 +25367,7 @@
       "delete" : {
         "operationId" : "delete-api-ee-ai-controls-permissions-advanced",
         "summary" : "DELETE /api/ee/ai-controls/permissions/advanced",
-        "description" : "Switch back to simple permissions. Removes any custom permissions from all specific groups, keeping only Admins and All Users.",
+        "description" : "Switch back to simple permissions. Removes the permissions of every group other than Administrators, All Users\n   and All tenant users.",
         "parameters" : [ ],
         "responses" : {
           "2XX" : {

diff --git a/_docs/v0.63/developers-guide/api-changelog.md b/_docs/v0.63/developers-guide/api-changelog.md
@@ -11,12 +11,45 @@ layout: new-docs
 
 # Breaking changes to the API interface
 
+## Metabase 0.63.15
+
+- `POST /api/slack/bug-report` now requires bug reporting to be enabled (`MB_BUG_REPORTING_ENABLED`).
+  `diagnosticInfo.reporter` is now a boolean: `true` attributes the report to the authenticated user, `false` (or
+  omitting it) submits the report anonymously. The previous `{ "name": ..., "email": ... }` object is still accepted
+  and treated as `true`; the name and email in it are ignored. The request body is validated against a fixed set of
+  keys; undeclared keys are dropped.
+
+## Metabase 0.62.18
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
+## Metabase 0.61.20
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
 ## Metabase 0.61.0
 
 - `POST /api/metabot/describe/card` and `POST /api/metabot/describe/dashboard/:id` have been removed. These endpoints
   provided LLM-powered autodescription of cards and dashboards using the legacy OpenAI client. This functionality has
   been superseded by the Metabot agent.
 
+## Metabase 0.60.26
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
+## Metabase 0.59.30
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
+## Metabase 0.58.32
+
+- `POST /api/slack/bug-report`: `diagnosticInfo.reporter` is now a boolean and bug reporting must be enabled. See the
+  0.63.15 entry.
+
 ## Metabase 0.57.0
 
 - MBQL queries (in Cards and elsewhere) are now serialized as MBQL 5 as opposed to MBQL 4 (aka legacy MBQL) in the