Default ACL for Jobs and Clusters

murtadha_s — Thu, 02 Apr 2026 13:37:19 GMT

Hi,

I want to set default ACL that applies to all created jobs and clusters, according to a cluster policy for example, but currently I need to apply my ACL at every created job/cluster separately.

is there a way to do that?

BR,

Re: Default ACL for Jobs and Clusters

Ashwin_DSA — Thu, 02 Apr 2026 15:13:36 GMT

Hi @murtadha_s

Can you please clarify what you are after? The second part of your question sounded more like a statement: "but currently I need to apply my ACL at every created job/cluster separately," and that confused me a bit.

To make sure we point you to the best option... how are you creating your jobs and clusters today (UI, REST, Terraform, bundles), and what default ACL behaviour are you trying to enforce (for example, always granting a specific group CAN_VIEW or CAN_MANAGE)?

Just so that you know, there isn’t currently a way to define a workspace‑wide "default ACL" for all new jobs and clusters via cluster policies. Policies control which config options users can set (instance types, runtime, autoscaling, etc.), but they don’t set object permissions.

When it comes to Jobs, if Job ACLs are enabled in the workspace, you can pass an access_control_list when creating jobs through the REST API/SDK (/api/2.1/jobs/create or /jobs/runs/submit). That lets you apply a consistent ACL pattern at creation time. The job’s ACLs also govern the associated job clusters, so you don’t need a separate ACL template for those.

For all‑purpose (interactive) clusters, there’s no built‑in default ACL template. The usual approach is to enforce a pattern via the Permissions API / Terraform / Databricks bundles when clusters are created, rather than via cluster policy.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

topic Re: Default ACL for Jobs and Clusters in Data Engineering

Default ACL for Jobs and Clusters

Re: Default ACL for Jobs and Clusters