Move Web Editor access from the Creator user type to the Contributor user type

[MelanieWawryk]

The Web Editor is an ideal tool for lightweight, task‑focused GIS editing, especially for organizations that want to empower broader teams to make simple updates without requiring full professional GIS software. Our goal is to roll out Web Editor as a streamlined alternative to ArcGIS Pro for users who only need to perform basic, controlled edits.

However, because Web Editor is restricted to the Creator user type, it becomes significantly more expensive than necessary. Purchasing a Creator license effectively bundles ArcGIS Pro and other advanced capabilities that these users do not need and will not use. This creates avoidable licensing overhead and reduces our ability to scale light-editing workflows to the staff who would benefit most.

Moving Web Editor to the Contributor user type would:

• Enable broader adoption of light editing across organizations without unnecessary licensing costs.
• Support modern web‑based editing workflows without requiring ArcGIS Pro deployments or advanced GIS skills.
• Allow GIS teams to maintain governance and data integrity while empowering non‑GIS staff to update authoritative layers.
• Align Web Editor with its intended purpose—a simplified, browser‑based tool for minimal edits, not a professional‑grade editing environment.

Contributor‑level access would make Web Editor a practical, cost‑effective solution for organizations looking to modernize editing workflows and reduce reliance on desktop software for routine updates.

[Bill_VS]

Amen to that!!!

[MaximePelletier1villequebec]

All of this. ArcGIS already provides an easy and efficient way to provide WE to Contributors without them using any map they get their hand on: Experience Builder's Embed widget.

I'd add that Web Editor bypassing the map editing restriction is also contrary to it's intended purpose, but that may be another conversation.

[CraigGillgrass]

"I'd add that Web Editor bypassing the map editing restriction is also contrary to it's intended purpose, but that may be another conversation."

@MaximePelletier1villequebec can you elaborate on this comment?

[MaximePelletier1villequebec]

@CraigGillgrass Maybe this has changed in later releases, but in our Enterprise 11.5 tests we had to switch out Feature services (with editing disabled in Web Map) to the underlying Map services to ensure there wouldn't be unexpected edits against background features. The use case was using WE to batch created/assign Tasks from infrastructure assets.

This could also be a weird licensing bypass with elevated users. 

[CraigGillgrass]

@MaximePelletier1villequebec The workflow you describe is what happens when the owner of the data or a user in the Administrator role edits through Web Editor.  What was the role of the user who you connected as when performing the edits?  

[MaximePelletier1villequebec]

@CraigGillgrass That would likely be the case yes. Since contributors don't have access we've given up on the Web Editor as a solution and are no longer testing.

I'd argue it's not an ideal behavior regardless of the licensing discussion this page is about, but best left as a seperate conversation. Happy to hear this is not expected behavior for other users.