Edit Privileges at the User Level

[marksm_macomb]

I was wondering if it is possible to manage the edit privileges for each user rather than at the service layer level. For example: maybe you have a team of 10 people, all of whom need to be able to add, delete, and update attributes, but you have 1 person who you want to be able to edit attributes, but not add or delete content across all layers. Is this possible? 

I've looked into custom roles but the toggles for feature editing are very broad - either their edit privileges follow the privileges of each layer, or they have full edit control regardless of the layer's properties. 

[D_Atkins]

Others may have some better suggestions, but one way we handle this is by creating views of our layers, then assigning those views to specific groups (and relevant members to the same groups).  This also allows you to specify field visibility, data filters, and limit extents for each view and group.

[bbollin]

Hi @marksm_macomb, @D_Atkins  is correct. Views are a great way to create tailored editing experiences without needing to create a bunch of copies or maintain separate feature layers. The doc explains more here: https://doc.arcgis.com/en/arcgis-online/manage-data/create-hosted-views.htm

Basically in your case you'd have 
- A hosted feature layer
- View A (add, delete, and update attributes) shared to a group
- View B (attribute editing only) shared to a different group

Any changes in the hosted feature layer will trickle down to the views (but not impact the view specific settings)

I hope this helps!

[D_Atkins]

(I know, not the ideas forum, but...) it would be nice if we could eventually use Views with Referenced Layers in Portal, too!  It would allow our technicians to follow the same workflows without having to republish services!

(Maybe I'm missing a trick here?)