Translated HTML fields and snc_required_script_writer_permission

[SNAdmin47]

We recently upgraded to Zurich and set about using the Scripting Governance Tool, whereby we allocated the ‘snc_required_script_writer_permission’ role to admins or trusted users which might need to do some scripting. Other non-scsripting users were removed. However, what we found was that users without the ‘snc_required_script_writer_permission’  role suddenly can't access 'Translated HTML' fields anywhere in the instance because there's an ACL which prevents write access to anybody without the role and is read only so not easily disabled without ServiceNow assistance.

Unfortunately, one of the 'Translated HTML' fields is the 'Article Body' field on the Knowledge table which effectively means people without the ‘snc_required_script_writer_permission’ role can't create a new KB Article. This seems to be very counter-intuitive, because we need standard itil users to be able to create KB Articles but the only way currently able to do so is to add the ‘snc_required_script_writer_permission’ role as a child role in something like the 'itil' role, which then raises the question of how effective this is supposed to be if every user has it?

Has anybody else hit this issue with the new ‘snc_required_script_writer_permission’ role, and if so, how did you go about allowing basic users to access those translated HTML fields for basic functions such as KB Article writing? The product docs gives very minimal insight or advice on this kind of thing: https://www.servicenow.com/docs/bundle/zurich-platform-security/page/administer/security/concept/scr...

[SNAdmin47 · Accepted solution]

After posting, I found this which was very insightful and answered most of my questions: https://www.servicenow.com/community/servicenow-ai-platform-articles/scripting-governance-tool/ta-p/...