Select to view content in your preferred language

Edit Widget not honoring portal group permissions of feature layers

486
3
Jump to solution
04-02-2025 11:45 PM
Labels (1)
KerissaReedy1
Occasional Contributor

Previously in Web App builder were able to control our users editing on feature layers by using Groups in Portal.  This doesn't seem to be the case with Experience Builder Edit Widget. 

Are privileges in experience builder only based on the users UserType/Role and groups disregarded?

 

0 Kudos
1 Solution

Accepted Solutions
KerissaReedy1
Occasional Contributor

Solution found. Once the Experience builder was added as an Application item in Portal, the behavior was as expected. Previously i was testing directly from Experience Builder developer application without it published to our enterprise portal

View solution in original post

0 Kudos
3 Replies
AlixVezina
Esri Regular Contributor

Hi @KerissaReedy1 ,

Please would you be able to describe any unexpected behavior you are seeing regarding editing and groups when using Experience Builder? Also, what version of ArcGIS Enterprise are you on? This will help us narrow down if there are in fact any limitations.

0 Kudos
ChristopherCounsell
MVP Frequent Contributor

Previously in Web App builder were able to control our users editing on feature layers by using Groups in Portal

Groups allow users to access the item. Editing capabilities are enabled at multiple levels:

  • User role (privileges to edit, with some users having admin privileges to edit anything in org)
  • Hosted feature layer editing settings 
  • Map/app editing settings 

The new map viewer and I believe perience builder will allow owners and admins to edit features when they have the privilege to do so, even when it's disabled in the map/app. This may be why you are seeing it.

https://enterprise.arcgis.com/en/portal/latest/use/data-access-and-editing.htm

There may also be some confusion with the Shared Update group setting. This has nothing to do with allowing feature editing. It's for updating items e.g. maps, apps or item details.

I think you want to be creating non-editable hosted feature layer views, maps and apps to share to a read only group, and then an editable equivalent group. Noting that admins will always be given option to edit 

0 Kudos
KerissaReedy1
Occasional Contributor

Solution found. Once the Experience builder was added as an Application item in Portal, the behavior was as expected. Previously i was testing directly from Experience Builder developer application without it published to our enterprise portal

0 Kudos