---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Automate Configuration Assignment policy process

# Automate Configuration Assignment policy process {#ariaid-title1}

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

Automate assigning configurations and AWS organizational units in requests based on specified conditions. When conditions are met and approvals are complete, requests move forward without admin input. Update the default policy to include specific
conditions and values for configuration and AWS organizational unit.

## Before you begin

Role required: sn_itom_cam.cw_admin

## About this task

This procedure demonstrates how to assign account configuration using the assignment policy. For example, when the account creation request is approved and awaits for the provisioning configuration
information, this automation is executed.

## Procedure

1. Navigate to AllCloud WorkspaceRequest Policies.
2. Select Subscription Account Creation Configuration Assignment.
3. Customize the policy by selecting Create copy.
4. Under the Policy builder tab, in the If condition block, make a note of the values that you're validating.  
   Note:  
   In this section, you're validating:
   1. Environment = Development
   2. Business unit = business-app-1
   {#automate-account-creation-config-assign__ul_jwz_skw_ycc}
5. To select the configuration and AWS org unit output, select Data collectors from the Data sources section.
6. Select Add.
7. Select Get Config Assignment Results.
8. In the Add data collector pop-up, enter <kbd class="ph userinput">Label</kbd> and <kbd class="ph userinput">Variable name</kbd>.  
   These field values are only used to identify the data collector.

9. Under the Inputs tab, select CW Application Configuration and CW Account Group (same as the AWS org unit that an admin selects on the account request screen).  
   Note:  
   The selected AWS org unit in the data collector should be part of the same Cloud Organization provided in the configuration.
10. Select Save.  
    The new data collector entry is saved. Only when the If condition is met, the then condition get executed.
11. Select the output result as follows.  
12. To save the policy, select Save.  
    Note:  
    * If necessary, you can enhance the Log message for the result. For some examples, you can see the default-published policies.
    * Map only one policy according to automation.
    * This configuration approval policy is inactive by default. You can deactivate to stop the automation.
    {#automate-account-creation-config-assign__ul_o2f_vpm_zcc}
{#automate-account-creation-config-assign__steps_s3k_xwx_ycc}

## What to do next

To test the policy, see [Test updates to a PaCE policy version](https://www.servicenow.com/docs/access?context=pace-test-policy-version&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

To publish the policy, see [Publish a PaCE policy version](https://www.servicenow.com/docs/access?context=pace-publish-policy-version&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

To add a new approval step in the flow designer, see [Using Workflow Studio](https://www.servicenow.com/docs/access?context=building-workflow-studio-components&version=yokohama&pubname=yokohama-build-workflows&ft:locale=en-US).

*[\>]: and then