<?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 Preserve Group Context in User View (Prevent Mixed Conent Across Groups) in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/preserve-group-context-in-user-view-prevent-mixed/idi-p/1695063</link>
    <description>&lt;P&gt;In ArcGIS Online, groups are a powerful way to organize content- but only from the admin side.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Issue:&lt;/STRONG&gt;&lt;BR /&gt;When a user belongs to multiple groups, content becomes flattened and mixed together, losing the structure admins intentionally created.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Real impact (water utility example):&lt;/STRONG&gt;&lt;BR /&gt;A field user opens a map picker expecting operational layers (valves, mains), but also sees:&lt;/P&gt;&lt;P&gt;- Engineering design maps&lt;BR /&gt;- Easement/ROW apps&lt;BR /&gt;- Internal or draft content&lt;/P&gt;&lt;P&gt;Now they’re guessing which map to use- slowing them down and increasing risk of error.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What’s needed:&lt;/STRONG&gt;&lt;BR /&gt;Give users a way to &lt;STRONG&gt;stay within a group context&lt;/STRONG&gt;, such as:&lt;/P&gt;&lt;P&gt;- Group-based tabs or sections&lt;BR /&gt;- “Enter group” view that isolates its content&lt;BR /&gt;- Clear visual separation by group in map/app pickers&lt;BR /&gt;- Optional admin setting to enforce group-scoped browsing&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why it matters:&lt;/STRONG&gt;&lt;BR /&gt;Groups shouldn’t just organize content for admins- they should guide users to the &lt;STRONG&gt;right data at the right time.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Right now, that structure disappears where it matters most.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2026 15:18:29 GMT</pubDate>
    <dc:creator>Debert</dc:creator>
    <dc:date>2026-04-08T15:18:29Z</dc:date>
    <item>
      <title>Preserve Group Context in User View (Prevent Mixed Conent Across Groups)</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/preserve-group-context-in-user-view-prevent-mixed/idi-p/1695063</link>
      <description>&lt;P&gt;In ArcGIS Online, groups are a powerful way to organize content- but only from the admin side.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Issue:&lt;/STRONG&gt;&lt;BR /&gt;When a user belongs to multiple groups, content becomes flattened and mixed together, losing the structure admins intentionally created.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Real impact (water utility example):&lt;/STRONG&gt;&lt;BR /&gt;A field user opens a map picker expecting operational layers (valves, mains), but also sees:&lt;/P&gt;&lt;P&gt;- Engineering design maps&lt;BR /&gt;- Easement/ROW apps&lt;BR /&gt;- Internal or draft content&lt;/P&gt;&lt;P&gt;Now they’re guessing which map to use- slowing them down and increasing risk of error.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What’s needed:&lt;/STRONG&gt;&lt;BR /&gt;Give users a way to &lt;STRONG&gt;stay within a group context&lt;/STRONG&gt;, such as:&lt;/P&gt;&lt;P&gt;- Group-based tabs or sections&lt;BR /&gt;- “Enter group” view that isolates its content&lt;BR /&gt;- Clear visual separation by group in map/app pickers&lt;BR /&gt;- Optional admin setting to enforce group-scoped browsing&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why it matters:&lt;/STRONG&gt;&lt;BR /&gt;Groups shouldn’t just organize content for admins- they should guide users to the &lt;STRONG&gt;right data at the right time.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Right now, that structure disappears where it matters most.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 15:18:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/preserve-group-context-in-user-view-prevent-mixed/idi-p/1695063</guid>
      <dc:creator>Debert</dc:creator>
      <dc:date>2026-04-08T15:18:29Z</dc:date>
    </item>
  </channel>
</rss>

