disable add/delete column from attribute tables

[jakubk]

I've realised that users with edit permissions on a hosted feature layer can totally mess with the schema of attribute tables

What/how do I configure/set it up so that users can view/edit/add/delete rows in attribute tables but dont have modify schema permissions

[ChristopherCounsell · Accepted solution]

Users shouldn't have permissions to update schema tables as part of standard workflows?

https://doc.arcgis.com/en/arcgis-online/manage-data/work-with-fields.htm

Only the Owner or Administrators (or roles with administrator priveleges) can do this by default.

The exception is if you are sharing your layer through a Shared Update Group. This is a super-user group that would allow others to update your maps, layers and apps with capabilities similar to that of being the owner.

https://doc.arcgis.com/en/arcgis-online/share-maps/create-groups.htm#ESRI_SECTION1_12B3CD7ADAF843DB9...

So to avoid this scenario you need to change your group (recreate it and share again) or reconsider who has administrator privileges in your organization.

[jakubk]

Thanks, 

the org im at has organically grown bigger and used the 'just give everyone admin' approach to onboarding to limit downtime and not having a dedicated agol admin

I'm not one either - business intelligence/data warehousing.  Are there any beginners guides/best practise to how to manage read only/edit that you can recommend?  I've noticed that agol takes a different approach to most other data driven apps I use as data sources when it comes to config/data admin/integration