knowledge ownership groups best practice

[JohnnySnow]

Hi Team,

We are in the process of enabling Knowledge ownership groups(KOGs) and I wanted to know if its a best practice to use the existing assignment groups itself and use them as KOGs. 

Has anyone done this? Is it a good practice? are there any challenges of doing this?

[Weird]

Do you mean OOB groups? You can use the existing ones if you want and that's OK.
Sometimes there might be stuff you don't want with the existing groups but that depends a lot on how much demo data you've left around.

If you want to be sure you're not getting anything extra, then create a new group.

If you meant using a group that's used for another task, then it depends on what the tasks are.
If the people on that group are always associated with the knowledge side as well, then it might make sense to use the same group. Using a separate group allows you to add new people into the group without having to worry about possible visibility/access issues on the first group. For example your existing group might have visibility to certain reports, but some users might need access to only the KB instead of the report, so you shouldn't give them the access to the report which is why you'd use a separate group.

tldr if you don't want to worry about any extra stuff, then create a new group.

[Mark Manders]

This really depends on what you are using your groups for. I don't think you want a junior servicedesk employee being responsible as knowledge owner. 

If you have existing groups for these kinds of levels, you can use them, but it's better to create separate groups, so you can really assign the correct users. If you have a 'Microsoft 365' group with all experts, you can use it as knowledge ownership group as well, but as I said: it really depends on the group and what you are using them for.