docs(databricks): require Databricks SQL Access and Workspace Access entitlements - #39209
Open
charlesmyu wants to merge 3 commits into
Open
docs(databricks): require Databricks SQL Access and Workspace Access entitlements#39209charlesmyu wants to merge 3 commits into
charlesmyu wants to merge 3 commits into
Conversation
…entitlements in Permissions section
charlesmyu
force-pushed
the
charlesyu/databricks-permissions-entitlements
branch
from
August 14, 2026 21:00
2cc57b7 to
fa59b43
Compare
charlesmyu
marked this pull request as ready for review
August 14, 2026 21:01
Contributor
Preview links (active after the
|
janine-c
approved these changes
Aug 14, 2026
janine-c
left a comment
janine-c
left a comment
Contributor
There was a problem hiding this comment.
Hey Charles, this looks great! Just some really minor suggestions/questions but no blockers. Feel free to ping me if you have any questions!
Comment on lines
+465
to
+466
| - {{< ui >}}Databricks SQL access{{< /ui >}} | ||
| - {{< ui >}}Workspace access{{< /ui >}} |
Contributor
There was a problem hiding this comment.
Suggested change
| - {{< ui >}}Databricks SQL access{{< /ui >}} | |
| - {{< ui >}}Workspace access{{< /ui >}} | |
| - {{< ui >}}Workspace access{{< /ui >}} | |
| - {{< ui >}}Databricks SQL access{{< /ui >}} |
Super nitpicky, but I can see that these are in the opposite order elsewhere in the file, and parallelism is just so satisfying (and can make docs easier to act on for users!)
| - **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 | |
Contributor
There was a problem hiding this comment.
Should the links in this table be moved to the Object column rather than the Permission column? It looks like they all go to pages about the objects rather than the permissions. If there's more nuance here, then disregard!
jhgilbert
added
the
astro-reorg-no-conflicts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a note to the Permissions section (Advanced Configuration) of the Jobs Monitoring for Databricks page stating that the connecting user or service principal must have the Databricks SQL Access and Workspace Access workspace entitlements enabled, in addition to the other permissions already listed there.
This requirement applies regardless of whether Workspace Admin privileges or the granular workspace-level permissions are granted, so it is surfaced as an info callout at the top of the section.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
AI-assisted draft; content manually reviewed.
Additional notes