Hey,

This is hopefully going to be a pretty straight forward request, we have a number of different teams that are looking to use Guru as their primary knowledge tool, but as Guru can only connect to one slack workspace, that means that we’re going to potentially have more teams using Guru - which is great.

However, the likes of Accounting don’t need access to Support docs and vice versa, which is obviously all solved through Groups - which is grand. However, there’s no way to organise, or categorise the number of groups, so they’re going to need verifiers and author groups of their own, along with anything else that they might need, which means that this section is going to grow and expand, but the issue is that we currently have 50 groups - which range from product visibility, to verification, region, office and team level so we can get snapshot reports when necessary.

However, with the number of teams planning on getting involved in Guru, this is going to create a number of additional groups, and no way of categorising them.

What would be useful would be ability to use “Board Group” esque structure for this.

The same sort of structure could be applied to the “Collections” which would allow admins to “group” (for lack of a better term) collections belonging to one team under one heading, which could make it easier for Collection Management going forward as well.