nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Edit Widget not honoring portal group permissions of feature layers

KerissaReedy1

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?

Najděte více příspěvků označených jako

ArcGIS Enterprise

Accepted answers

KerissaReedy1

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

All comments

AlixVezina

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.

ChristopherCounsell

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

KerissaReedy1

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.