---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Add a state to a GRC state model

# Add a state to a GRC state model {#ariaid-title1}

Release version: Australia  
Updated September 1, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Add a state to a GRC state model and configure its stepper display, transitions, and attributes.

## Before you begin

The GRC state model must exist. See [Create a GRC state model](https://www.servicenow.com/docs/i76zlRl82tCN~gmUtMzAug "Create a GRC state model to define the states a table's records move through so an issue workflow can use it to control its lifecycle.").

Role required: sn_grc_issue_mgmt.issue_workflow_admin

## About this task

Each state can be configured with its own stepper display, transitions, and attributes.

## Procedure

1. Open the state model.
2. In the GRC Workflow States related list, add each state that records can move through, and specify a sequence number to control the display order.
3. Open a state. {#add-a-state-to-a-grc-state-model__step_open-state}
{#add-a-state-to-a-grc-state-model__step_open-state}
4. Configure the stepper display fields.  
   {#add-a-state-to-a-grc-state-model__entry__2}

   | Field | Description |
   |-|-|
   | Display type | Controls whether the state appears as a node or sub-level in the stepper component. |
   | Stepper label | The label displayed for the state in the stepper component. |
   | Parent node | The parent state for the current state. Applies only when Display type is set to As sub-level. |
   | Is optional | Indicates whether the state can be skipped. |
   [ ]

5. On the Model State Transitions tab, add transitions to other states.
6. If the transition should occur without user action, select Automatic transition.
7. On the State Model Attributes tab, select Edit.
8. In the Collection list, select the attributes that apply to the state, and move them to the State Model Attributes list.  
   Note:  
   A terminal state typically includes either the Default closed state or Default cancelled state attribute. For example, in the Core workflow state model, Closed Complete includes the Terminal state and Default closed state attributes. Closed Incomplete includes the Terminal state and Default cancelled state attributes. See [State model attributes for the Issue table](https://www.servicenow.com/docs/3PU~EvHvnSE6PkJqEh90LA "Attributes available for states in a GRC state model applied to the Issue table.").
9. Select Save. {#add-a-state-to-a-grc-state-model__step_save}
{#add-a-state-to-a-grc-state-model__step_save}
10. Repeat [3](https://www.servicenow.com/docs/FvVK0HqnDJaaLLbHhkj4GA#add-a-state-to-a-grc-state-model__step_open-state) through [9](https://www.servicenow.com/docs/FvVK0HqnDJaaLLbHhkj4GA#add-a-state-to-a-grc-state-model__step_save) for each additional state that you want to include in the state model.

## Result

The state model is saved with its states, transitions, and attributes. You can select the state model when adding components to an issue workflow.
* **[State model attributes for the Issue table](https://www.servicenow.com/docs/3PU~EvHvnSE6PkJqEh90LA)**   
  Attributes available for states in a GRC state model applied to the Issue table.

**Related tasks**   

* [Add the layout, state model, and playbook to a workflow](https://www.servicenow.com/docs/zcAZCb5n~op5~90A~_HBKQ "Attach a layout, state model, and playbook to a workflow to define what it captures, its lifecycle, and how users are guided through it.")
* [Map states to playbook stages](https://www.servicenow.com/docs/2LokRMSeob5Vu1IbS~APyw "Map workflow states to playbook stages so that the issue state and guided activities remain synchronized as an issue moves through its lifecycle.")