On the New Collection page, the user should have the option to share a collection with all registered users.
Makes it easy for a user to share a collection with everyone.
When I am creating a new collection, and I am ready to select with whom to share it, I need the ability to share it with the group of all users who have repository accounts.
I can only share my collection with the admin group, which has very little utility to me as a collection creator who wants to share it more broadly.

@hannahfrost Do you see this being used to share 'read' access with all registered users, or 'edit' access, or both?
@mjgiarlo I had pondered this initially and came to the conclusion that both options should be available. I suspect that 'read' access will be used much more frequently than 'edit', but I can imagine use cases for both. Thanks for checking.
@hannahfrost I ask because granting all registered users "read" is essentially the same as assigning it the 'institution' visibility. But since 'edit' is a requirement, this is new work to be done.
@mjgiarlo IMO, that is an argument against allowing a different representation of "Institution" visibility. I.E., we should ONLY provide sharing "edit" access to registered users as a group. Otherwise, for read, we should direct users to change the visibility.
@mjgiarlo Right, I realized this while I was riding my bike home from work (seriously). And I think I agree with @atz. Let's talk this over sometime soon, no big rush. The way we are elevating collections now for discovery purposes, it would be helpful to work through how the collection sharing functionality fits.
In Hyrax 3.0.2 the "add group" box for collections is a search box, rather than a drop-down as initially reported. It is possible to add all repository users to a collection by searching for the "registered" group and then adding to the appropriate role.
While this is technically resolved, the solution is not intuitive to users and may need additional work. @jlhardes
I think this connects to #227 and possibly the proposed changes from @no-reply in #4686.