<?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 Allow Users to Edit Group-Owned Items Without Requiring Creator Licences in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/allow-users-to-edit-group-owned-items-without/idi-p/1691649</link>
    <description>&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;I help maintain an ArcGIS Enterprise environment for a large government organisation that works with sensitive and operationally critical information. We’ve recently been facing challenges on a project where several team members need the ability to edit data, but we cannot assign them full editing or Creator licences without risking the integrity of our environment. At the same time, we can’t make the layer public, as doing so could expose sensitive information contained in the dataset.&lt;/P&gt;&lt;P&gt;This creates an operational deadlock: users need to maintain content, but our governance model prevents us from giving them the permissions that would enable it.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;The problem:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;DIV&gt;&lt;P&gt;In ArcGIS Enterprise, users currently require a &lt;EM&gt;Creator&lt;/EM&gt; (or higher) user type to make even small adjustments to shared items, such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Updating symbology or map properties&lt;/LI&gt;&lt;LI&gt;Configuring pop-ups&lt;/LI&gt;&lt;LI&gt;Editing metadata&lt;/LI&gt;&lt;LI&gt;Adding, editing, or deleting records in attribute tables&lt;/LI&gt;&lt;LI&gt;Making basic updates to group-owned maps or layers&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;However, granting Creator licences also gives users capabilities they &lt;STRONG&gt;do not&lt;/STRONG&gt; need, such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Creating new hosted layers&lt;/LI&gt;&lt;LI&gt;Publishing services&lt;/LI&gt;&lt;LI&gt;Overwriting feature layers&lt;/LI&gt;&lt;LI&gt;Deleting datasets&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For environments handling sensitive data, this is a significant governance concern. As a result:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Users lack the permissions they need to maintain operational data&lt;/LI&gt;&lt;LI&gt;Administrators become bottlenecks for even minor updates&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Enhancement Ideas:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;Introduce a new permission model that allows users to edit existing items and table records shared within their groups, without granting high‑risk publishing or creation rights.&lt;/P&gt;&lt;P&gt;This could be implemented in one of two ways:&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H4&gt;&lt;FONT size="3"&gt;&lt;STRONG&gt;Idea 1:&amp;nbsp;Introduce a New “Editor+” User Type&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;A user type that includes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Editing maps and apps shared with their groups&lt;/LI&gt;&lt;LI&gt;Editing layer settings&lt;/LI&gt;&lt;LI&gt;Adding, editing, and deleting attribute table records&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;but excludes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Creating new hosted content&lt;/LI&gt;&lt;LI&gt;Publishing data or services&lt;/LI&gt;&lt;LI&gt;Overwriting datasets&lt;/LI&gt;&lt;LI&gt;Deleting entire items&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H4&gt;&lt;FONT size="3"&gt;&lt;STRONG&gt;Idea 2: Add New Fine-Grained Role Privileges&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;&lt;DIV&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;“Edit items and table records shared within user’s groups (no ability to create or publish new content)”&lt;/P&gt;&lt;P&gt;This could be assigned to custom roles while retaining strict governance.&lt;/P&gt;&lt;/DIV&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Why This Matters:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;P&gt;This change would support:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Stronger data governance&lt;/STRONG&gt; – Allows operational updates without giving users privileges that could compromise sensitive datasets.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Operational efficiency&lt;/STRONG&gt; – teams can maintain their own content without relying on GIS administrators for every small change.&lt;/LI&gt;&lt;LI&gt;&lt;DIV&gt;&lt;STRONG&gt;Aligned with Real-World Needs&lt;/STRONG&gt;&amp;nbsp;&lt;SPAN&gt;–&amp;nbsp;&lt;/SPAN&gt;Many organisations manage sensitive or high-risk data but still need collaborative editing capabilities.&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Who Benefits:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Organisations with large non-GIS workforces&lt;/LI&gt;&lt;LI&gt;Government agencies with tight data controls&lt;/LI&gt;&lt;LI&gt;&lt;DIV&gt;Any organisation managing sensitive datasets across multiple teams&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&lt;DIV&gt;Enabling users to edit group-owned items and attribute table data, without granting high‑risk Creator permissions would significantly improve governance, collaboration, and cost efficiency within ArcGIS Enterprise environments. This enhancement would better reflect how organisations work today and provide a safer, more flexible approach to shared content maintenance.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 20 Mar 2026 05:31:56 GMT</pubDate>
    <dc:creator>Emily_Clark</dc:creator>
    <dc:date>2026-03-20T05:31:56Z</dc:date>
    <item>
      <title>Allow Users to Edit Group-Owned Items Without Requiring Creator Licences</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/allow-users-to-edit-group-owned-items-without/idi-p/1691649</link>
      <description>&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;I help maintain an ArcGIS Enterprise environment for a large government organisation that works with sensitive and operationally critical information. We’ve recently been facing challenges on a project where several team members need the ability to edit data, but we cannot assign them full editing or Creator licences without risking the integrity of our environment. At the same time, we can’t make the layer public, as doing so could expose sensitive information contained in the dataset.&lt;/P&gt;&lt;P&gt;This creates an operational deadlock: users need to maintain content, but our governance model prevents us from giving them the permissions that would enable it.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;The problem:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;DIV&gt;&lt;P&gt;In ArcGIS Enterprise, users currently require a &lt;EM&gt;Creator&lt;/EM&gt; (or higher) user type to make even small adjustments to shared items, such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Updating symbology or map properties&lt;/LI&gt;&lt;LI&gt;Configuring pop-ups&lt;/LI&gt;&lt;LI&gt;Editing metadata&lt;/LI&gt;&lt;LI&gt;Adding, editing, or deleting records in attribute tables&lt;/LI&gt;&lt;LI&gt;Making basic updates to group-owned maps or layers&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;However, granting Creator licences also gives users capabilities they &lt;STRONG&gt;do not&lt;/STRONG&gt; need, such as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Creating new hosted layers&lt;/LI&gt;&lt;LI&gt;Publishing services&lt;/LI&gt;&lt;LI&gt;Overwriting feature layers&lt;/LI&gt;&lt;LI&gt;Deleting datasets&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For environments handling sensitive data, this is a significant governance concern. As a result:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Users lack the permissions they need to maintain operational data&lt;/LI&gt;&lt;LI&gt;Administrators become bottlenecks for even minor updates&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Enhancement Ideas:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;Introduce a new permission model that allows users to edit existing items and table records shared within their groups, without granting high‑risk publishing or creation rights.&lt;/P&gt;&lt;P&gt;This could be implemented in one of two ways:&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H4&gt;&lt;FONT size="3"&gt;&lt;STRONG&gt;Idea 1:&amp;nbsp;Introduce a New “Editor+” User Type&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;A user type that includes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Editing maps and apps shared with their groups&lt;/LI&gt;&lt;LI&gt;Editing layer settings&lt;/LI&gt;&lt;LI&gt;Adding, editing, and deleting attribute table records&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;but excludes:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Creating new hosted content&lt;/LI&gt;&lt;LI&gt;Publishing data or services&lt;/LI&gt;&lt;LI&gt;Overwriting datasets&lt;/LI&gt;&lt;LI&gt;Deleting entire items&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H4&gt;&lt;FONT size="3"&gt;&lt;STRONG&gt;Idea 2: Add New Fine-Grained Role Privileges&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;&lt;DIV&gt;&lt;P&gt;For example:&lt;/P&gt;&lt;P&gt;“Edit items and table records shared within user’s groups (no ability to create or publish new content)”&lt;/P&gt;&lt;P&gt;This could be assigned to custom roles while retaining strict governance.&lt;/P&gt;&lt;/DIV&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Why This Matters:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;P&gt;This change would support:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Stronger data governance&lt;/STRONG&gt; – Allows operational updates without giving users privileges that could compromise sensitive datasets.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Operational efficiency&lt;/STRONG&gt; – teams can maintain their own content without relying on GIS administrators for every small change.&lt;/LI&gt;&lt;LI&gt;&lt;DIV&gt;&lt;STRONG&gt;Aligned with Real-World Needs&lt;/STRONG&gt;&amp;nbsp;&lt;SPAN&gt;–&amp;nbsp;&lt;/SPAN&gt;Many organisations manage sensitive or high-risk data but still need collaborative editing capabilities.&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;&lt;FONT size="4"&gt;&lt;STRONG&gt;Who Benefits:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Organisations with large non-GIS workforces&lt;/LI&gt;&lt;LI&gt;Government agencies with tight data controls&lt;/LI&gt;&lt;LI&gt;&lt;DIV&gt;Any organisation managing sensitive datasets across multiple teams&lt;/DIV&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&lt;DIV&gt;Enabling users to edit group-owned items and attribute table data, without granting high‑risk Creator permissions would significantly improve governance, collaboration, and cost efficiency within ArcGIS Enterprise environments. This enhancement would better reflect how organisations work today and provide a safer, more flexible approach to shared content maintenance.&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 20 Mar 2026 05:31:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/allow-users-to-edit-group-owned-items-without/idi-p/1691649</guid>
      <dc:creator>Emily_Clark</dc:creator>
      <dc:date>2026-03-20T05:31:56Z</dc:date>
    </item>
  </channel>
</rss>

