<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Is there a setting which restricts users from Creating Job and Pipeline? in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/64540#M1003</link>
    <description>&lt;P&gt;as far i know currently ((as of 03-25-2024) databricks don't any workspace admin settings option to restrict users from creating a workflow/job or delta pipelines.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the use case for it&amp;nbsp;Example: you have 3 tier landscape Dev, Qa and Prod.&lt;/P&gt;&lt;P&gt;It is ok for users to create workflows/jobs and pipelines in dev but there is no need for them to create in QA and production but as an admin we can't restrict users from creating.&lt;/P&gt;&lt;P&gt;If anyone else out there feels same. Unbale to restrict could have below disadvantages.&lt;/P&gt;&lt;P&gt;1. There could lot unnecessary jobs and if user base large there could be many workflows.&lt;/P&gt;&lt;P&gt;2. Let's assume user has read access to data and access to all purpose cluster/SQL warehouse, user can schedule a workflow. as admin we expect user not to do it but admin won't be able to restrict. This could incur cost.&lt;/P&gt;&lt;P&gt;There could workarounds like scheduling a job to delete workflows which are created by users, but it would be good to have this feature.&lt;/P&gt;</description>
    <pubDate>Mon, 25 Mar 2024 18:49:57 GMT</pubDate>
    <dc:creator>Avvar2022</dc:creator>
    <dc:date>2024-03-25T18:49:57Z</dc:date>
    <item>
      <title>Is there a setting which restricts users from Creating Job and Pipeline?</title>
      <link>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/64540#M1003</link>
      <description>&lt;P&gt;as far i know currently ((as of 03-25-2024) databricks don't any workspace admin settings option to restrict users from creating a workflow/job or delta pipelines.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the use case for it&amp;nbsp;Example: you have 3 tier landscape Dev, Qa and Prod.&lt;/P&gt;&lt;P&gt;It is ok for users to create workflows/jobs and pipelines in dev but there is no need for them to create in QA and production but as an admin we can't restrict users from creating.&lt;/P&gt;&lt;P&gt;If anyone else out there feels same. Unbale to restrict could have below disadvantages.&lt;/P&gt;&lt;P&gt;1. There could lot unnecessary jobs and if user base large there could be many workflows.&lt;/P&gt;&lt;P&gt;2. Let's assume user has read access to data and access to all purpose cluster/SQL warehouse, user can schedule a workflow. as admin we expect user not to do it but admin won't be able to restrict. This could incur cost.&lt;/P&gt;&lt;P&gt;There could workarounds like scheduling a job to delete workflows which are created by users, but it would be good to have this feature.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 18:49:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/64540#M1003</guid>
      <dc:creator>Avvar2022</dc:creator>
      <dc:date>2024-03-25T18:49:57Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a setting which restricts users from Creating Job and Pipeline?</title>
      <link>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/72090#M1260</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;&amp;nbsp;- How can I initiate a product enhancement request?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 19:41:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/72090#M1260</guid>
      <dc:creator>Avvar2022</dc:creator>
      <dc:date>2024-06-07T19:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a setting which restricts users from Creating Job and Pipeline?</title>
      <link>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/74805#M1291</link>
      <description>&lt;P&gt;We face the same situation as the OP and are likewise missing such a feature. In my opinion this limits Databricks' platform capabilities (speaking from the perspective of a platform team that intends to provide Databricks workspaces as a service to internal consumers).&lt;/P&gt;&lt;P&gt;A great solution would be the possibility to define workspace-wide policies, and one example directed to the OPs and my situation could be defining a policy that restrict the possible owners of workflows, as in "Only this or that principal (user/ group/ service principal) may create/own workflows". While we're at that, why not also a policy to restrict the possible "run as" principals for a workflow?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 08:23:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/74805#M1291</guid>
      <dc:creator>camilo_s</dc:creator>
      <dc:date>2024-06-18T08:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a setting which restricts users from Creating Job and Pipeline?</title>
      <link>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/74806#M1292</link>
      <description>&lt;P&gt;&amp;nbsp;I notice that a separate discussion overlaps with the OPs issue:&amp;nbsp;&lt;A href="https://community.databricks.com/t5/data-engineering/restricting-workflow-creation-and-implementing-approval/td-p/4336" target="_blank"&gt;https://community.databricks.com/t5/data-engineering/restricting-workflow-creation-and-implementing-approval/td-p/4336&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;&amp;nbsp;do you have a mechanism for clustering discussions for contributors to have a better view of existing topics and Databricks to know which major topics its customers occupy with?&lt;/P&gt;&lt;P&gt;I'm thinking about issue tracking in GitHub, where moderators often track topics in a single GitHub issue, closing related ones and referring them to the single issue.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 08:29:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/is-there-a-setting-which-restricts-users-from-creating-job-and/m-p/74806#M1292</guid>
      <dc:creator>camilo_s</dc:creator>
      <dc:date>2024-06-18T08:29:38Z</dc:date>
    </item>
  </channel>
</rss>

