---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Datatype ACL

# Datatype ACL {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

The datatype ACL enables you to write ACL rules that apply to all fields of a specific type.

Datatype ACLs provide a targetted approach to access controls by restricting table fields based on data type. This allows for broader security constraints than wildcard(\*) ACLs. The syntax for datatype ACLs follows the format
\*.\[<kbd class="ph userinput">(field to be restricted)</kbd>\].

Conventional field ACLs are limited to specific table-field identifiers, all fields in a table, or all tables with a specific field name, in contrast the datatype ACLs enable you to apply security uniformly across fields that share
certain metadata. This helps prevent creating additional ACLs to apply security uniformly across all fields.

When implementing datatype ACLs, its essential to validate all affected fields before and after adding them to avoid unexpected security issues. See [Create a datatype ACL](https://servicenow-prod.fluidtopics.net/x0or4IyZ77dDMM68vrEVqw "Learn how to create a datatype ACL.") to create your own datatype ACL.

To review existing datatype ACLs navigate to AllSystem SecurityAccess Controls and use the Name field to search for ACLs that start with <kbd class="ph userinput">*.[</kbd>.  
Hinweis:  
Scripting Governance uses datatype ACLs by default for scripting restrictions, see _ for more details.