---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Configure the compliance dynamic schema

# Configure the compliance dynamic schema {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Review and adjust the dynamic namespace that supports the risk and compliance fields on a change request. Ensure the attributes and categories match the compliance obligations of your organization.

## Before you begin

Decide which risk and compliance details your organization records with every change, because the attributes and categories in the base system are examples.

Role required: admin

## About this task

The compliance dynamic schema for change requests is delivered as a single dynamic namespace. Configuring the namespace changes which attributes users can record in the Risk and compliance attributes field
and which categories they can select in the Risk and compliance category field. For information about the elements that make up the schema, see [Compliance dynamic schema](https://www.servicenow.com/docs/BX4wyzdoAo3hDiukpR2I2A "Compliance dynamic schema stores the risk and compliance details of a change as name and value pairs in a single field. This avoids adding a column to the Change Request table for each detail.").

## Procedure

1. Navigate to AllChangeAdministrationCompliance Dynamic Schema.  
   The module opens the `change_request/risk_and_compliance_attributes` dynamic namespace record directly. You can also reach the same record from the platform by opening the Dynamic Namespaces list.
2. Review the fields on the dynamic namespace record.  
   {#configure-compliance-dynamic-schema__table_dynamic_namespace__entry__2}

   | Field | Description |
   |-|-|
   | Label | Display name of the namespace. For change requests, the label is `Change request/risk and compliance attributes`. |
   | Name | System name of the namespace, `change_request/risk_and_compliance_attributes`. Scripts use this name to read the stored attributes. |
   | Description | Purpose of the namespace. |
   | Application | Application that the namespace belongs to. |
   | Active | Option for making the namespace available to the store field. |
   [Table 1. Dynamic Namespace form]

   {#configure-compliance-dynamic-schema__table_dynamic_namespace}
3. On the Dynamic Attributes tab, review the attributes that users can record.  
   The related list shows the name, label, type, choice set, description, and active state of each attribute. To add or update a dynamic attribute, see [Dynamic Schema](https://www.servicenow.com/docs/access?context=dynamic-schema&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).
4. Select the Dynamic Categories tab and review the categories that users can select.  
   A category groups the attributes that are relevant to a kind of change. Set the Parent field to place a category below a broader category, so that the category inherits the attributes of its parent.
   To add or update a dynamic category, see [Dynamic Schema](https://www.servicenow.com/docs/access?context=dynamic-schema&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US).
5. **Optional:** Select the Dynamic Choices tab to review the values that a choice set offers.  
   A dynamic choice belongs to a choice set that an attribute of type `String` references. The Order field determines the sequence of the values, and the Value
   column holds the string that is stored on the change request.
6. **Optional:** Select the Dynamic Choice Overrides tab to review the choices that are overridden for a category or an attribute.
7. Deactivate the attributes and categories that are not required, and add the ones that are.  
   Clear the Active check box on a record rather than deleting it, so that the values already recorded on existing change requests remain readable.

## What to do next

Add the Risk and compliance attributes and Risk and compliance category fields to the Change Request form. For information about recording values in the fields, see [Create a change request](https://www.servicenow.com/docs/d9g1mmI~EBDHDZIOuOoM7Q "Create a change request to implement a controlled process for modifying approved and supported configuration items (CIs).").
**Related concepts**   

* [Compliance dynamic schema](https://www.servicenow.com/docs/BX4wyzdoAo3hDiukpR2I2A "Compliance dynamic schema stores the risk and compliance details of a change as name and value pairs in a single field. This avoids adding a column to the Change Request table for each detail.")  
**Related topics**   

* [Dynamic Schema](https://www.servicenow.com/docs/access?context=dynamic-schema&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US)

*[\>]: and then