how disable the restriction to edit that ownership group has?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2022 06:58 PM
I'm using knowledge function to share the information of daily tasks.
When a knowledge is created/updated/retired, our team and related team can get a mail notification to catch a newest information all the time.
The related team is various. It is depends on the article's details.
We use ownership group for setting mail address of notifications, but it makes a problem.
It is unuseful that ONLY the members of the ownership group can edit or retire the article.
I understand the function of ownership group is exiting to remove an incorrect edition or retirement of knowledge articles, but it is not suit for our team management.
So I want to disable this restriction of ownership group.
What function do I change the setting of servicenow?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-23-2023 01:45 AM
Unfortunately User Criteria for Can contribute is not applicable when an Ownership group is set on an article. There is to my knowledge only one option to allow edit for a user which is not member of the ownership group, and that is by setting property glide.knowman.ownership_group.override to false. On the other hand, this only allows Author of the article to edit, no one else. I am also looking for a way to allow multiple groups to edit an article, not only the Ownership group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-11-2023 03:16 AM
Hi Tera contributor,
I do have the same requirement, did you find the solution?
Regards,
Khadar Basha V

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-22-2022 10:13 PM
Hello,
Could you please check any ACL in place which allows only ownership group to perform the actions in knowledge base.
Thanks,
Priyanka R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2023 08:10 PM
Dear @MR6
@MR6 and @khadar , hope you're doing great!
- Navigate to System Administration.
- Security
- Access Controls.
- Click on the New button.
- In the Name field, enter a name for the new access control.
- In the Type field, select Record.
- In the Table field, select the kb_knowledge table.
- In the Operation field, select Update.
- In the Conditions section, add the following condition:
- Condition: Owner group
- Operator: Is not
- Value: [Ownership group name]
- Click on the Save button.
Once you have created the new access control, you will need to assign it to the users or roles that you want to be able to edit or retire knowledge articles that are owned by other groups.
Note: Disabling the restriction of ownership group can have security implications. It is important to carefully consider the risks before making this change.
Recommendation:
In your case, I recommend that you create a new access control to allow users to edit or retire knowledge articles that are owned by other groups. This will allow you to disable the restriction of ownership group without compromising the security of your knowledge articles.
You can also consider using the kb_notification table to send notification emails to specific users or groups when a knowledge article is created, updated, or retired. This would allow you to send notification emails to the related team for each knowledge article, even if the related team is different for each knowledge article.
Kindly, please mark my solution as Helpful/Correct, if applicable.
Thanks & Regards,
Revanth. K
Product Test Automation Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-18-2023 11:04 PM
Good morning Revanth! There is no Update operation in ACL's. Do you mean Write? And do you mean to create one ACL for each ownership group you don't want to restrict updates to?
//Per