---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Removing assignments from findings and remediation tasks

# Removing assignments from findings and remediation tasks {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Removing assignments from findings and remediation tasks

ServiceNow Australia release enables remediation owners and vulnerability analysts to remove themselves or their groups from theAssigned toandAssignment groupfields on findings and remediation tasks.
This capability is useful when records are incorrectly assigned or fall outside their responsibility, helping route them to the proper owners efficiently.
Show full answer Show less  

## Unassigning Findings and Remediation Tasks

* Records can be unassigned in any state except **Closed** or **Resolved** using the **Unassign** UI action or the More options menu.
* When a remediation task is unassigned, all associated findings sharing the same assignment group are also unassigned; findings assigned to different groups remain assigned as they are considered manually assigned.
* Unassigned records appear in the **Unassigned** module for easy tracking and reassignment.

## Approval Workflow and System Properties

* By default, unassigning triggers an approval workflow if the system property **snvul.unassignvr.approvalrequired** is set to **true** . This creates an approval request under **My Approvals**.
* If approved:
  * **Assigned to** and **Assignment group** fields are cleared.
  * **Assignment type** is set to **Unassigned**.
  * The record may be reassigned to a default group specified by **snvul.defaultassignmentgroup**, with notifications sent to that group.
* If rejected, the rejection reason is noted in the record's Notes tab.
* Administrators can:
  * Disable approval by setting **snvul.unassignvr.approvalrequired** to **false**.
  * Redirect unassigned records to a specific default group by setting its sysid in **snvul.defaultassignmentgroup**.
  * Manage notifications via the Unassign notification user group if no default group is configured.
* The **Assignment type** field (Manual, Rule, or Unassigned) indicates how the record was last assigned and is visible on the record and list views.

## Monitoring Unassignments

* A daily scheduled job, **Reassignment count for assignment rules**, tracks unassigned records to evaluate assignment rule effectiveness.
* It counts:
  * Findings reassigned to Unassigned.
  * Manually unassigned records.
  * System-unassigned records.
* These counts appear in the Assignment Rules list as **Manual items count** and **Unassigned items count**.
* To view reassignment counts, navigate to:
  * **Workspaces \> Security Exposure Management Workspace**
  * **Administration** \> **Review** on the Assignment rules tile
  * Select **Assignment** in the navigation pane and add reassignment columns via the gear icon.
* Each unassigned record retains a reference to its original assignment rule, helping identify rules that may need adjustment.  
You can remove yourself or your group from the Assigned to and Assignment group fields on findings and remediation tasks if you believe they were incorrectly assigned.

## Overview of the workflow {#sem-unassigning-findings__section_pgq_krx_f5b}

Remediation owners and vulnerability analysts can unassign records using the Unassign UI action. This helps route records that are outside their scope to the appropriate owners.

## Use case {#sem-unassigning-findings__id_k4b_cr3_nwb}

Use the Unassign option when a finding or remediation task is not relevant to your scope or was mistakenly assigned to you or your group.

## Unassigning from findings and remediation tasks {#sem-unassigning-findings__section_c5f_lsx_f5b}

You can unassign records in any state except Closed or Resolved, using the Unassign button or the More options menu.  
Supported Records:

* Remediation tasks: When a remediation task is unassigned, all associated findings with the same assignment group are also unassigned.  
  Note:  
  Items with a different assignment group than their remediation task aren't unassigned, as they are likely manually assigned.
* Findings: Records unassigned manually or via UI appear under the Unassigned module.
{#sem-unassigning-findings__ul_mqv_gkc_wfc}

Any records that you update assignments for with the UI action or manually are displayed on the Unassigned module.

## Approval workflow and system properties {#sem-unassigning-findings__section_mjy_qsx_f5b}

By default, unassigning a record triggers an approval workflow if the system property sn_vul.unassign_vr.approval_required is set to true. This generates an approval request that appears
under My Approvals. If approved:

* The Assigned to and Assignment group fields are cleared.
* The Assignment type is set to Unassigned.
* The record can be optionally reassigned to a group defined in sn_vul.default_assignment_group.
* Notifications are sent to the new group.
* If rejected, the reason appears in the Notes tab.

{#sem-unassigning-findings__ul_f4f_cfd_wfc}

As a vulnerability administrator, you can:

* Disable approvals by setting sn_vul.unassign_vr.approval_required to false.
* Redirect unassigned records to a specific group by setting its sys_id in sn_vul.default_assignment_group.
* Manage notifications using the Unassign notification user group if no default group is set.

{#sem-unassigning-findings__ul_h4f_cfd_wfc}

The Assignment type (Manual, Rule, or Unassigned) helps identify how a record was last assigned. When unassigned, this field is set to Unassigned and is visible on both the record and list views.

## Monitoring unassignments with scheduled jobs {#sem-unassigning-findings__section_kjk_kcy_f5b}

A daily Reassignment count for assignment rules scheduled job tracks unassigned records to assess assignment rule
effectiveness. This job counts:

* Findings reassigned to Unassigned.
* Manually unassigned records.
* System-unassigned records

{#sem-unassigning-findings__ul_efn_m3d_wfc}

These counts appear in the Assignment Rules list under the following columns:

* Manual items count
* Unassigned items count

{#sem-unassigning-findings__ul_gfn_m3d_wfc}To view reassignment counts:

1. Navigate to WorkspacesSecurity Exposure Management Workspace.
2. Select Administration in the navigation pane.
3. Select Review on the Assignment rules tile.
4. On the Rules page, select Assignment in the navigation pane.
5. Use the gear icon to add both reassignment columns to the list view.

{#sem-unassigning-findings__ol_hfn_m3d_wfc}

Each reassigned record retains a reference to its original assignment rule. The list view displays reassignment counts for each assignment rule, helping you identify rules that may need
adjustment.
**Related tasks**   

* [Remove assignments from findings and remediation tasks](https://servicenow-prod.fluidtopics.net/senHk2kEqWoiDPxUGGD1cA#sem-unassign-findings-remediation-tasks "Clear the Assigned to and Assignment group fields on vulnerable item records in the Vulnerability Response, Application Vulnerability Response, and Container Vulnerability Response applications.")

*[\>]: and then