Publishing service with different sharing for Feature and Map Image Layer

[KamilNovák]

We have scenarios when we share differently Map Image Layer and Feature Layer items (these items are created for one AGS map service - AGS is federated with Portal). For example, Feature layer is shared for a specific group (for editing, ..) within the Portal, but Map Image Layer is shared publicly. But when a service needs to be overwrite, ArcGIS Pro will override the items sharing according to the publication settings for both items. There is no option to control sharing for each item separately.

I suggest adding the ability to control sharing for all items at the ArcGIS Pro level.

[JonahLay]

@KamilNovák Thank you for your idea submission. Can you clarify a few things so that we can better understand your suggestion?

• Why is it important to be able to set a different sharing setting for the associated web feature layer?
• Is your current workflow to share the map image layer with the associated web feature layer and then change the sharing settings for the web feature layer in portal after publishing? It sounds like you have to repeat this step after overwriting as well?

Thank you!

[KamilNovák]

@JonahLay

• There are many reasons to set different sharing setting for the associated web feature layer. For example:
  • some Portal users can only view the data in the app (WAB, ExB) vs. some users have the right to edit the data in the same app
  • within the opendata catalog we don't want to share a map image layer that creates a separate "HTML item"
  • ...
• Yes, it's exactly as you say. Our current workflow is as you describe. And our sharing settings can be very complicated - many assigned groups. And this setting is lost after overwriting.

[SusanTran]

Thank you for submitting your idea. Map image layers and their associated extensions (ex: Feature Layers) must have the sharing permissions to be accessible in ArcGIS Enterprise. While the Enterprise portal website currently allows users to diverge sharing settings of extensions from the parent Map Image Layer, there are known access and permission issues when doing so. Due to these limitations, this idea cannot be implemented.