Assignment groups vs. ownership groups

[Aerin]

We are currently using ownership groups to manage creation, etc., of knowledge articles, but my devs want to transfer this functionality back to the standard assignment groups. I can see the pros in terms of minimizing the number of total groups to manage. 

But it got me wondering why there are separate ownership groups to begin with? Is there anything different about how the ownership groups work or functionality associated with them that doesn't go with assignment groups that I'll miss, if I let them make the switch? Is there a best practice from SN's point of view with maintaining this separation?

I'd appreciate any input or experience with this that you'd like to share.

[EricG2]

Our team also did the same thing and opened it up to the Assignment Groups.  Why maintain duplicates?  I also restricted the lookup to only Active and Assignable groups, as we have other groups such as Approvers, CAB Managers, etc.

[JohnnySnow]

Can you tell us how you went about and if you faced any issues? learnings? We are also trying to use our resolver groups as KOGs (knowledge ownership groups) but wasn't sure of the best practice.

[TJohns19]

@Aerin if your assignment groups are pretty much 1:1 with the people in your ownership groups then there is no need for two groups, just manage the exceptions. This is exactly what we do.  We have a few groups that we want to handpick the KBA owners, but we don't want tickets assigned to them and vice versa.  In the Group use the "Type" field to address those exceptions.  Adding 'ITIL' as a "Type" allow tickets to be assigned to that Group.  Adding 'Knowledge' as a "Type" allows it KBA to be assigned to it.  

[Philippe Luickx]

You can add the "type" field to group records and just add the "knowledge" type to your existing assignment groups. That way you can select these as ownership groups.

[shannont]

@Aerin ,

I would caution you specifically on the point of routing approvals to those that an approval is not required from.  We have the KCS Coach role and not all in our Assignment Groups are KCS Coaches.  We have a custom workflow today using existing Assignment Groups, but that has caused some churn in adding KCS Coaches to groups that they only need to be in to receive the approval which causes other issues.  We are moving to Ownership Groups and have requested automation that would add the KCS Coaches only to the Assignment Groups either existing or upon creation of an assignment group, the OG would also be created.  Any OGs without KCS Coaches would be routed to our team to fill gap.

I hope that is helpful!