'Edit' widget ignores capabilities

[abureaux]

Am I missing something, or does the Edit widget ignore capabilities?

I set the following:

But still get the option to Delete and Add Record:

[AlixVezina · Accepted solution]

You have the privilege to edit the data because you are an admin/own the layer. If you log in as another user without admin privileges and try to edit the data using the published application, you'll see that they cannot edit the data.

See: What's new—ArcGIS Experience Builder | Documentation

[abureaux]

Thank you for the response.

Guess I'll toss a something into the Idea thread then. Would be nice if those settings had the final say on app behaviour since, if I'm making an app, I am trying to engineer a specific user behaviour.

[JDenham]

I couldn't agree more.  This change that allows a user's permission to supersede the web application design is the wrong direction entirely.  As the owner of an app, I'm not going to be doing significant editing (beyond attributes) from within the app, anyway.  If I need to make geometry changes, I'll do it in ArcGIS Pro.  If I need to delete or modify fields, I'll do it in the portal.  I do not want the ability to inadvertently delete data from within an app that was built to exclude that capability.  I don't understand how anyone thought this was a good idea.  There used to be multiple safeguards against accidental deletion of data.  You can disable editing at the web layer, disable editing in the web map, exclude the capability in the web app, restrict their view in the portal etc..  The apps that I maintain are used by department staff who have minimal GIS experience, and no interest or need to do anything beyond editing and querying their own attribute data without risk to the underlying features.  ESRI needs to provide an option to opt-out of this app behavior.  @abureaux Did you submit an idea to them that I can upvote?