<?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 Manage access to saved trace configs for different user groups in ArcGIS Utility Network Ideas</title>
    <link>https://community.esri.com/t5/arcgis-utility-network-ideas/manage-access-to-saved-trace-configs-for-different/idi-p/1651698</link>
    <description>&lt;P&gt;I am working on a UN data model that will potentially have a large number of saved traces.&amp;nbsp; These are tailored to different groups of users (with differences for filtered features and functions to meet specific needs). &amp;nbsp;The benefit of this is traces that meet specific needs of different users.&amp;nbsp; The downside is a large number of saved traces that users will need to navigate.&lt;/P&gt;&lt;P&gt;From this example, an idea is to have the functionality to control the visibility of saved traces for different user groups.&amp;nbsp; So when a user wants to select a saved trace to run, they can only see the saved traces relevant to them.&amp;nbsp; This will help improve the user experience by making the list of saved traces easier (smaller) for each user to navigate.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Sep 2025 23:40:27 GMT</pubDate>
    <dc:creator>GKing</dc:creator>
    <dc:date>2025-09-18T23:40:27Z</dc:date>
    <item>
      <title>Manage access to saved trace configs for different user groups</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-ideas/manage-access-to-saved-trace-configs-for-different/idi-p/1651698</link>
      <description>&lt;P&gt;I am working on a UN data model that will potentially have a large number of saved traces.&amp;nbsp; These are tailored to different groups of users (with differences for filtered features and functions to meet specific needs). &amp;nbsp;The benefit of this is traces that meet specific needs of different users.&amp;nbsp; The downside is a large number of saved traces that users will need to navigate.&lt;/P&gt;&lt;P&gt;From this example, an idea is to have the functionality to control the visibility of saved traces for different user groups.&amp;nbsp; So when a user wants to select a saved trace to run, they can only see the saved traces relevant to them.&amp;nbsp; This will help improve the user experience by making the list of saved traces easier (smaller) for each user to navigate.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Sep 2025 23:40:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-ideas/manage-access-to-saved-trace-configs-for-different/idi-p/1651698</guid>
      <dc:creator>GKing</dc:creator>
      <dc:date>2025-09-18T23:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Manage access to saved trace configs for different user groups</title>
      <link>https://community.esri.com/t5/arcgis-utility-network-ideas/manage-access-to-saved-trace-configs-for-different/idc-p/1651937#M333</link>
      <description>&lt;P&gt;I can see a use for this in our organization as well.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Sep 2025 22:17:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-utility-network-ideas/manage-access-to-saved-trace-configs-for-different/idc-p/1651937#M333</guid>
      <dc:creator>JamesRains</dc:creator>
      <dc:date>2025-09-19T22:17:12Z</dc:date>
    </item>
  </channel>
</rss>

