Bug in attribute table experience builder editing uneditable layers

[MarianneLindauLanghelle]

I found a potential bug while building a new app in Experience Builder. I have a web map with a number of different layers, where some of them have editing enabled and others have not. I previously added two of the editable layers in the attribute table. Today I wanted to add one of the uneditable ones. But having done so I discovered that it was possible to edit attribute values in the uneditable layer in the attribute table. I double checked that the layer did not have editing enabled and I also got an error message when trying to add it to the edit widget, as it was a "read only" layer. So as far as I can tell this is a bug in the attribute table widget, and a serious one at that. 

[JeffreyThompson2]

Whether or not a layer is editable should be controlled on the server side (ArcGIS Portal or the REST endpoint), so even if you can appear to edit an un-editable feature in Experience Builder, it should not affect the actual data. Can you confirm that the actual data is unchanged?

Within the Table Widget, there is an option to Allow Editing. This should be controllable on a Sheet by Sheet basis. Can you turn it off for the layers you do not want to edit?

[KenBuja]

This could be caused by Esri's editing quirk. If you are the owner of the layer, you can edit records even when editing is disabled. This is what shows when I view the data for a layer that should be uneditable. I can still make changes to the Comments field, for example.

Have you tried using the app with another account to see if it's still editable?

[ChristopherCounsell]

Yeah it's most likely this, admins/owners can always edit even if it's disabled.

Absolute pain when you want to test / see the user experience while you're designing maps, apps and forms.

[KenBuja]

I have a separate account I use for testing how a regular user would see these things.

[BillFox]

is that one using windows authentication to connect to the source?