The “snc_required_script_writer_permission” Role in Zurich: A Quiet but Important Change

[Tushar]

If you've recently upgraded to the Zurich release, you might have already bumped into something unexpected: script fields suddenly becoming read-only, even for admins.

The reason? ServiceNow introduced a new role called snc_required_script_writer_permission as part of the broader Scripting Governance improvements.

In short:

• Before Zurich → being an admin (or having other broad roles) usually let you edit scripts freely (Business Rules, Client Scripts, Script Includes, UI Actions, etc.).
• Now in Zurich → script-writing is deny-by-default. You need this specific role to make those fields editable again.

Even full admins lose write access to script fields unless they (or their group) have snc_required_script_writer_permission.

How did people get it? During the upgrade, ServiceNow ran an automatic provisioning job that added this role to many existing users based on certain criteria like past scripting activity. That's why thousands of users in some instances now have it... including some who probably shouldn't if you're trying to tighten governance.

Quick recommendation If your instance is on Zurich and you haven't looked yet, take 5 minutes to review:

1. Navigate to User Administration > Roles and search for snc_required_script_writer_permission
2. See who holds it (or check the Conditional Script Writer group, which automatically grants this role)
3. Decide if the current assignments make sense for your security model

You can remove it from users who don't need scripting access and explicitly grant it (or add people to the Conditional Script Writer group) only for developers.

This change is part of ServiceNow's push for better scripting governance, and once you know about it, it's pretty straightforward to manage. But yeah… it definitely caught a lot of us by surprise because the rollout was pretty quiet and the docs aren't super loud about it yet.