<?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 🔐 How Do I Prevent Users from Accidentally Deleting Tables in Unity Catalog? 🔐 in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/121424#M443</link>
    <description>&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":question_mark:"&gt;❓&lt;/span&gt; &lt;STRONG&gt;Question:&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;I have a role called dev-dataengineer with the following privileges on the catalog dap_catalog_dev:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;APPLY TAG&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE FUNCTION&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE MATERIALIZED VIEW&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE TABLE&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE VOLUME&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;EXECUTE&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;READ VOLUME&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;REFRESH&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;SELECT&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;USE SCHEMA&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;WRITE VOLUME&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Despite this, users are still able to &lt;STRONG&gt;delete/drop tables&lt;/STRONG&gt; within dap_catalog_dev.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":question_mark:"&gt;❓&lt;/span&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;:&lt;/H3&gt;&lt;P&gt;&lt;STRONG&gt;Why are users still able to delete tables, and how can I restrict this behavior so that table deletion is not allowed?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I want to ensure that users can read and create tables if needed, but not delete them&lt;/P&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; &lt;STRONG&gt;Answer:&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;Great question — and one that's crucial for &lt;STRONG&gt;data governance and table protection&lt;/STRONG&gt; in shared environments!&lt;/P&gt;&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":prohibited:"&gt;🚫&lt;/span&gt; Why Users Can Still Delete Tables&lt;/H2&gt;&lt;P&gt;&lt;STRONG&gt;CREATE TABLE on a catalog&lt;/STRONG&gt; allows users to create AND drop their own tables, unless further restricted.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":locked_with_key:"&gt;🔐&lt;/span&gt; &lt;STRONG&gt;How to Prevent Table Deletion&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;To prevent accidental or unauthorized table deletion:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Avoid granting DROP, MODIFY, or ALL PRIVILEGES&lt;/STRONG&gt; at the catalog or schema level.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Grant CREATE TABLE only at the schema level&lt;/STRONG&gt;, not the catalog level — this scopes table creation to specific areas.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Restrict OWNERSHIP&lt;/STRONG&gt; transfer, as object owners can drop their own tables regardless of other permissions.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Review and manage privileges regularly&lt;/STRONG&gt; using SHOW GRANTS.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Fix - That Worked for mea nd eventually for all&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Audit all roles (not just dev-dataengineer) and users for:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;DROP, MODIFY, or ALL PRIVILEGES&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE TABLE permissions granted at higher scopes (e.g., catalog)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;You can run something like:&lt;/P&gt;&lt;PRE&gt;SHOW GRANTS ON SCHEMA dap_catalog_dev;&lt;BR /&gt;SHOW GRANTS ON CATALOG dap_catalog_dev;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jun 2025 04:14:50 GMT</pubDate>
    <dc:creator>CURIOUS_DE</dc:creator>
    <dc:date>2025-06-11T04:14:50Z</dc:date>
    <item>
      <title>🔐 How Do I Prevent Users from Accidentally Deleting Tables in Unity Catalog? 🔐</title>
      <link>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/121424#M443</link>
      <description>&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":question_mark:"&gt;❓&lt;/span&gt; &lt;STRONG&gt;Question:&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;I have a role called dev-dataengineer with the following privileges on the catalog dap_catalog_dev:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;APPLY TAG&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE FUNCTION&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE MATERIALIZED VIEW&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE TABLE&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE VOLUME&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;EXECUTE&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;READ VOLUME&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;REFRESH&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;SELECT&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;USE SCHEMA&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;WRITE VOLUME&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Despite this, users are still able to &lt;STRONG&gt;delete/drop tables&lt;/STRONG&gt; within dap_catalog_dev.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":question_mark:"&gt;❓&lt;/span&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;:&lt;/H3&gt;&lt;P&gt;&lt;STRONG&gt;Why are users still able to delete tables, and how can I restrict this behavior so that table deletion is not allowed?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I want to ensure that users can read and create tables if needed, but not delete them&lt;/P&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; &lt;STRONG&gt;Answer:&lt;/STRONG&gt;&lt;/H3&gt;&lt;P&gt;Great question — and one that's crucial for &lt;STRONG&gt;data governance and table protection&lt;/STRONG&gt; in shared environments!&lt;/P&gt;&lt;H2&gt;&lt;span class="lia-unicode-emoji" title=":prohibited:"&gt;🚫&lt;/span&gt; Why Users Can Still Delete Tables&lt;/H2&gt;&lt;P&gt;&lt;STRONG&gt;CREATE TABLE on a catalog&lt;/STRONG&gt; allows users to create AND drop their own tables, unless further restricted.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":locked_with_key:"&gt;🔐&lt;/span&gt; &lt;STRONG&gt;How to Prevent Table Deletion&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;To prevent accidental or unauthorized table deletion:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Avoid granting DROP, MODIFY, or ALL PRIVILEGES&lt;/STRONG&gt; at the catalog or schema level.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Grant CREATE TABLE only at the schema level&lt;/STRONG&gt;, not the catalog level — this scopes table creation to specific areas.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Restrict OWNERSHIP&lt;/STRONG&gt; transfer, as object owners can drop their own tables regardless of other permissions.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Review and manage privileges regularly&lt;/STRONG&gt; using SHOW GRANTS.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Fix - That Worked for mea nd eventually for all&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Audit all roles (not just dev-dataengineer) and users for:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;DROP, MODIFY, or ALL PRIVILEGES&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;CREATE TABLE permissions granted at higher scopes (e.g., catalog)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;You can run something like:&lt;/P&gt;&lt;PRE&gt;SHOW GRANTS ON SCHEMA dap_catalog_dev;&lt;BR /&gt;SHOW GRANTS ON CATALOG dap_catalog_dev;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 04:14:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/121424#M443</guid>
      <dc:creator>CURIOUS_DE</dc:creator>
      <dc:date>2025-06-11T04:14:50Z</dc:date>
    </item>
    <item>
      <title>Re: 🔐 How Do I Prevent Users from Accidentally Deleting Tables in Unity Catalog? 🔐</title>
      <link>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/121697#M447</link>
      <description>&lt;P&gt;Thanks for breaking it down so clearly, &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/96088"&gt;@CURIOUS_DE&lt;/a&gt;! That’s such a subtle detail. Many overlook it, but it's important to be aware of it.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jun 2025 09:30:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/121697#M447</guid>
      <dc:creator>Advika</dc:creator>
      <dc:date>2025-06-13T09:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: 🔐 How Do I Prevent Users from Accidentally Deleting Tables in Unity Catalog? 🔐</title>
      <link>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/123530#M454</link>
      <description>&lt;P&gt;Managing assets in UC is always a overhead maintenance. We have this access controls in terraform codes and it is always hard to see what level of access is given to different personas in the org. We are building an audit dashboard for it.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jul 2025 19:23:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/how-do-i-prevent-users-from-accidentally-deleting-tables-in/m-p/123530#M454</guid>
      <dc:creator>nayan_wylde</dc:creator>
      <dc:date>2025-07-01T19:23:23Z</dc:date>
    </item>
  </channel>
</rss>

