Role-based access control

[GrantFox]

The current implementation of 'ownership-based access control' is limited to the user level. Expected functionality of this would be that features could be controlled based on role membership. Example: I want to ensure that only users that belong to a functional group within a company can edit features under that groups control.

[JoshuaBixby]

Four years, no progress, I won't be holding my breath, but I did up vote because role-based access control is at the heart of any true enterprise system.

[Anonymous User]

Do groups with update capability help solve this issue?

Organization administrators can create groups that allow members to update items that have been shared with the group. Groups created with this item update capability are useful in collaborative situations in which multiple people need to update the same item—for example, shift workers in operations centers who need to update the maps underlying their apps and dashboards.

https://enterprise.arcgis.com/en/portal/latest/administer/windows/create-groups.htm

[Sarah_Hanson]

When creating a group, organization administrators can enable shared update, which will allow items that are shared to that group to be editable by any group members. This will allow members other than the item owner, to edit and update any related items. 

https://enterprise.arcgis.com/en/portal/latest/administer/windows/create-groups.htm

If this does not address your concerns, please create a new idea with additional details regarding your request.