<?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>idea Return Enterprise Geodatabase Dataset Permissions in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idi-p/1303168</link>
    <description>&lt;P&gt;Please create a geodatabase/arcpy tool that returns permissions on an input enterprise dataset.&amp;nbsp; There are cases when we have new staff start and they need/want the same permissions as another user.&amp;nbsp; It would be nice to be able to iterate over datasets in a geodatabase, get the permissions on a particular dataset and be able to check what permissions a certain user has.&amp;nbsp; In this example, I could set a target user name and if found, assign the new user the same permissions as the target user.&lt;/P&gt;&lt;P&gt;The return could be something like either of the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;return = [{user: UserName1, edit: True, view: True}, {user: UserName2, edit: False, view: True}]

return = [{user: UserName1, select: True, insert: True, update: True, delete: True}, {user: UserName2, select: True, insert: False, update: False, delete: False}]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 26 Jun 2023 20:39:14 GMT</pubDate>
    <dc:creator>mpboyle</dc:creator>
    <dc:date>2023-06-26T20:39:14Z</dc:date>
    <item>
      <title>Return Enterprise Geodatabase Dataset Permissions</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idi-p/1303168</link>
      <description>&lt;P&gt;Please create a geodatabase/arcpy tool that returns permissions on an input enterprise dataset.&amp;nbsp; There are cases when we have new staff start and they need/want the same permissions as another user.&amp;nbsp; It would be nice to be able to iterate over datasets in a geodatabase, get the permissions on a particular dataset and be able to check what permissions a certain user has.&amp;nbsp; In this example, I could set a target user name and if found, assign the new user the same permissions as the target user.&lt;/P&gt;&lt;P&gt;The return could be something like either of the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;return = [{user: UserName1, edit: True, view: True}, {user: UserName2, edit: False, view: True}]

return = [{user: UserName1, select: True, insert: True, update: True, delete: True}, {user: UserName2, select: True, insert: False, update: False, delete: False}]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jun 2023 20:39:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idi-p/1303168</guid>
      <dc:creator>mpboyle</dc:creator>
      <dc:date>2023-06-26T20:39:14Z</dc:date>
    </item>
    <item>
      <title>Re: Return Enterprise Geodatabase Dataset Permissions</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1355739#M27364</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/189832"&gt;@mpboyle&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am wondering whether using database roles would help you achieve the same solution and ultimately make managing database permissions much easier. What i am suggesting is that you would create database roles that fit each user groups specific permission needs, then grant the needed permissions to the roles. When a new staff needs to connect to the database, you can determine which permissions role they fit into and simply create a new database user and add it to that database role.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2023 16:16:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1355739#M27364</guid>
      <dc:creator>ChetDobbins</dc:creator>
      <dc:date>2023-12-01T16:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: Return Enterprise Geodatabase Dataset Permissions - Status changed to: Needs Clarification</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1355781#M27366</link>
      <description>&lt;P&gt;Please see Chet's potential solution using existing tooling in &lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1355739/highlight/true#M27364" target="_self"&gt;the post above&lt;/A&gt; this one. His question is quoted here for convenience.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;I am wondering whether using database roles would help you achieve the same solution and ultimately make managing database permissions much easier. What i am suggesting is that you would create database roles that fit each user groups specific permission needs, then grant the needed permissions to the roles. When a new staff needs to connect to the database, you can determine which permissions role they fit into and simply create a new database user and add it to that database role.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-ChetDobbins&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;</description>
      <pubDate>Fri, 01 Dec 2023 16:54:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1355781#M27366</guid>
      <dc:creator>HannesZiegler</dc:creator>
      <dc:date>2023-12-01T16:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: Return Enterprise Geodatabase Dataset Permissions - Status changed to: Closed</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1479683#M30431</link>
      <description>&lt;P&gt;Thank you for submitting your idea for a tool to inspect enterprise geodatabase dataset permissions. We appreciate your suggestion.&amp;nbsp;At this time, we are not pursuing this idea given that a best practice solution was offered, and we received no further feedback.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;The solution to consider is as follows:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create database roles&lt;/LI&gt;&lt;LI&gt;Assign users to those roles&lt;/LI&gt;&lt;LI&gt;Assign permissions to the roles that each user group requires&lt;/LI&gt;&lt;LI&gt;When a new user comes online… determine what permissions they need and assign them to the appropriate role or roles.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;See the original response by &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/1175"&gt;@ChetDobbins&lt;/a&gt;:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;I am wondering whether using database roles would help you achieve the same solution and ultimately make managing database permissions much easier. What i am suggesting is that you would create database roles that fit each user groups specific permission needs, then grant the needed permissions to the roles. When a new staff needs to connect to the database, you can determine which permissions role they fit into and simply create a new database user and add it to that database role.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;-ChetDobbins&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Thank you again for your contribution and understanding.&amp;nbsp;If you have any further questions or concerns, please do not hesitate to contact us.&lt;/P&gt;</description>
      <pubDate>Tue, 28 May 2024 17:51:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/return-enterprise-geodatabase-dataset-permissions/idc-p/1479683#M30431</guid>
      <dc:creator>HannesZiegler</dc:creator>
      <dc:date>2024-05-28T17:51:06Z</dc:date>
    </item>
  </channel>
</rss>

