<?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 Access based content / layer enumeration in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/access-based-content-layer-enumeration/idi-p/1695354</link>
    <description>&lt;P&gt;An option would be helpful for embedded content (layers included in maps, for example) to toggle between the existing behavior of requiring a user to log in whenever content is beyond the user's current access level, and a way of simply "ignoring" any content that does not match that user's access level.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example ideal workflow:&lt;/P&gt;&lt;P&gt;An application exists, using a web map containing layers with multiple levels of sharing enabled.&amp;nbsp; Some layers are acceptable for public sharing and some are restricted to the organization and/or group level.&amp;nbsp; Enable a proposed option to ignore content for which the user does not have access and continue to load the application.&amp;nbsp; The advantage is to be able to serve a single app and web map for multiple types of users; without having to expand maintenance complexity for the application where the theme remains constant.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For our specific workflow, this could be simplified to ignore all content that requires a login (not set to "public"). However, I imagine others might want to additionally leverage groups as a part of their strategy which is why I described it more broadly as the 'user not having the required access.'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Current (not ideal) workflow:&lt;/P&gt;&lt;P&gt;Create two web maps, one containing only public layers and another for privileged access.&amp;nbsp; Create two Instant apps, one for each web map.&amp;nbsp; Maintain all duplicate content in parallel.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Apr 2026 16:36:44 GMT</pubDate>
    <dc:creator>KennyLohr1</dc:creator>
    <dc:date>2026-04-09T16:36:44Z</dc:date>
    <item>
      <title>Access based content / layer enumeration</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/access-based-content-layer-enumeration/idi-p/1695354</link>
      <description>&lt;P&gt;An option would be helpful for embedded content (layers included in maps, for example) to toggle between the existing behavior of requiring a user to log in whenever content is beyond the user's current access level, and a way of simply "ignoring" any content that does not match that user's access level.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example ideal workflow:&lt;/P&gt;&lt;P&gt;An application exists, using a web map containing layers with multiple levels of sharing enabled.&amp;nbsp; Some layers are acceptable for public sharing and some are restricted to the organization and/or group level.&amp;nbsp; Enable a proposed option to ignore content for which the user does not have access and continue to load the application.&amp;nbsp; The advantage is to be able to serve a single app and web map for multiple types of users; without having to expand maintenance complexity for the application where the theme remains constant.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For our specific workflow, this could be simplified to ignore all content that requires a login (not set to "public"). However, I imagine others might want to additionally leverage groups as a part of their strategy which is why I described it more broadly as the 'user not having the required access.'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Current (not ideal) workflow:&lt;/P&gt;&lt;P&gt;Create two web maps, one containing only public layers and another for privileged access.&amp;nbsp; Create two Instant apps, one for each web map.&amp;nbsp; Maintain all duplicate content in parallel.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2026 16:36:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/access-based-content-layer-enumeration/idi-p/1695354</guid>
      <dc:creator>KennyLohr1</dc:creator>
      <dc:date>2026-04-09T16:36:44Z</dc:date>
    </item>
  </channel>
</rss>

