Disable Editing on Web Map For Field Map Users

[KansasDASC]

I have a Field Maps deployment question, but this is more of a AGO Map Viewer focus. I have a web map with several layers and forms built for those layers for use in Field Maps app on a mobile device. The users have edit ability on the layers once they're in the FM app so that they can fill out the forms.

The issue here is that if they log in to AGO and go to the map, they also have edit control over the actual map and access to the FM smart forms. How do I prevent any unauthorized map changes to symbology, FM forms, layer adds/removals, etc in the map itself?

I tried adding the map to a group, but didn't see any edit controls there. I can't make the map private to restrict access to only me because that would then prevent users seeing the map on the FM app. I feel like this is a valid concern and that I'm missing something obvious here.

[DavidSolari]

Whoops, I wrote an entire paragraph before realizing you're talking about restricting edits to the Web Map structure itself, not feature edits. Anyways, it looks like if a user has editing privileges they can reconfigure a web map and then make edits in that same window, even if they technically can't create content. It'd be nicer if the map authoring controls were locked out below the creator level (although there might be a user role option that I'm missing here) but it seems like the best solution for now is regular data validation as mentioned below. Here's my original write-up in case it helps:

To my knowledge there's no "only use this map in Field Maps" option. One thing you can try is adding some GPS Metadata Fields and then validating if they're populated with valid data. This might be possible with form validation but I'm not sure if these fields are populated before the form is validated or not. An Attribute Rule would work but this will restrict editing to Field Maps only and you might not have access to them if you're Online-only. So sadly, not the best options for this level of access control in real time, you might have to settle for regular inspections and take disciplinary action as needed.

[KansasDASC]

Thanks for replying. I did consider user roles and there are controls to restrict editing, but it's an umbrella option that pertains to all content, not just web maps. I don't see our users making intentional changes to the map, but it's always a possibility that someone could without knowing. Or someone who is curious about the form structure could easily open the form designer and make edits. They'd have to hit the save button in either case, but still remains a possibility.