---
sourceDocument: Yokohama Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Create GRC workflow states

# Create GRC workflow states {#ariaid-title1}

* Release version: Yokohama
* 
* Updated December 5, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Add Governance, Risk, and Compliance workflow states to a state model to define the individual steps in your workflow. Each workflow state represents a phase in the authorization package life cycle and determines what you can do at that
stage.

## Before you begin

Role required: sn_irm_cont_auth.admin

## Procedure

1. Navigate to AllContinuous Authorization and MonitoringAdministrationGRC State Models.
2. Open the state model record to which you want to add workflow states.
3. In the GRC workflow states section, select New to create a workflow state.  
4. On the GRC workflow state New record form, fill in the fields.  
   {#add-workflow-states__table_qt2_4by_thc__entry__2}

   | Fields | Descriptions |
   |-|-|
   | State | Select the state from the drop-down list. |
   | Display type | Select As node or As sub-level to display how the state appears in the authorization package. Note: If the display type for the state is As sub-level, then define the state that serves as the parent node for the sublevel. |
   | Stepper Label | Enter the display name of the state that appears in the authorization package. |
   [Table 1. Governance, Risk, and Compliance workflow state new record form]

   {#add-workflow-states__table_qt2_4by_thc}
5. Select Submit to add the workflow state to the state model.

## Result

The workflow states appear in the workflow states related list on the state model record. After adding all the required states, you can create state transitions to define valid paths between steps.

## What to do next

[Configure transition between state models](https://servicenow-prod.fluidtopics.net/PnanshVyUL3uiK7QktEEuw "Create state model transitions to define valid paths between workflow states. State model transitions control how authorization packages move from one step to another and verify that packages follow the correct sequence through your workflow.")

*[\>]: and then