---
sourceDocument: Brazil Security Management
sourceDocumentLink: https://www.servicenow.com/docs/r/security-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil 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: Brazil  
Updated September 10, 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

This functionality allows remediation owners and vulnerability analysts to remove themselves or their groups from theAssigned toandAssignment groupfields on findings and remediation tasks when these assignments are incorrect or outside their scope.
The unassignment process helps reroute records to the appropriate owners for better workflow management.
Show full answer Show less  

## Key Features

* **Unassign Capability:** You can unassign yourself or your group from findings and remediation tasks in any state except *Closed* or *Resolved*, using the Unassign button or the More options menu.
* **Impact on Related Records:** When a remediation task is unassigned, all associated findings with the same assignment group are also unassigned. Findings with different assignment groups remain assigned to their respective groups.
* **Unassigned Module:** Unassigned findings and tasks appear under the Unassigned module, enabling easy review and reassignment.
* **Approval Workflow:** By default, unassigning triggers an approval request if the system property `snvul.unassignvr.approvalrequired` is set to true. Approved unassignments clear assignment fields and optionally reassign records to a default group defined in `snvul.defaultassignmentgroup`. Notifications are sent accordingly. Rejected requests include reasons in the Notes tab.
* **Administrator Controls:** Vulnerability administrators can disable approval workflows, redirect unassigned records to specific groups, and manage notifications through designated user groups.
* **Assignment Type Tracking:** The **Assignment type** field updates to "Unassigned" upon unassignment, providing visibility into how the record was last assigned.
* **Monitoring via Scheduled Jobs:** A daily scheduled job tracks unassignment counts (manual, system, and reassigned to Unassigned) to help evaluate assignment rule effectiveness. These counts are visible in the Assignment Rules list and help identify rules needing adjustment.

## What This Enables for ServiceNow Customers

This feature empowers your security and vulnerability teams to efficiently manage ownership of findings and remediation tasks by unassigning incorrectly routed items. It streamlines the reassignment process, ensures appropriate approval controls, and provides visibility into assignment changes for better operational oversight. The monitoring tools help you optimize assignment rules to reduce manual corrections and improve workflow accuracy.  
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://www.servicenow.com/docs/631EiZ4yg4ieOihEBKWGCA#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.")
* [Approve or reject an unassign request](https://www.servicenow.com/docs/Cmb8d~iqgX4I3LJm_y_KLg "Approve requests for the removal of findings from an assignment group or an individual user in the Security Exposure Management Workspace.")

*[\>]: and then