idea Separate member privileges for editing vs. publishing a StoryMap in ArcGIS StoryMaps Ideas

Separate member privileges for editing vs. publishing a StoryMap

Anonymous User — Tue, 09 Nov 2021 13:53:25 GMT

We want our users to be able to create, edit, and save story maps. However, we don't want them to be able to publish story maps. We need to be able to review the story maps before they are published.

Re: Restrict Owner from Publishing - Status changed to: Already Offered

OwenGeo — Fri, 05 Nov 2021 20:57:46 GMT

Hi @Anonymous User -- This is already offered since ArcGIS StoryMaps honors the roles and privileges of your ArcGIS organization.

There are two ways to prevent members from publishing. You can restrict individual members from sharing items with everyone and/or the organization by placing them in a role that does not have that privilege. You can also restrict public sharing at the organization level. If you do this, only administrators can share items publicly. For more information, see the ArcGIS Online documentation on roles and organization settings.

Configure member roles—ArcGIS Online Help | Documentation

Configure security settings—ArcGIS Online Help | Documentation

Members with restricted sharing privileges will see the corresponding options disabled in the StoryMap builders when publishing.

Re: Restrict Owner from Publishing

Anonymous User — Fri, 05 Nov 2021 21:34:42 GMT

Thanks for your response, OwenGeo.

We already have our users in roles that prevent them from sharing publicly.

We noticed that if someone isn't able to share something publicly, but they are able to share to the organization, and they choose to publish a story map that is already publicly available, that the story map becomes unavailable to the public, and is only available to the organization. This is an issue because we cannot allow downtime for a publicly available item.

We need the story map creators to be able to edit and save their story map after it has already been published and made publicly available. We don't want to risk them accidentally publishing an already publicly available story map to the organization, causing the story map to no longer be available to the public. To minimize this risk, we want to just outright disable their ability to publish story maps at all. We realize that it specifically says that it will publish to the organization and that the publish to the public option is greyed out, but some users still make this mistake. Of course for users that we can trust to not make this mistake, we would let them retain the ability to publish story maps.

When editing a role, there is a subsection called Content that is under a section called General privileges. There are a bunch of publishing options that can be disabled here, but story map publishing is not one of them. It would be really nice if there was an option to disable story map publishing from here.

Re: Restrict Owner from Publishing

Anonymous User — Fri, 05 Nov 2021 21:52:37 GMT

I have the same concern. The user roles don't really work for StoryMaps like they do for other content. Quite frankly, while Storymaps are a great tool and overall, one of Esri's best products as far as displaying data, they are a headache from an admin aspect.

Re: Restrict Owner from Publishing

OwenGeo — Tue, 09 Nov 2021 13:52:44 GMT

@Anonymous User -- Thank you for the additional information! If I'm understanding you correctly, you are looking for a way to define separate member privileges for editing vs. publishing a StoryMap.

This is currently not offered, so I'll update the status and title of this idea based on the additional info. We'll do some more research, think a bit more about this, and update this thread when we have more information.

Re: Restrict Owner from Publishing - Status changed to: Open

OwenGeo — Tue, 09 Nov 2021 13:52:55 GMT

Re: Separate member privileges for editing vs. publishing a StoryMap

OwenGeo — Tue, 09 Nov 2021 13:54:18 GMT

@Anonymous User -- I'm sorry that you are having administrative challenges with StoryMaps. It'd be great if you could please share some details (on a different thread) so we can consider enhancements that will be helpful to you.