--- title: Set Conditional Rules on Multiple Objects slug: neurons-for-itsm/admin-user-help/enu/latest/set-conditional-rules-on-multiple-objects createdAt: 2026-08-25T16:13:06.000Z --- The Bulk Update Rules feature lets you apply a conditional rule to multiple roles and business objects at the same time, instead of configuring each object individually. As an administrator, you select the roles and business objects, enter a conditional rule, and use the color-coded preview to see which objects accept the rule before you apply it. After you apply the rules, you can verify them in Object Permissions in the Admin UI, and you can roll back selected roles to their previous state. This topic covers the prerequisites for the feature, how to apply and preview rules, how to verify and roll them back, and how bulk conditional rules interact with the single role editor. ## Apply Bulk Conditional Rules 1. Log in to ITSM with the **Admin** role, and then open the **Admin** UI. 2. In the left pane, go to **Configure > User and Permissions > Roles and Permissions.** 3. Select **Bulk Update Rules.** ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/iaspmzY4doShWUZsfApyZ_bulk-updates.png" position="flex-start" size="80" width="1326" height="666" initialPath="../../Resources/Images/Configure/Users and Permissions/Bulk Updates.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Bulk Updates.png" darkWidth="1326" darkHeight="666" showCaption="false" indent="1"} 4. On the **Bulk Update Conditional Rule** page, select one or more roles and business objects, and then enter the conditional rule to apply. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/0mog5mMIrQvRIiE5ve7WB_bulk-update.png" position="flex-start" size="80" width="1326" height="672" initialPath="../../Resources/Images/Configure/Users and Permissions/Bulk Update.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Bulk Update.png" darkWidth="1326" darkHeight="672" showCaption="false" indent="1"} 5. Select **Preview**. :::hint{type="info"} The page shows the result for each business object. Business objects that accept the rule appear in green, and business objects that do not accept the rule appear in yellow. For example, if you set the rule **Address = Test123** for the **Address** business object, the rule does not apply because the **Address** business object does not contain an Address field. In the same preview, both conditional rules apply to the **Account** business object for every selected role. ::: ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/TrsHfVWr-7qKNri1HwkBY_preview-changes.png" position="flex-start" size="80" width="1348" height="680" initialPath="../../Resources/Images/Configure/Users and Permissions/Preview Changes.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Preview Changes.png" darkWidth="1348" darkHeight="680" showCaption="false" indent="1"} 6. Select **Apply to \ Objects**. The application saves the conditional rules. ### Verify the Applied Rules 1. Refresh the application. 2. Go to **Configure > User and Permissions > Roles and Permissions > Admin > Object Permissions > Account**. 3. In the **With Access** column, select **Edit**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/3kToXYaoGFBtIYGW2jUs9_object-permission.png" position="flex-start" size="80" width="1407" height="717" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permission.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permission.png" darkWidth="1407" darkHeight="717" showCaption="false" indent="1"} 4. The expressions from the bulk conditional rule appear. 5. Repeat the previous steps for the **Asset Administrator** role to confirm that the expressions are added. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/7I_u0ywMW9llSTWzksGEE_object-permissions.png" position="flex-start" size="80" width="1405" height="697" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions.png" darkWidth="1405" darkHeight="697" showCaption="false" indent="1"} ### Roll Back Bulk Conditional Rules 1. Go to **Configure > User and Permissions > Roles and Permissions > Bulk Update Rules**. 2. Select **Rollback**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/gwK5y4VyM0Yjn0fo3YFWr_bulk-update-conditional-rules.png" position="flex-start" size="80" width="1406" height="720" initialPath="../../Resources/Images/Configure/Users and Permissions/Bulk Update conditional rules.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Bulk Update conditional rules.png" darkWidth="1406" darkHeight="720" showCaption="false" indent="1"} 3. In the dialog box, select the roles to roll back, and then select **Rollback**. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/PBMVQRETRKO6p8OH0jvko_rollback-conditional-rules.png" position="flex-start" size="80" width="1400" height="703" initialPath="../../Resources/Images/Configure/Users and Permissions/Rollback conditional rules.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Rollback conditional rules.png" darkWidth="1400" darkHeight="703" showCaption="false" indent="1"} 4. When the rollback finishes, the **Bulk Update Conditional Rules** page displays a confirmation message. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/nynVdFWAa1l3Efkb-eyrx_rollback-conditional-rules-1.png" position="flex-start" size="80" width="1402" height="707" initialPath="../../Resources/Images/Configure/Users and Permissions/Rollback conditional rules 1.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Rollback conditional rules 1.png" darkWidth="1402" darkHeight="707" showCaption="false" indent="1"} ### Verify the Rollback 1. Refresh the **Admin** UI. 2. Go to **Configure > User and Permissions > Roles and Permissions > Admin > Object Permissions > Account**, and then select **Edit** in the **With Access** column. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/u3tIPmuuK7kXKOzD0DaDI_object-permissions-1.png" position="flex-start" size="80" width="1407" height="733" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions 1.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions 1.png" darkWidth="1407" darkHeight="733" showCaption="false" indent="1"} 3. Confirm that the expressions added by the bulk conditional rule no longer appear. 4. Repeat the previous steps for the **Asset Administrator** role. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/c-DCzUfnK1o9qlI1MMRUP_object-permissions-2.png" position="flex-start" size="80" width="1407" height="712" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions 2.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions 2.png" darkWidth="1407" darkHeight="712" showCaption="false" indent="1"} ## Update Bulk Conditional Rules You cannot edit a bulk conditional expression on the **Bulk Update Conditional Rule **page. From this page, you can only add new bulk conditional rules or roll them back. To change an expression that a bulk conditional rule applied, edit it in the single role editor for that specific role and business object. The following scenarios describe how to update a bulk conditional rule: - **Scenario 1:** After you create and save a bulk conditional rule, you update it in the single role editor for the specific role and business object that the rule was applied to. For example, if you created a bulk conditional rule for the **Admin** role and the **Account** business object, go to the single role editor to update it. - **Scenario 2:** You cannot update a bulk conditional rule from the **Bulk Update Conditional Rule** page. From that page, you can only create a bulk conditional rule or roll it back. ### How Bulk Conditional Rules Interact with the single role editor The application appends any expression that you add through bulk conditional rules to the existing or blank conditional rule in the single role editor by using the OR operator. ### Supported Conditional Rules The **Bulk Update Conditional Rule** page currently supports only the following conditional rule types from the UI: - **Expression** - **Group** The page does not support the following conditional rules: - **CurrentUser** - **UserAssociatedList** - **UserAssociatedSubtree** - **UserAssociatedTenants** ### Rollback Behavior and Limitations The following scenarios describe how rollback resolves row conditions: **Scenario 1:** A role (for example, **Admin** or **Self Service**) already has row conditions in the single role editor, and you apply a bulk conditional rule on top of them. The database stores both the single role editor conditions and the bulk conditional rule. When you roll back, the system reverts the roles to their previous values prior to applying the bulk conditional rule. **Scenario 2:** A role already has a row condition in the single role editor, you apply a bulk conditional rule on top of it, and then you add an incremental expression in the single role editor or the bulk conditional form after the bulk conditional rule. When you roll back, the system restores the state that existed immediately before you applied the bulk conditional rule. It removes both the bulk conditional rule and the incremental expression, because the product does not currently support incremental expressions added after a bulk conditional rule. **Scenario 3:** You apply the same bulk conditional rule to a role and business object more than once. Each application adds the rule again as a new row joined by the **OR** operator, so applying it three times produces three identical row conditions. When you roll back, the system removes only the most recent application and leaves the earlier ones in place for example, three identical applications leave two after rollback. Each rollback undoes one bulk conditional application, which is the N-1 behavior. ### Example: Roll Back After a Post-Bulk Increment 1. In the single role editor, the **Admin** role has one row condition on the **Account** business object: **Created By** equals **ATaylor**. 2. You apply a bulk conditional rule (**Address** equals **Test123**, City equals **Mumbai**, Country equals **India**, and Status equals **Active**) to the **Account** business object for the role. The system adds the rule as a new row joined by the **OR** operator. 3. In the single role editor, you add an incremental expression (**Name** equals **AGreen**) to the existing row condition. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/EmZ5mAn-7PByX_iy2AHBF_object-permissions-3.png" position="flex-start" size="80" width="1403" height="675" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions 3.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions 3.png" darkWidth="1403" darkHeight="675" showCaption="false" indent="1"} 4. You roll back the bulk conditional rule for the role. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/-pJrcCStbdDZPBAwXHzwB_object-permissions-4.png" position="flex-start" size="80" width="1405" height="630" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions 4.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions 4.png" darkWidth="1405" darkHeight="630" showCaption="false" indent="1"} :::hint{type="info"} The system restores the **Account** business object for the role to its state at step 1: **Created By** equals **ATaylor**. It removes the bulk conditional rule from step 2 and the incremental expression from step 3, because you added the incremental expression after the bulk conditional rule. ::: ### Example: Roll Back One of Several Identical Rules 1. You apply a bulk conditional rule (**Country** equals **India**, **Address** equals **Test123**, and **Created By** equals **ATaylor**) to the **Account** business object for the **Asset Administrator** role. 2. You apply the same bulk conditional rule to the same role and business object two more times. The **Account** business object now shows the row condition three times, each joined by the **OR** operator. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/mvcRiUBaam0mYp6Cc0CKB_object-permissions-5.png" position="flex-start" size="80" width="1407" height="640" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions 5.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions 5.png" darkWidth="1407" darkHeight="640" showCaption="false" indent="1"} 3. You roll back the bulk conditional rule for the role. ::Image[]{src="https://api.archbee.com/api/optimize/parib0MC3hVoUNdfQdnac/GeJjrQUadb0kDY0d8c9ts_object-permissions-6.png" position="flex-start" size="80" width="1407" height="728" initialPath="../../Resources/Images/Configure/Users and Permissions/Object Permissions 6.png" githubPath="ISM_OLH/Content/Resources/Images/Configure/Users and Permissions/Object Permissions 6.png" darkWidth="1407" darkHeight="728" showCaption="false" indent="1"} :::hint{type="info"} The application removes only the most recent application. The row condition remains twice on the **Account** business object, which reflects the N-1 rollback behavior. :::