Removing assignments from Application Vulnerability Response vulnerable items and remediation tasks

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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 Application Vulnerability Response vulnerable items and remediation tasks

    This guide outlines the process for removing assignments from Application Vulnerability Response vulnerable items (AVITs) and remediation tasks (AVULs) when they are incorrectly assigned. Customers can clear the Assigned to and Assignment group fields directly from the records, either in the classic or workspace views. Approval requests can be sent for unassigning these records if necessary.

    Show full answer Show less

    Key Features

    • The Unassign button is available on AVIT and AVUL records that are not Closed or Resolved.
    • Upon approval of an unassign request, all associated records with matching assignment groups are also unassigned.
    • Records updated through the UI action or manually appear in the Unassigned module for Application Vulnerability Response.
    • Bulk unassigning is possible by selecting multiple AVITs and using the Bulk Edit feature.
    • System properties control the approval workflow and default assignment groups for unassign requests.

    Key Outcomes

    By following these processes, ServiceNow customers can efficiently manage assignments for remediation tasks and ensure that only relevant records are assigned to their teams. The ability to configure approval flows and default groups allows for greater flexibility and control over assignment management within the Application Vulnerability Response module.

    You can clear the Assigned to and Assignment group fields on Application Vulnerability Response vulnerable items directly from the application 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 Application Vulnerability Response vulnerable items (AVITs) and remediation tasks (AVULs) 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 AVIT and AVUL records.

    The unassign workflow is supported in the classic and workspace views for AVITs and AVULs.

    You have the option to send requests to clear the assignment fields for approval. See Approve or reject an unassign request in Vulnerability Response for more information.

    • The Unassign button is displayed on AVIT and AVUL records in any state other than the Closed or Resolved.
    • After the request to clear the fields is approved, all the Assigned to and Assignment group fields on the AVITs that are associated with an AVUL that have the same assignment group are also unassigned. If any application vulnerable item has a different assignment group than its associated remediation task, it is not unassigned. In most cases these application vulnerable items have been manually assigned. See Removing assignments from vulnerable items and remediation tasks for more information.
    • Any records that you update with either the UI action or manually are displayed on the Unassigned module for Application Vulnerability Response.
    • You can clear the assignment fields for multiple AVITs on a list. After you select the AVITs and select Bulk Edit, on the dialog that is displayed, select the Unassign check box.

    See Remove assignments from vulnerable items and remediation tasks 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_.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.

    See Removing assignments from vulnerable items and remediation tasks for more information about changing the system properties.