---
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


---

# Enforce field-level ACLs on records created from the filtered list view UI query string

# Enforce field-level ACLs on records created from the filtered list view UI query string {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Use a system property to prevent list filters from affecting the initial values of created records.
Use the com.glide.acl_check_all_filter_on_new system property to confirm field level ACLs are evaluated when query string parameters are applied during the creation of new table records triggered from the
UI.

How filter query strings work:

When a new record is created from the list view UI, field values from the filter query string are applied to it.

For example, using this filter:

    author={62826bf03710200044e0bfc8bcbe5df1}^state={3}

The Author field is assigned the value <kbd class="ph userinput">62826bf03710200044e0bfc8bcbe5df1</kbd> and State is assigned the value <kbd class="ph userinput">3</kbd>, regardless of their default
value.

The com.glide.acl_check_all_filter_on_new property verifies that field level ACLs are evaluated for all fields when a record is created from the filtered list view UI of a table.

However, exceptions are applied in the following order:

1. If the ignore_filter_on_new dictionary attribute is set for a field, the value of that field is never used during record creation from the filtered list view.
2. If the acl_check_filter_on_new dictionary attribute is set for a field, ACLs must be checked for that field during record creation from the filtered list view.
3. If the allow_filter_on_new dictionary attribute is set for a field, ACLs aren't checked for that field during record creation from the filtered list view.
4. The sys_domain field and other domain fields defined by the glide.sys.domain.domain_determining_field.{table_name} property aren't checked by ACLs on record creation from the filtered list view.
5. If the com.glide.acl_check_all_filter_on_new system property is set to <kbd class="ph userinput">true</kbd>, ACLs must be checked for all other fields during record creation from the filtered list.
6. If a field's type is listed in the com.glide.ignore_filter_on_new.field_types system property, ACLs must be checked for that field on record creation from the filtered list view.

{#sc-enforce-field-level-acls-on__ol_tkz_x11_b3c}

Confirm that the com.glide.acl_check_all_filter_on_new system property is set to <kbd class="ph userinput">true</kbd>.

## More information {#sc-enforce-field-level-acls-on__section_wc1_cqn_phc}

{#sc-enforce-field-level-acls-on__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Configuration name | com.glide.acl_check_all_filter_on_new |
| Configuration type | System Properties (/sys_properties_list.do) |
| Data type | Boolean |
| Recommended value | true |
| Default value | false |
| Fallback value | false |
| Category | [Access control](https://www.servicenow.com/docs/x7vcJqvJ0dwOasc9M2~48A "The access control category audits the process of protecting resources from unauthorized access through granting and denying requests based on a permission model. This includes ensuring an entity accessing a resource holds valid credentials to do so, creating and protecting a well-defined set of roles or permissions and ensuring role or permission controls are protected from replay and tampering.") |
| Security risk | * Severity score: 4.8 * CVSS score: Medium * Security risk details: When com.glide.acl_check_all_filter_on_new is set to <kbd class="ph userinput">false</kbd>, then ACLs aren't checked for fields on new record creation from the filtered list view UI of a table, unless one of the other exceptions applies. In this state, users without create access to fields can bypass ACLs by setting protected fields through filter query strings during record creation. This allows protected fields to be set to improper values on record creation through the filtered list view UI of a table. {#sc-enforce-field-level-acls-on__ul_g1g_3sf_xwb} |
| Functional impact | When com.glide.acl_check_all_filter_on_new is set to <kbd class="ph userinput">true</kbd>, ACLs are enforced for fields included in the filter query string during record creation from the list view UI. This prevents users without create access from modifying protected fields through filter parameters. |
| Dependencies and prerequisites | None |
[ ]

{#sc-enforce-field-level-acls-on__table_ajc_b43_3kb}

