I completely get the ask, however, it's not great as a solution in allowing a user to publish data from Pro/local and not being given the chance to manipulate any info etc prior to sharing to a group.
Really should be dealt with by ensuring a Creator is fully aware of the scope of publication and where they want to share with colleagues, they ensure the appropriate group is selected.
I have our AGOL and Portal setup in almost the exact same way:
- Each service are or Team have two groups assigned to them, one that has everyone from the team in it, then one that is an editors' group for creators to work together, create items, then publish.
- In portal I also have a single Organisation Group where, if users want to share information across the organisation, they can do so. I limit all my users to only being able to share to groups - no org share and certainly no public share.
This all seems to work for the 360 users we have at the moment.
