<?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 Enable Editors/Contributors to make content changes to existing StoryMaps in ArcGIS StoryMaps Ideas</title>
    <link>https://community.esri.com/t5/arcgis-storymaps-ideas/enable-editors-contributors-to-make-content/idi-p/1647600</link>
    <description>&lt;P&gt;We would like to propose an enhancement that allows &lt;STRONG&gt;users with the Editor/Contributor user type to contribute to existing StoryMaps&lt;/STRONG&gt;—specifically, to edit content within StoryMaps that have been shared with them via portal groups.&lt;/P&gt;&lt;P&gt;Currently, only users with the &lt;STRONG&gt;Creator user type&lt;/STRONG&gt; (or higher) can edit StoryMaps. However, with the recent expansion of the Creator license to include &lt;STRONG&gt;ArcGIS Pro Basic&lt;/STRONG&gt;, the cost has increased significantly. This makes it &lt;STRONG&gt;financially unsustainable for organizations&lt;/STRONG&gt; that have a large number of users who only need to &lt;STRONG&gt;collaborate on StoryMaps&lt;/STRONG&gt;, not use ArcGIS Pro or other advanced tools.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":light_bulb:"&gt;💡&lt;/span&gt; Proposed Enhancement:&lt;/H3&gt;&lt;P&gt;Introduce a &lt;STRONG&gt;privilege or role-based permission&lt;/STRONG&gt; that allows Editors/Contributors to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Edit text, images, and sections within a shared StoryMap.&lt;/LI&gt;&lt;LI&gt;Add new content blocks (e.g., maps, media, narrative).&lt;/LI&gt;&lt;LI&gt;Save changes collaboratively without needing a Creator license.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This could be implemented as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;A &lt;STRONG&gt;group-level setting&lt;/STRONG&gt; that enables collaborative editing.&lt;/LI&gt;&lt;LI&gt;A &lt;STRONG&gt;StoryMap-specific permission&lt;/STRONG&gt; that overrides default user-type restrictions (like the sadly &lt;A title="https://www.esri.com/arcgis-blog/products/arcgis-online/announcements/two-user-types-retiring-in-2023" href="https://www.esri.com/arcgis-blog/products/arcgis-online/announcements/two-user-types-retiring-in-2023" target="_blank" rel="noreferrer noopener"&gt;in 2023 retired ArcGIS Storyteller User Type).&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":direct_hit:"&gt;🎯&lt;/span&gt; Why This Matters:&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Cost Efficiency&lt;/STRONG&gt;: Many users only need StoryMap editing capabilities. Requiring a Creator license for this is not cost-effective.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Collaboration&lt;/STRONG&gt;: StoryMaps are often built by teams. Limiting editing to Creators hinders collaborative workflows.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Accessibility&lt;/STRONG&gt;: Expanding editing capabilities to Editors would democratize storytelling and spatial communication across organizations.&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":raising_hands:"&gt;🙌&lt;/span&gt; Our Use Case:&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;We introduced&amp;nbsp;ArcGIS StoryMaps&amp;nbsp;as a &lt;STRONG&gt;resident information system&lt;/STRONG&gt; for construction sites.&lt;/LI&gt;&lt;LI&gt;Site managers&amp;nbsp;use StoryMaps to quickly &lt;STRONG&gt;update residents online&lt;/STRONG&gt; about&amp;nbsp;current progress of construction work,&amp;nbsp;road closures,&amp;nbsp;other relevant updates.&lt;/LI&gt;&lt;LI&gt;We (one of the largest AEC firms in Europe) estimate a &lt;STRONG&gt;potential need for&amp;nbsp;approximately 400 licenses&lt;/STRONG&gt; for this use case alone, assuming pricing is suitable for&amp;nbsp;distributed teams. Otherwise the use case is limited to just a few selected larger construction sites without big scaling potential.&lt;/LI&gt;&lt;LI&gt;Without affordable editing access, site managers must report updates to&amp;nbsp;central roles. This introduces:&amp;nbsp;Slower communication,&amp;nbsp;additional process steps, &lt;STRONG&gt;reduced responsiveness&amp;nbsp;to residents&lt;/STRONG&gt; and thus, overall reduced acceptance.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;(As a non-native speaker, I used generative AI to help draft and refine this text.)&lt;/P&gt;</description>
    <pubDate>Wed, 03 Sep 2025 13:28:09 GMT</pubDate>
    <dc:creator>Geoeki</dc:creator>
    <dc:date>2025-09-03T13:28:09Z</dc:date>
    <item>
      <title>Enable Editors/Contributors to make content changes to existing StoryMaps</title>
      <link>https://community.esri.com/t5/arcgis-storymaps-ideas/enable-editors-contributors-to-make-content/idi-p/1647600</link>
      <description>&lt;P&gt;We would like to propose an enhancement that allows &lt;STRONG&gt;users with the Editor/Contributor user type to contribute to existing StoryMaps&lt;/STRONG&gt;—specifically, to edit content within StoryMaps that have been shared with them via portal groups.&lt;/P&gt;&lt;P&gt;Currently, only users with the &lt;STRONG&gt;Creator user type&lt;/STRONG&gt; (or higher) can edit StoryMaps. However, with the recent expansion of the Creator license to include &lt;STRONG&gt;ArcGIS Pro Basic&lt;/STRONG&gt;, the cost has increased significantly. This makes it &lt;STRONG&gt;financially unsustainable for organizations&lt;/STRONG&gt; that have a large number of users who only need to &lt;STRONG&gt;collaborate on StoryMaps&lt;/STRONG&gt;, not use ArcGIS Pro or other advanced tools.&lt;/P&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":light_bulb:"&gt;💡&lt;/span&gt; Proposed Enhancement:&lt;/H3&gt;&lt;P&gt;Introduce a &lt;STRONG&gt;privilege or role-based permission&lt;/STRONG&gt; that allows Editors/Contributors to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Edit text, images, and sections within a shared StoryMap.&lt;/LI&gt;&lt;LI&gt;Add new content blocks (e.g., maps, media, narrative).&lt;/LI&gt;&lt;LI&gt;Save changes collaboratively without needing a Creator license.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This could be implemented as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;A &lt;STRONG&gt;group-level setting&lt;/STRONG&gt; that enables collaborative editing.&lt;/LI&gt;&lt;LI&gt;A &lt;STRONG&gt;StoryMap-specific permission&lt;/STRONG&gt; that overrides default user-type restrictions (like the sadly &lt;A title="https://www.esri.com/arcgis-blog/products/arcgis-online/announcements/two-user-types-retiring-in-2023" href="https://www.esri.com/arcgis-blog/products/arcgis-online/announcements/two-user-types-retiring-in-2023" target="_blank" rel="noreferrer noopener"&gt;in 2023 retired ArcGIS Storyteller User Type).&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":direct_hit:"&gt;🎯&lt;/span&gt; Why This Matters:&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;Cost Efficiency&lt;/STRONG&gt;: Many users only need StoryMap editing capabilities. Requiring a Creator license for this is not cost-effective.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Collaboration&lt;/STRONG&gt;: StoryMaps are often built by teams. Limiting editing to Creators hinders collaborative workflows.&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Accessibility&lt;/STRONG&gt;: Expanding editing capabilities to Editors would democratize storytelling and spatial communication across organizations.&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;H3&gt;&lt;span class="lia-unicode-emoji" title=":raising_hands:"&gt;🙌&lt;/span&gt; Our Use Case:&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;We introduced&amp;nbsp;ArcGIS StoryMaps&amp;nbsp;as a &lt;STRONG&gt;resident information system&lt;/STRONG&gt; for construction sites.&lt;/LI&gt;&lt;LI&gt;Site managers&amp;nbsp;use StoryMaps to quickly &lt;STRONG&gt;update residents online&lt;/STRONG&gt; about&amp;nbsp;current progress of construction work,&amp;nbsp;road closures,&amp;nbsp;other relevant updates.&lt;/LI&gt;&lt;LI&gt;We (one of the largest AEC firms in Europe) estimate a &lt;STRONG&gt;potential need for&amp;nbsp;approximately 400 licenses&lt;/STRONG&gt; for this use case alone, assuming pricing is suitable for&amp;nbsp;distributed teams. Otherwise the use case is limited to just a few selected larger construction sites without big scaling potential.&lt;/LI&gt;&lt;LI&gt;Without affordable editing access, site managers must report updates to&amp;nbsp;central roles. This introduces:&amp;nbsp;Slower communication,&amp;nbsp;additional process steps, &lt;STRONG&gt;reduced responsiveness&amp;nbsp;to residents&lt;/STRONG&gt; and thus, overall reduced acceptance.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;(As a non-native speaker, I used generative AI to help draft and refine this text.)&lt;/P&gt;</description>
      <pubDate>Wed, 03 Sep 2025 13:28:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-storymaps-ideas/enable-editors-contributors-to-make-content/idi-p/1647600</guid>
      <dc:creator>Geoeki</dc:creator>
      <dc:date>2025-09-03T13:28:09Z</dc:date>
    </item>
  </channel>
</rss>

