diff --git a/hugo/content/en/data_observability/jobs_monitoring/databricks/_index.md b/hugo/content/en/data_observability/jobs_monitoring/databricks/_index.md
index d17fcd9aa4b..25c9695201f 100644
--- a/hugo/content/en/data_observability/jobs_monitoring/databricks/_index.md
+++ b/hugo/content/en/data_observability/jobs_monitoring/databricks/_index.md
@@ -460,17 +460,27 @@ DD_LOGS_CONFIG_PROCESSING_RULES=[{\"type\": \"exclude_at_match\",\"name\": \"dro
 ```
 
 ### Permissions
-Grant {{< ui >}}Workspace Admin{{< /ui >}} privileges to the user or service principal that connects to your Databricks workspace. This allows Datadog to manage init script installations and updates automatically, reducing the risk of misconfiguration.
+The user or service principal that connects to your Databricks workspace must have the following workspace entitlements enabled, in addition to the permissions described below:
 
-If you need more granular control, grant these minimal permissions to the following [workspace level objects][19] to still be able to monitor all jobs, clusters, and queries within a workspace:
+- {{< ui >}}Workspace access{{< /ui >}}
+- {{< ui >}}Databricks SQL access{{< /ui >}}
 
-| Object                 | Permission                                                                                                                                                      |
-|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Job                              | [CAN VIEW][20]
-| Compute                          | [CAN ATTACH TO][21]
-| Lakeflow Declarative Pipelines   | [CAN VIEW][22]
-| Query                            | [CAN VIEW][23]
-| SQL warehouse                    | [CAN MONITOR][24]
+#### Workspace permissions
+
+Choose one of the following approaches for the user or service principal:
+
+- **Workspace Admin privileges** (recommended): Grant {{< ui >}}Workspace Admin{{< /ui >}} privileges. This allows Datadog to manage init script installations and updates automatically, reducing the risk of misconfiguration.
+- **Granular permissions**: If you need more granular control, grant these minimal permissions to the following [workspace level objects][19] to still be able to monitor all jobs, clusters, and queries within a workspace:
+
+  | Object                 | Permission                                                                                                                                                      |
+  |--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+  | [Job][20]                              | CAN VIEW
+  | [Compute][21]                          | CAN ATTACH TO
+  | [Lakeflow Declarative Pipelines][22]   | CAN VIEW
+  | [Query][23]                            | CAN VIEW
+  | [SQL warehouse][24]                    | CAN MONITOR
+
+#### Cost data permissions
 
 Additionally, for Datadog to access your Databricks cost data in Data Observability: Jobs Monitoring or [Cloud Cost Management][26], the user or service principal used to query [system tables][27] must have the following permissions:
    - `CAN USE` permission on the SQL Warehouse.