<?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 Customizeable default settings in ArcGIS Pro in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/customizeable-default-settings-in-arcgis-pro/idi-p/1691025</link>
    <description>&lt;P&gt;Using ArcGIS Pro in an organisation which balances between decentralization and central administration it would be very useful if every default setting could be set by an administrator.&lt;/P&gt;&lt;P&gt;This would be especially useful because:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Several users who may not be especially knowledgeable about GIS workflows need to maintain organisation data. Thus without proper defaults supporting&amp;nbsp;business workflows they either do somthing wrong, refuse to do it, or admins fearing disaster won't let end-users publish data.&lt;/LI&gt;&lt;LI&gt;In rarely performed repeditative tasks particular settings choices are often forgotten. As a result the resulting data quality suffers. And scripting is rarely an option outside the central GIS administration team.&lt;/LI&gt;&lt;LI&gt;Decentralized data maintenance are used througout the organisation.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Basically governance of the application and the organisation GIS data would be much easier if every default could be set by administrators. In many cases defaults can be controlled from a pro.settingsConfig file. But not in all cases. A few examples where it can't be controlled are Publish/Overwrite Web Layer and Geoprocessing Enviroments. I'm sure there are others.&lt;/P&gt;&lt;P&gt;Thus my idea is to enable pro.settingsConfig to set defaults (and locks) for every possible setting in ArcGIS Pro.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Mar 2026 14:48:42 GMT</pubDate>
    <dc:creator>ThomasUhrePedersen</dc:creator>
    <dc:date>2026-03-17T14:48:42Z</dc:date>
    <item>
      <title>Customizeable default settings in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/customizeable-default-settings-in-arcgis-pro/idi-p/1691025</link>
      <description>&lt;P&gt;Using ArcGIS Pro in an organisation which balances between decentralization and central administration it would be very useful if every default setting could be set by an administrator.&lt;/P&gt;&lt;P&gt;This would be especially useful because:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Several users who may not be especially knowledgeable about GIS workflows need to maintain organisation data. Thus without proper defaults supporting&amp;nbsp;business workflows they either do somthing wrong, refuse to do it, or admins fearing disaster won't let end-users publish data.&lt;/LI&gt;&lt;LI&gt;In rarely performed repeditative tasks particular settings choices are often forgotten. As a result the resulting data quality suffers. And scripting is rarely an option outside the central GIS administration team.&lt;/LI&gt;&lt;LI&gt;Decentralized data maintenance are used througout the organisation.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Basically governance of the application and the organisation GIS data would be much easier if every default could be set by administrators. In many cases defaults can be controlled from a pro.settingsConfig file. But not in all cases. A few examples where it can't be controlled are Publish/Overwrite Web Layer and Geoprocessing Enviroments. I'm sure there are others.&lt;/P&gt;&lt;P&gt;Thus my idea is to enable pro.settingsConfig to set defaults (and locks) for every possible setting in ArcGIS Pro.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Mar 2026 14:48:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/customizeable-default-settings-in-arcgis-pro/idi-p/1691025</guid>
      <dc:creator>ThomasUhrePedersen</dc:creator>
      <dc:date>2026-03-17T14:48:42Z</dc:date>
    </item>
  </channel>
</rss>

