Default to hiding all web maps from Field Maps unless actively 'shared' to Field Maps

[HeatherBell]

We recently became aware that all of our maps in our organisation are automatically shared to Field Maps mobile by default depending on the sharing settings. They need to be manually 'hidden from the mobile app' (see screenshot). There are two reasons that we can see that this is an issue:

1. We have some maps which are editable by hub community members and these have been configured for certain Experience Builder apps or for Survey123. By sharing these unintentionally we can end up with data collection and edits that are not constrained to the options which we need to give users, and do not assign unique IDs for our records in the way that we require. 

2. It is confusing for users of the mobile app because there are so many options for maps - we just want them to be able to see the very specific one which we have configured for Field Maps and not everything as it currently defaults to. 

We suggest that the maps should not all be shared by default to Field Maps, but that it should be the opposite way around and that users should have to actively click 'share to Field Maps'. We create a large number of maps in our organisation and it will be an ongoing task to keep checking which maps are shared if this is not resolved. 

Thank you. 

[GeoffreyAplin]

Hi

I agree with your issue and sentiment.  We similarly have maps intended to use with web app builder applications that were exposed to Field Maps.  Unfortunately as we discovered this some time down the track it's probably too late to disable as I expect people have found creative uses for the maps.

[DougBrowning]

Does this on the Settings page of the map not work?

[Debert]

Are they getting shared with the group due to a default setting within your organization? All my maps default to sharing with Owner only. I then change the settings after, if I want to share with a group or organization. I would look into this.

[James_Whitacre_PGC]

Add this to the growing list of things that Esri gets backwards in their software architecture and design. This should have been an opt-in option from the beginning, not an opt-out option. @HeatherBell is exactly right and why this wasn't considered by Esri from the outset or why this hasn't been changed/updated to align with her idea, is mindboggling. Can someone from Esri respond to this idea to help us user understand the reasoning behind this decision if it is not going to be changed? Or provide better tools to manage in bulk web maps in Field Maps?

@DougBrowning the setting does work, but if you manage hundreds of maps and users, you would have to manually assess all web maps and then turn that setting off for every web map you don't want listed in Field Maps. Or, you would need to ensure that every user turns that setting off for their maps if it should not be shared, but I have found that people are not great at remembering to turn the setting off (imagine that!).

[GeoffreyAplin]

Hi
I appreciate your response and support of my post.
We found out inadvertently that we have web maps accessible in Field Maps that weren't intended to be.
Direct access to web maps intended for use with related web apps only bypasses functionality and importantly security built in the web app layer.
Thanks,

Geoffrey