I believe that an Organization or a Groups should be able to own content. This would alleviate a vast majority of overhead when people who own data/maps/apps leave an organization. Instead of having to either create headless users [wasting at least one Named User seat] that would have the overhead of transferring data under their umbrella and having to share this common password or transfer all that data to someone else so that the user can be removed, you would simply have to.. remove the user. Members of the group owning the data would be able add, update, and remove items in that ownership group.
For groups to own data, here are some thoughts on possibly implementing it.
In the group creation, require that the who can change content in the group be all members of the group.
Add a checkbox to group creation "Allow group to own content". If checked, it could create a named user in the background in the group's name [that doesn't take up an actual seat].
From there, the appropriate members could update the maps/apps/layers owned by the Group, and data would then be shared out via a non-data-owning group.
