Hmm, maybe. I think I'm more excited about an implementation of #236 as a next step towards making progress on the direction of scaling the user lists; I think it's very possible the right solution here for the administration page is just to have a good search feature.

Depending on the use-case, a group-based approach can be nice in that, with some additional modifications, it enables a User creating a Stream to easily subscribe an entire swag of Users (versus picking through the entire User list).

This suggestion could be more of an "and" rather than an "or" with #236.

@Alpus We've implemented this approach in our project and it works well. Our project has made enough mods so to not be able to merge back, but I can share some code and screenshots, if interested.

Cool @danshev. Some screenshots of how you did groups support would be great! One of the big challenges with this sort of thing is always figuring out how to make the UI for a groups feature work well.

Our access paradigm is very different, so our implementation can thankfully be pretty basic. Just sharing for the sake of ideas for others:

1. In a User's profile settings page, they can freely subscribe / unsubscribe to / from Groups:
   
2. For subscribing an entire Group to a Stream, we use the TextExt jQuery Plugin to handle the UI. The plugin takes a suggestions array, which we populate with people.get_rest_of_realm() and a list of the Realm's Groups, which we pass on initial load as page_params.group_list.

Using TextExt creates a little work as far as reversing from full_name to email, but the UI is much better. For any value that doesn't resolve to an email (i.e. a Group name), we just pass the Group name. This requires a little work in streams.py on the backend (i.e. handling email addresses and raw group names), but it's not too bad.

Cool. Your screenshots reminded me that it'd be great to have that kind of name boxes in the compose box, so I opened #595 for that issue.

We've now implemented groups in Zulip, closing.