Select to view content in your preferred language

Allow Users to Change Content Ownership without the View All Content Privilege Enabled

5900
12
08-01-2018 01:59 PM
GregMcNamee
Regular Contributor

A useful enhancement would be to allow a user to reassign their own content without requiring the permission to see the content of other users. If the "View all" content administrative privilege is not enabled in a custom publisher role, the user will not be able to reassign the ownership of their content to another folder. In our organization, there is private and confidential data that should not be visible to the entire organization.  Users sometimes need to transfer ownership of their items to another folder without viewing the content of the entire organization. Currently, the "View all" parameter under the Content portion of the Administrative Privilege section, must be enabled to reassign ownership of an item. 

12 Comments
FayDearing

We definitely need this.

PeterKnoop

With close to 7000 users in our org, relying on admins for re-assigning ownership doesn't scale. It is the users that know when ownership needs to be changed, not the admins.

I would like to see this functionality as well, though as a two-step process. Step one being a user creating a request to re-assign any of the content they own to another user within the organization, while step two is that other user accepting the request, at which point the ownership change actually takes place. This would prevent users from inadvertently or maliciously spamming others with content that is not wanted, and it would give the recipient some awareness of the content arriving, if they want to move it elsewhere, rather than it mysteriously appearing.

Alternatively, if the sharing model in ArcGIS Online were evolved to allow groups to own items, rather than just users, then this functionality, and the extra work it places on users, would not be needed for many of the user cases outlined. Ownership of an item could be tied a group, and when one person leaves the group, then that has no impact, nor extra work, for the other collaborators in the group to continue working with the item. (For example, Google Team Drives versus Shared Drives.)