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

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Restrict access to fields in an article template

# Restrict access to fields in an article template {#ariaid-title1}

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

Use encryption modules to set field-level security in article templates and display
the fields based on role permissions.

## Vorbereitungen

Role required: security_admin  
Hinweis:  
Use Knowledge blocks to restrict the content within the same field. For more information, see [Knowledge blocks](https://servicenow-prod.fluidtopics.net/x13eDltwA3IgGqLRr9O12A "Simplify knowledge authoring for writers and knowledge consumption for readers with knowledge blocks. Knowledge blocks are reusable pieces of content secured by customizable user criteria that controls which users can read or not read the block content in an article or search, enabling users to more easily view content that is relevant to them.").

## Prozedur

1. Create an encryption module for the article template field to be encrypted.  
   See [Create a cryptographic module](https://www.servicenow.com/docs/access?context=create-cryptographic-module&version=australia&pubname=australia-platform-security&ft:locale=en-US) for details.
2. Associate the article template field with the encryption module.  
   See [Encrypting fields and attachments](https://www.servicenow.com/docs/access?context=field-encryption-key-management&version=australia&pubname=australia-platform-security&ft:locale=en-US) for details.
   1. Navigate to System SecurityField EncryptionEncryption Field Configurations and click New.
   2. On the form, fill in the fields.  
      {#secure-field-article-template__table_y2h_dg2_gkb__entry__2}

      | Field | Description |
      |-|-|
      | Table | Table associated with the article template fields. For example, for the How to article template fields, select How To \[kb_template_how_to\]. |
      | Column | Article template field to be encrypted. Only String, Date, Date/Time, and URL fields are supported. * String and URL fields: You can add a new encryption configuration to either a parent table or a child table. * Date and Date/Time fields: You can create encrypted field configurations to encrypt existing Date and Date/Time fields. You can add a new encryption configuration to a parent table only. You cannot add a new encryption configuration to a child table. Hinweis: Depending on the number of records affected by the Date and Date/Time fields you are encrypting, it may take up to a few minutes to create the encryption configuration. Make sure that you create the encryption configuration for Date and Date/Time fields when transaction volume on the instance is low. {#secure-field-article-template__ul_zhw_jj2_gkb} |
      | Encryption module | Encryption module you created for the article template field. |
      | Method | * Single Encryption Module: Enables data to be encrypted with a single encryption module only. The field is encrypted with the encryption module defined in the Encryption module field. Users that do not have the encryption module cannot view or update field values. * Multiple Encryption Module: Enables data to be encrypted with more than one encryption module. The field is encrypted by the encryption context of the first user to enter data. If the user has multiple encryption modules, the context defined in the encryption module selector is used. Because the encryption module is set on a per record basis, fields in a list can have different encryption modules. However, within a single record, the field can be encrypted by only one module. Hinweis: Mass encryption is not available when using the Multiple Encryption module method. {#secure-field-article-template__ul_jnz_sjf_p1b} After a configuration is created using the single encryption module method, you can update the record to use multiple encryption modules. However, you cannot change a field using multiple encryption modules to use a single encryption module. |
      [Tabelle : 1. Encrypted Field Configuration form]

      {#secure-field-article-template__table_y2h_dg2_gkb}
   3. Click Submit.
   {#secure-field-article-template__substeps_drs_mf2_gkb}
3. Define role permissions for the encrypted field.
   1. Navigate to User AdministrationRoles.
   2. In the Name column, click the link to the role you want to allow to view this field.
   3. In the Encrypted context field, search for and select the name of the encryption context for the article template field to apply for the selected role.  
      Hinweis:  
      You may need to configure the Role form to add the Encrypted context field.
   4. Click Update.
   {#secure-field-article-template__substeps_q11_3wb_zbb}

## Ergebnisse

Depending on their role permissions defined for the encrypted field, users can view the field on the article template.
**Zugehörige Informationen**   

* [Field Encryption](https://www.servicenow.com/docs/access?context=field-encryption&version=australia&pubname=australia-platform-security&ft:locale=en-US)