<?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 Limiting access by region in Web App Builder App in ArcGIS Online Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-questions/limiting-access-by-region-in-web-app-builder-app/m-p/517387#M26075</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a customer that would like to create an app using Web App Builder and make this available to end users, but limit/filter the data within it for some users based on either an area (e.g. extent/polygon) or an attribute (e.g. region name).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can use hosted feature layer views to acheive the filtering, creating one view per region and sharing this with the appropriate users via groups. However, I cannot currently see a way to easily consume those separate hosted layer views within a single Web App Builder app, as this is based on a web map that contains the base hosted feature layer. If I supply a different web map as a parameter in the URL for the app (effectively substituting the base layer with the view), then various widgets in the app do not work correctly as I assume they are referencing the base hosted feature layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only approach currently seems to be:&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create the hosted feature layer view with the appropriate filter for the region.&lt;/LI&gt;&lt;LI&gt;Share the view with the appropriate group.&lt;/LI&gt;&lt;LI&gt;Create a new web map with the same symbology/settings as the main web map.&lt;/LI&gt;&lt;LI&gt;Create a new web app with WAB with the same configuration as the main app.&lt;/LI&gt;&lt;LI&gt;Share the new web map and app with the appropriate group.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, with possibly hundreds of different regions, this approach will become a management nightmare, especially when functionality needs to be added/changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone suggest a better approach? For example, can layer details be passed in to the web app as parameters so that all widgets reference the new layer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My personal opinion is that there should be a way to limit the geographical extent accessible to a specific user in ArcGIS Online as we have had a number of requests for this type of filtering and the hosted layer view does not fulfill these requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts appreciated. Ideally we wanted to avoid custom development, but would consider this if its the only sensible approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 May 2018 14:16:53 GMT</pubDate>
    <dc:creator>JohnFannon</dc:creator>
    <dc:date>2018-05-15T14:16:53Z</dc:date>
    <item>
      <title>Limiting access by region in Web App Builder App</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/limiting-access-by-region-in-web-app-builder-app/m-p/517387#M26075</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a customer that would like to create an app using Web App Builder and make this available to end users, but limit/filter the data within it for some users based on either an area (e.g. extent/polygon) or an attribute (e.g. region name).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can use hosted feature layer views to acheive the filtering, creating one view per region and sharing this with the appropriate users via groups. However, I cannot currently see a way to easily consume those separate hosted layer views within a single Web App Builder app, as this is based on a web map that contains the base hosted feature layer. If I supply a different web map as a parameter in the URL for the app (effectively substituting the base layer with the view), then various widgets in the app do not work correctly as I assume they are referencing the base hosted feature layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The only approach currently seems to be:&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create the hosted feature layer view with the appropriate filter for the region.&lt;/LI&gt;&lt;LI&gt;Share the view with the appropriate group.&lt;/LI&gt;&lt;LI&gt;Create a new web map with the same symbology/settings as the main web map.&lt;/LI&gt;&lt;LI&gt;Create a new web app with WAB with the same configuration as the main app.&lt;/LI&gt;&lt;LI&gt;Share the new web map and app with the appropriate group.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, with possibly hundreds of different regions, this approach will become a management nightmare, especially when functionality needs to be added/changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone suggest a better approach? For example, can layer details be passed in to the web app as parameters so that all widgets reference the new layer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My personal opinion is that there should be a way to limit the geographical extent accessible to a specific user in ArcGIS Online as we have had a number of requests for this type of filtering and the hosted layer view does not fulfill these requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts appreciated. Ideally we wanted to avoid custom development, but would consider this if its the only sensible approach.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 May 2018 14:16:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/limiting-access-by-region-in-web-app-builder-app/m-p/517387#M26075</guid>
      <dc:creator>JohnFannon</dc:creator>
      <dc:date>2018-05-15T14:16:53Z</dc:date>
    </item>
  </channel>
</rss>

