---
title: Removing assignments from container vulnerable items and remediation tasks
description: You can clear the Assigned to and Assignment group fields on container vulnerable items directly from the container vulnerable item and remediation task records that you determine might be incorrectly assigned to you or your groups.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/container-vulnerability-response/unassigning-cvits.html
release: australia
product: Container Vulnerability Response
classification: container-vulnerability-response
topic_type: concept
last_updated: "2026-04-03"
reading_time_minutes: 3
breadcrumb: [Use, Container Vulnerability Response, Unified Security Exposure Management, Security Operations]
---

# Removing assignments from container vulnerable items and remediation tasks

You can clear the **Assigned to** and **Assignment group** fields on container vulnerable items directly from the container vulnerable item and remediation task records that you determine might be incorrectly assigned to you or your groups.

## Overview for the workflow

If you determine that container vulnerable items \(CVITs\) and remediation tasks \(CVULs\) aren't within your scope for remediation, or if you think that records have been incorrectly assigned to you or to your groups, you can remove yourself or your groups from the **Assigned to** and **Assignment group** fields on CVIT and CVUL records.

The unassign workflow is supported in workspace and both classic and workspace views for CVITs and CVULs.

You have the option to send requests to clear the assignment fields for approval. See [Approve or reject an unassign request in Vulnerability Response](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-approve-unassign-requests.md) and [Removing assignments from vulnerable items and remediation tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/Unassigning_vis.md) for more information.

-   The **Unassign** UI action is displayed on CVIT and CVUL records in any state other than the Closed or Resolved.

    **Note:** After the request to clear the fields is approved for a CVUL, all the **Assigned to** and **Assignment group** fields on CVITs that have the same assignment group are unassigned. If any CVIT on a CVUL has a different assignment group than its associated CVUL, it is not unassigned. In most cases these CVITs have been manually assigned. See [Removing assignments from vulnerable items and remediation tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/Unassigning_vis.md) for more information.

-   Any records that you update with either the UI action or manually are displayed on the Unassigned module for Container Vulnerability Response.

See [Remove assignments from vulnerable items and remediation tasks](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/vr-unassign-vi.md) for more information about the steps for how to clear the assignment fields.

## System properties and approval notifications

If a remediation owner selects **Unassign** on a record, by default, the sn\_vul.unassign\_vr.approval\_required system property triggers the approval flow and creates a state change approval record in the Review state, and the request is routed for approval. The request is displayed on the My Approvals list for users with the sn\_vul\_container.unassign\_approver.

**Note:** As a vulnerability administrator \[sn\_vul.vulnerability\_admin\], you can set the **sn\_vul.unassign\_vr.approval\_required** system property to **false** to disable the approval process.

Additionally, you can change the value in the **sn\_vul.default\_assignment\_group** system property so if the assignment fields are cleared, a specific group is assigned. For example, if a user clicks **Unassign** on a record and you want to redirect it to a specific group for review, you can add the system ID for the group of your choice in the value field of the system property.

**Note:** If you change this value, notifications for all the VITs, AVITs, and CVITs that are unassigned are sent to the group you specify.

**Parent Topic:**[Remediating container vulnerabilities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/container-vulnerability-response/remediate-cvr.md)