---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Manage Scripting Governance Tool

# Manage Scripting Governance Tool {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Manage Scripting Governance Tool

The Scripting Governance Tool in ServiceNow helps enforce scripting access policies by managing user permissions and group memberships related to script writing.
It operates in either an enabled or disabled state, controlled exclusively by users with thesecurityadminrole.
This tool is enabled by default on your instance, ensuring that scripting governance policies are actively enforced.
Show full answer Show less  

## Key Features

* **Enabled State:** When enabled, the tool enforces scripting governance policies, evaluates user access against scripting rules, and provisions users to the Conditional Script Writer group accordingly. Security admins can run scans, manage group memberships, and review audit logs for scripting access.
* **Disabled State:** When disabled, all scripting governance policies and associated ACLs are deactivated. Users are not evaluated or assigned to script writer groups, although existing memberships remain without enforcement. The interface remains accessible to security admins but scanning and access management functions are inactive.
* **Role-Based Control:** Only users with the **securityadmin** role can enable or disable the tool and modify related properties, ensuring secure governance management.
* **Scheduled Job Management:** Enabling or disabling scripting governance runs specific scheduled scripts that activate or deactivate properties and manage membership jobs for the Conditional Script Writer group.

## Practical Actions for ServiceNow Customers

* **To Disable Scripting Governance:** Navigate to *All \> Scheduled Script Executions* and run the **Disable Scripting Governance** script. This deactivates key properties, stops membership provisioning jobs, and removes users from the Conditional Script Writer group via a scheduled job.
* **To Enable Scripting Governance:** Navigate to *All \> Scheduled Script Executions* and run the **Enable Scripting Governance** script. This activates necessary properties, schedules user provisioning jobs, and enforces scripting access policies again.

## Key Outcomes

* Maintaining enabled status ensures controlled and auditable scripting access, reducing security risks associated with unauthorized scripting.
* Disabling the tool temporarily suspends enforcement but preserves group memberships and configuration for seamless reactivation without data loss.
* Role-restricted control and scheduled job automation streamline governance administration for security admins.  
Enable or disable the Scripting Governance Tool on your instance by running the appropriate script. Only users with the <kbd class="ph userinput">security_admin</kbd> role can run these scripts and modify the associated
properties.

## Scripting Governance Tool states {#manage-sgt__sgt-states}

Scripting Governance Tool operates in one of two states. The active state determines whether scripting governance policies are enforced and whether users are provisioned to the Conditional Script Writer group.  
Note:  
* Scripting Governance Tool is enabled by default. You can choose to disable.
* You must elevate your role to <kbd class="ph userinput">security_admin</kbd> to enable or disable Scripting Governance Tool.
{#manage-sgt__ul_fsm_cjr_djc}
{#manage-sgt__table_chd_vxm_djc__entry__2}

| States | Behavior of Scripting Governance Tool |
|-|-|
| Enabled | * Scripting Governance Tool and all associated ACLs are active on the instance. * Users are evaluated against scripting access rules and assigned to the appropriate script writer groups. * The <kbd class="ph userinput">security_admin</kbd> can run scans to identify users with scripting access and manage group membership. * Scripting governance policies are enforced across all applicable records and transactions. * Audit logs and visibility into scripting access are available to the security admin. {#manage-sgt__ul_fp3_xxm_djc} |
| Disabled | * Scripting Governance Tool and all associated ACLs are deactivated on the instance. * No scripting governance policies are enforced. Users are not evaluated or assigned to script writer groups. * Existing group memberships from a prior enabled state are preserved but have no enforcement effect. * The Scripting Governance Tool interface remains accessible to the security admin but scanning and access management actions are inactive. * Scripting Governance Tool can be re-enabled by the <kbd class="ph userinput">security_admin</kbd> at any time without data loss. {#manage-sgt__ul_h5z_xxm_djc} |
[Table 1. Scripting Governance Tool states]

{#manage-sgt__table_chd_vxm_djc}

## Disable scripting governance {#manage-sgt__disable-sgt}

To disable Scripting Governance, navigate AllScheduled Script Executions (<kbd class="ph userinput">sysauto_script_list.do</kbd>) and run the Disable Scripting Governance script to deactivate Scripting Governance Tool on your instance.

Running this script performs the following actions:

* Disables the `glide.security.scripting_role.provisioning_job_running` property.
* Disables the `glide.security.scripting_role.auto_provisioning` property.
* Disables the `glide.security.scripting_governance.enabled` property.
* Disables the Add Users to Conditional Script Writer Group and Update Users in Conditional Script Writer Group scheduled jobs.
* Removes all users from the Conditional Script Writer Group through a scheduled job.
{#manage-sgt__ul_hlj_zzm_djc}

## Enable scripting governance {#manage-sgt__enable-sgt}

To enable Scripting Governance, navigate AllScheduled Script Executions (<kbd class="ph userinput">sysauto_script_list.do</kbd>) and execute the Enable Scripting Governance script to activate Scripting Governance Tool on your instance.

Running this script performs the following actions:

* Enables the `glide.security.scripting_role.provisioning_job_running` property.
* Enables the `glide.security.scripting_governance.enabled` property.
* Enables the Add Users to Conditional Script Writer Group and Update Users in Conditional Script Writer Group scheduled jobs.
* Schedules the Add Users to Conditional Script Writer Group job to run.

*[\>]: and then


