Note: The StoryMap editor is accessible here: https://storymap.knightlab.com/select/. Please access your StoryMap for edit via this selector link and not a direct bookmark to a specific StoryMap in order to ensure proper authentication to your account.

How do I ask for help about StoryMapJS?

Before opening a support ticket, please read through this page. Most of the questions we get are covered here. If you are still unable to solve the problem:

• Submit a request here: https://knightlab.zendesk.com/hc/en-us/requests/new
• Please include the share link to your StoryMap. This can be found by selecting the Share button in the upper right corner of the editor. Important Please be sure to provide the Share link and not the URL from your browser's address bar. The browser URL is an application link that does not help us to find anything related to your account.
• If the problem is such that you cannot access the Share link, please be sure to authenticate via https://storymap.knightlab.com/select/, then visit this link and copy-and-paste the info from that page: https://storymap.knightlab.com/userinfo/

Note: Including the StoryMap share link and/or your userinfo is extremely helpful for diagnosing problems and will serve to expedite your request. Again, please review the common problems below before submitting your request.

You are trying to access StoryMap on a domain that is used for internal purposes only. The correct location for accessing the StoryMap editor is https://storymap.knightlab.com/

The fix is to manually edit the longitude values in the JSON file. If you are using the StoryMap editor, Knight Lab support will have to upload the modified file for you

• Pick an East/West hemisphere and "shift" those longitude points by 360 degrees
• If you are modifying points on the Eastern side (positive longitude numbers) then subtract 360 from each longitude value
• If you are modifying points on the Western side (negative longitude numbers) then add 360 to each longitude value

Only shift points on one side or the other, not both.

There is not a straightforward mechanism for shared editing of a StoryMap. Generally, teams will create a separate Google account and share the password with everyone on the team. In this case, be sure that only one person is editing the StoryMap at a time. Otherwise, you will likely create conflicting edits.

If you have a more pipelined editing approach, with successive edits by different users, another option would be to copy the StoryMap from one account into another to continue the edits. This approach, however, requires a bit more disciplined organization as it will result in successive copies into different accounts without changes being reflected in previous accounts.

In most cases, having a single team account seems to be the best approach.