<?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 Unity Catalog - addition of account groups/users to workspaces in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/unity-catalog-addition-of-account-groups-users-to-workspaces/m-p/3947#M814</link>
    <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have set-up metastore, and were doing certain activities as part of MVP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we realized in a particular databricks workspace that was enabled with UC, in admin settings &amp;gt; "Add Groups" section, user groups from other platforms/projects which leverage UC are also appearing. Does this not lead this some unnecessary conflicts with regards to access management between projects/platforms/divisions in organization?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am curious to know experiences of others in this regard. Is there a way to initially restrict and selectively choose other divisions user groups when a need arises (keeping in mind delta sharing across other divisions in a marge organization).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: the same goes for service principals also.&lt;/P&gt;</description>
    <pubDate>Sat, 27 May 2023 21:36:01 GMT</pubDate>
    <dc:creator>NOOR_BASHASHAIK</dc:creator>
    <dc:date>2023-05-27T21:36:01Z</dc:date>
    <item>
      <title>Unity Catalog - addition of account groups/users to workspaces</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-addition-of-account-groups-users-to-workspaces/m-p/3947#M814</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have set-up metastore, and were doing certain activities as part of MVP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we realized in a particular databricks workspace that was enabled with UC, in admin settings &amp;gt; "Add Groups" section, user groups from other platforms/projects which leverage UC are also appearing. Does this not lead this some unnecessary conflicts with regards to access management between projects/platforms/divisions in organization?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am curious to know experiences of others in this regard. Is there a way to initially restrict and selectively choose other divisions user groups when a need arises (keeping in mind delta sharing across other divisions in a marge organization).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: the same goes for service principals also.&lt;/P&gt;</description>
      <pubDate>Sat, 27 May 2023 21:36:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-addition-of-account-groups-users-to-workspaces/m-p/3947#M814</guid>
      <dc:creator>NOOR_BASHASHAIK</dc:creator>
      <dc:date>2023-05-27T21:36:01Z</dc:date>
    </item>
    <item>
      <title>Re: Unity Catalog - addition of account groups/users to workspaces</title>
      <link>https://community.databricks.com/t5/data-engineering/unity-catalog-addition-of-account-groups-users-to-workspaces/m-p/3948#M815</link>
      <description>&lt;P&gt;Good question, didn't think of it that way, from my understanding UC uses users pushed from the account console and not from workspaces, One way to restrict would be to restrict other workspaces from using said catalog and also control ACLs with the right Workspace groups. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In any case following this thread to see what is the most valid solution for this&lt;/P&gt;</description>
      <pubDate>Mon, 29 May 2023 12:33:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unity-catalog-addition-of-account-groups-users-to-workspaces/m-p/3948#M815</guid>
      <dc:creator>Ismail1</dc:creator>
      <dc:date>2023-05-29T12:33:38Z</dc:date>
    </item>
  </channel>
</rss>

