In our organization we have several thousand connections communities. As part of our monthly maintenance tasks we contact community owners assigned to communities who have no activity for 90 days and ask them to take action to revitalize or remove the community. It is necessary to give multiple users owner access to large communities due to the nature of connections permissions. So often large numbers of users are contacted and we spend a great deal of time sorting through to find responsible owner.
Being an owner does not necessarily mean that the user is the person responsible for the community. We require a way to identify the Primary person responsible for community maintenance and content. This would allow better communication with the proper "Community Manager".
This could be accomplished by adding a Community Manger (person field) to the Start a community - advanced Features screen...
This could be accomplished by creating a new Role Managing Owner. The additional role option would allow connections clients ,more flexibility when adding components like ICXT allowing for additional permissions of components to be granted to All Owners or to only the Managing Owner(s)
Both options would provide the ability for Connections Clients to identify the person responsible for the community and more effectively communicate with the responsible parties.