ExB Edit Widget not honoring editing capabilities of service

Question

While trying to implement the Edit widget in Experience Builder (in AGOL) I discovered that ExB does not seem to be honoring the service level editing capabilities. Well technically it is but its showing in ExB as if they are not!!!

I have an ExB where I want to allow our user to add points, edit their points, and delete their points while being able to see all points add by any users. A user should NOT be able to edit points from other users. The editable layers are configured with editor tracking and in AGOL their settings are set so that users can see all the features but only edit their own.

Once configured in ExB though, the edit widget allows a user to select an existing point (not theirs) and "edit" the attributes or delete it.

Once a user confirms the changes though, they get the following error:

These "edits" fail every time and do not get pushed up to the database, but still it confusing that ExB give the appearance of allowing users to edit any and all points regardless of ownership. How do I configure ExB to not allow users to select points that are not theirs or not make them selectable at all? Or is this impossible and a known fault of ExB?

FYI These screenshots were all taken in the ExB when logged into my orgs test user account, so I know that this is not some issue with my admin permissions overriding the service permissions.

@AlixVezina (I've seen you answering alot of similar questions about ExB I'm hoping you know!)

NicoleJohnson · Answer

Oh no, not one view per editor. When you create the view, you can designate that only the current user's features will be in the view:

You then set your edit widget to this layer instead of the layer that contains everyone's points.

It might be annoying for people to click on one of their features and get two pop-ups, so something you can do is disable pop-ups on the user-specific layer, but keep them enabled on the layer that contains everyone's points (assuming it's helpful for people to be able to see that stuff).

ajohnson · Answer

So I would have to have one view per editor? I have roughly 50 editors for this map unfortunately, how would you add these to web map while still having all the edits sync back to one feature layer?

NicoleJohnson · Answer

I don't know that there's a way to avoid this with one layer, but you could create a view layer based on the editor name and use that instead for your edit widget. Then, keep your all-points layer as just something users can get pop-ups for/see but not have interact with the edit widget.