{
  "id": "arcgis-dashboards-vs-arcgis-storymaps",
  "ids": [
    "arcgis-dashboards",
    "arcgis-storymaps"
  ],
  "title": "ArcGIS Dashboards vs ArcGIS StoryMaps: publishing ArcGIS maps for different audiences",
  "heading": "ArcGIS Dashboards vs ArcGIS StoryMaps",
  "kicker": "GIS and analysis software comparison",
  "deck": "Dashboards communicates operational indicators and interactive data views. StoryMaps explains a subject through a geographic narrative. Use Dashboards for ongoing monitoring and StoryMaps for contextual explanation, while validating the underlying data permissions in either case.",
  "description": "Compare ArcGIS Dashboards vs ArcGIS StoryMaps for publishing ArcGIS maps for different audiences.",
  "answerHeading": "Which option fits the requirement?",
  "answer": "Dashboards communicates operational indicators and interactive data views. StoryMaps explains a subject through a geographic narrative. Use Dashboards for ongoing monitoring and StoryMaps for contextual explanation, while validating the underlying data permissions in either case.",
  "checkedAt": "2026-10-25",
  "researchTag": "Deployment, compatibility and cost scope",
  "researchLimit": "Official product material reviewed. Acceptance checks are proposed exercises, not completed product trials, performance measurements or reliability guarantees.",
  "datasetDescription": "Seven technical differences and four proposed acceptance checks for ArcGIS Dashboards vs ArcGIS StoryMaps.",
  "type": "workflow-buying",
  "sharedBuyingNeed": "Evaluate alternative approaches to publishing ArcGIS maps for different audiences.",
  "rows": [
    [
      "Output model",
      "Operational information dashboard",
      "Map-based narrative or presentation"
    ],
    [
      "Authoring approach",
      "Configure maps, indicators and dashboard elements",
      "Compose maps, text and multimedia"
    ],
    [
      "Data context",
      "Maps and connected data views",
      "Geographic context with narrative content"
    ],
    [
      "Interaction focus",
      "Monitoring indicators and interacting with data",
      "Explaining a topic through a story"
    ],
    [
      "Platform boundary",
      "ArcGIS organisation and sharing permissions",
      "ArcGIS content, access and publication settings"
    ],
    [
      "Evaluation focus",
      "Indicator definitions, filters and update behaviour",
      "Narrative clarity, accessibility and map permissions"
    ],
    [
      "Cost components",
      "Eligible access, underlying services and hosted data",
      "Eligible access, content creation and connected services"
    ]
  ],
  "scenarios": [
    {
      "name": "Audience task",
      "question": "Can the team build one copied view that answers a specific visitor question?",
      "left": "With ArcGIS Dashboards, build one copied view that answers a specific visitor question.",
      "right": "With ArcGIS StoryMaps, build one copied view that answers a specific visitor question.",
      "note": "The intended audience can complete the task using the available interaction."
    },
    {
      "name": "Mobile layout",
      "question": "Can the team read the app and operate its essential controls on a narrow screen?",
      "left": "With ArcGIS Dashboards, read the app and operate its essential controls on a narrow screen.",
      "right": "With ArcGIS StoryMaps, read the app and operate its essential controls on a narrow screen.",
      "note": "Content, controls and data remain understandable and usable."
    },
    {
      "name": "Sharing permissions",
      "question": "Can the team open the published test content as an anonymous and an authorised user?",
      "left": "With ArcGIS Dashboards, open the published test content as an anonymous and an authorised user.",
      "right": "With ArcGIS StoryMaps, open the published test content as an anonymous and an authorised user.",
      "note": "Apps and underlying layers follow the documented access policy."
    },
    {
      "name": "Content update",
      "question": "Can the team change one authorised sample record and inspect the published view?",
      "left": "With ArcGIS Dashboards, change one authorised sample record and inspect the published view.",
      "right": "With ArcGIS StoryMaps, change one authorised sample record and inspect the published view.",
      "note": "The update and ownership process is documented and repeatable."
    }
  ],
  "exampleTable": {
    "caption": "Proposed checks using authorised copies of representative datasets, projects or models. Record software versions, required licences, dependencies, configuration and observed results.",
    "headers": [
      "Requirement",
      "Proposed exercise",
      "Accept when"
    ],
    "rows": [
      [
        "Audience task",
        "Build one copied view that answers a specific visitor question.",
        "The intended audience can complete the task using the available interaction."
      ],
      [
        "Mobile layout",
        "Read the app and operate its essential controls on a narrow screen.",
        "Content, controls and data remain understandable and usable."
      ],
      [
        "Sharing permissions",
        "Open the published test content as an anonymous and an authorised user.",
        "Apps and underlying layers follow the documented access policy."
      ],
      [
        "Content update",
        "Change one authorised sample record and inspect the published view.",
        "The update and ownership process is documented and repeatable."
      ]
    ]
  },
  "sections": [
    {
      "id": "scope-and-architecture",
      "navLabel": "Architecture",
      "title": "Scope and architecture",
      "paragraphs": [
        "Dashboards communicates operational indicators and interactive data views. StoryMaps explains a subject through a geographic narrative. Use Dashboards for ongoing monitoring and StoryMaps for contextual explanation, while validating the underlying data permissions in either case.",
        "These applications present geographic information in different ways and can be combined. An operational dashboard, interactive web application and narrative story have different audience tasks. Confirm user types, public access, underlying layer permissions and any separately billed services."
      ],
      "links": [
        {
          "url": "https://www.esri.com/en-us/arcgis/products/arcgis-dashboards/overview",
          "label": "ArcGIS Dashboards product information"
        },
        {
          "url": "https://www.esri.com/en-us/arcgis/products/arcgis-storymaps/overview",
          "label": "ArcGIS StoryMaps product information"
        }
      ]
    },
    {
      "id": "cost-and-migration",
      "navLabel": "Costs & migration",
      "title": "Cost and migration planning",
      "paragraphs": [
        "For ArcGIS Dashboards, include eligible access, underlying services and hosted data. For ArcGIS StoryMaps, include eligible access, content creation and connected services. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration.",
        "Publish a copied map with test data, verify it as an anonymous visitor and an authorised user, and check its layout on a small screen. Preserve required layer access and document who owns the app, data and updates."
      ]
    }
  ],
  "faqs": [
    {
      "question": "How should we choose between ArcGIS Dashboards and ArcGIS StoryMaps?",
      "answer": "Dashboards communicates operational indicators and interactive data views. StoryMaps explains a subject through a geographic narrative. Use Dashboards for ongoing monitoring and StoryMaps for contextual explanation, while validating the underlying data permissions in either case."
    },
    {
      "question": "Which costs belong in the comparison?",
      "answer": "For ArcGIS Dashboards, include eligible access, underlying services and hosted data. For ArcGIS StoryMaps, include eligible access, content creation and connected services. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration."
    },
    {
      "question": "What should we validate before a production move?",
      "answer": "Publish a copied map with test data, verify it as an anonymous visitor and an authorised user, and check its layout on a small screen. Preserve required layer access and document who owns the app, data and updates."
    }
  ],
  "sources": [
    {
      "url": "https://www.esri.com/en-us/arcgis/products/arcgis-dashboards/overview",
      "facts": "Official product scope, deployment and integration context used for publishing ArcGIS maps for different audiences."
    },
    {
      "url": "https://www.esri.com/en-us/arcgis/products/arcgis-storymaps/overview",
      "facts": "Official product scope, deployment and integration context used for publishing ArcGIS maps for different audiences."
    }
  ],
  "relatedLinks": [
    {
      "path": "/categories/gis-geospatial/",
      "title": "Gis Geospatial software"
    },
    {
      "path": "/guides/software-buying-checklist/",
      "title": "Software buying checklist"
    }
  ]
}