allow permissions to be set by the administrator at the feature layer level for editing and viewing

L77

Idea:
Allow administrators to define and manage granular permissions for users on feature services, where some users can edit specific datasets while others can only view them. This would enable a flexible permission structure, allowing for secure data access and preventing accidental edits.

Use Case:
In many organizations, different teams or departments manage specific datasets. For example:

• Water and sewer staff should be the only group able to edit the water and sewer feature service, while other staff members need view-only access.

• Noxious weeds staff should have edit rights to their own dataset, but other teams should only have view-only access.

Currently, in ArcGIS Online, users with "Editor" access can edit any feature layer, which is not ideal for cases where data should remain protected or restricted to specific roles. While views can be used to limit access, creating separate views for every dataset is cumbersome and inefficient.

Proposed Solution:
Enable administrators to configure granular edit/view permissions for users at the feature service level, without the need for creating multiple views or additional datasets. This would allow admins to:

• Assign edit permissions to specific groups or users for particular feature layers.

• Restrict other users to view-only access for those same layers.

• Provide a streamlined, centralized approach to managing access and permissions for feature services.

This approach would help ensure that users have access to the data they need, while preventing unauthorized or accidental edits to critical datasets.

Benefits:

• Increased Security: Protect sensitive datasets from accidental or unauthorized edits.

• Simplified Management: No need to create multiple views or duplicate datasets to manage access.

• Flexible Access Control: Tailor permissions to specific roles or teams, enhancing data collaboration and management.

Conclusion:
Introducing granular edit/view permissions for feature services in ArcGIS Online would allow organizations to implement more secure and efficient workflows while ensuring users can access the data they need without the risk of modifying data they shouldn't.

OleNowak

Yes, I would appreciate this as well.

We have the following scenario:

A User with the Creator UserType has editing permissions in general. That's fine.

But in a specific group I want to restrict the user to edit features in a specific feature layer.

Where as the featurelayer may be edited by another user. So on feature layer level, the editing is allowed.

 

One solution is to create Feature Layer Views where editing is not allowed. This would work, but this leads to a whole host of consequences. In this case I have to double all the web maps an reassign the layers to point to the new layer views. And further on, with new web maps, all other apps like Experience Builder and so on have to be doubled, too. 
That's pretty much work.

 

With separated "group permissions" we could solve this better.