Ownership groups best practices

[Olga_B]

Hi everyone, 

we are currently exploring options to use ownership groups instead of individual authors being responsible for the articles' maintenance and I have a few questions in this regard: 

1. Is ownership group defined on the KB or KBA levels, is there an option to consider?

1. We have different business departments who are using knowledge management app and not all of them are ready to use ownership groups, if the glide.knowman.ownership_group.enabled  property is activated - is it mandatory to use ownership groups on all articles regardless of the knowledge base it is created in?

2. When article is created and ownership group is not assigned, will publish and approval workflows defined for that KB still be applicable?

3. When glide.knowman.ownership_group.enabled property is enabled what is required to be done with already defined workflows on the KB level?

[Satishkumar B · Accepted solution]

@Olga_B 

1. Ownership Group Definition:

   • Level of Definition: Ownership groups can be defined at the Knowledge Base (KB) or Knowledge Article (KBA) levels. This allows you to have flexibility in managing article ownership.
   • Option to Consider: You can decide to apply ownership groups broadly at the KB level for all articles or set specific ownership groups for individual KBAs if needed.

2. Impact of glide.knowman.ownership_group.enabled Property:

   • Mandatory Usage: If the glide.knowman.ownership_group.enabled property is activated, it is not mandatory for all knowledge articles across all knowledge bases to use ownership groups. Departments that are not ready to use ownership groups can continue as usual, while others can start using them.
   • Selective Application: This property enables the use of ownership groups, but it does not enforce them across all KBs unless you configure the specific KBs to require them.

3. Behavior When Ownership Group is Not Assigned:

   • Workflows Applicability: If an ownership group is not assigned to an article, the publish and approval workflows defined for the KB will still be applicable as per usual. The presence or absence of an ownership group does not override the workflows unless explicitly configured otherwise.

4. Impact on Existing Workflows:

   • No Immediate Changes Required: When you enable the glide.knowman.ownership_group.enabledproperty, there is no immediate need to modify existing workflows at the KB level. The existing workflows should continue to function as they were before the property was enabled.
   • Future Considerations: However, if you intend to incorporate ownership groups into your workflows (e.g., requiring approval from an ownership group), you may need to update your workflows to include these new conditions.

This approach provides a flexible transition to using ownership groups without disrupting current operations and workflows.

please mark my response is helpful 👍and accept the solution ✅if it helps you

[Olga_B · Accepted solution]

Thank you @Satishkumar B this is very helpful! Follow-up question , if possible, when ownership group is configured on the KB level - will the field appear for configuration only after property is enabled? will additional steps be required to update the KB form layout? Thank you in advance!

[Satishkumar B · Accepted solution]

@Olga_B 

1. Ownership Group Definition:

   • Level of Definition: Ownership groups can be defined at the Knowledge Base (KB) or Knowledge Article (KBA) levels. This allows you to have flexibility in managing article ownership.
   • Option to Consider: You can decide to apply ownership groups broadly at the KB level for all articles or set specific ownership groups for individual KBAs if needed.

2. Impact of glide.knowman.ownership_group.enabled Property:

   • Mandatory Usage: If the glide.knowman.ownership_group.enabled property is activated, it is not mandatory for all knowledge articles across all knowledge bases to use ownership groups. Departments that are not ready to use ownership groups can continue as usual, while others can start using them.
   • Selective Application: This property enables the use of ownership groups, but it does not enforce them across all KBs unless you configure the specific KBs to require them.

3. Behavior When Ownership Group is Not Assigned:

   • Workflows Applicability: If an ownership group is not assigned to an article, the publish and approval workflows defined for the KB will still be applicable as per usual. The presence or absence of an ownership group does not override the workflows unless explicitly configured otherwise.

4. Impact on Existing Workflows:

   • No Immediate Changes Required: When you enable the glide.knowman.ownership_group.enabledproperty, there is no immediate need to modify existing workflows at the KB level. The existing workflows should continue to function as they were before the property was enabled.
   • Future Considerations: However, if you intend to incorporate ownership groups into your workflows (e.g., requiring approval from an ownership group), you may need to update your workflows to include these new conditions.

This approach provides a flexible transition to using ownership groups without disrupting current operations and workflows.

please mark my response is helpful 👍and accept the solution ✅if it helps you

[hamed_abdy]

Hi,

1. how to set ownership group at KB level for all articles (are you referring to setting default values) ?

I do not see any ownership filed at the KB level.

Thanks

[Olga_B · Accepted solution]

Thank you @Satishkumar B this is very helpful! Follow-up question , if possible, when ownership group is configured on the KB level - will the field appear for configuration only after property is enabled? will additional steps be required to update the KB form layout? Thank you in advance!

[Satishkumar B · Accepted solution]

@Olga_B When you configure an ownership group on the Knowledge Base (KB) level, the field's visibility and availability depend on the glide.knowman.ownership_group.enabled property:

• Field Visibility: Explains that the ownership group field is not available until the property is enabled.
• Form Layout Update: Clarifies that the field might need to be added to the form manually if it doesn’t automatically appear.

please mark my response as helpful👍 and accept the solution✅ if it helps