---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Define a not-allowed CI action

# Define a not-allowed CI action {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Define a restriction for CI Lifecycle Management in which a specified action is not
allowed for a CI that is in a specified operational state.

## Before you begin

Role required: none

## About this task

By default, there are no restrictions in the CMDB CI Lifecycle Management on applying
CI actions. You can restrict this behavior by not allowing a specified action to be
applied to a CI when it is in a specified operational state. For example, you can
define a restriction in which the provisioning action cannot be applied to a Linux
Server that is in a non-operational state.

## Procedure

1. Navigate to AllConfigurationCI Lifecycle ManagementNot Allowed CI Actions.
2. Click New on the Not Allowed CI Actions page, and fill out the form.  
   {#non-allowed-cmdb-ci-action__table_x1h_zgj_kw__entry__2}

   | Field | Description |
   |-|-|
   | Not Allowed Action | The action that is being restricted. |
   | CI Type | The CI type for which the restriction applies to. To apply a rule to all CIs, select Configuration Item. |
   | Operational State | The operational state that the CI must be at in order to apply the restriction. |
   [ ]

   {#non-allowed-cmdb-ci-action__table_x1h_zgj_kw}
3. Click Submit.

## Result

If an API attempts to apply the specified action to the specified CIs, while it is in the specified operational state, the operation fails and an error is logged.

*[\>]: and then