---
title: "Reassign Assessment"
method: PUT
path: "/api/assessment/v2/assessments/{assessmentId}/reassign"
tags: ["Assessment Actions"]
---

# Reassign Assessment

`PUT /api/assessment/v2/assessments/{assessmentId}/reassign`

## Request

- Base URL: `https://hostname`
- URL: `https://hostname/api/assessment/v2/assessments/{assessmentId}/reassign`
- Auth: OAuth 2
  - Client credentials
  - Token URL: `https://{hostname}/api/access/v1/oauth/token` scopes: `ASSESSMENT`

Use this API to reassign the organization, approvers, and/or respondents of an assessment. The assessment will be updated with the new organization, approvers, and/or respondents provided in the request body.

 > 🗒 Things to Know  
 > 
 > - If the assessment is in **Completed** stage, reassignments made using this API will be ignored.
 > 
 > - The reassigned respondents and/or approvers should exist in the `orgGroupId` provided in the request.
 > 
 > - New respondents that do not already exist in the application will be created as Invited Users unless `PROJECT_RESPONDENT` is specified in the `respondentCreationType` parameter.
 > 
 > - If an update is made using this API, an event will be shown in the Assessment Activity.
 > 
 > - This API can update assessments of the following types: PIA, Vendor, ITRM, Control, Exchange, and Incident.
 > 
 > - The `stageId` parameter values returned in the [Get Assessment Workflow Stages](/onetrust/reference/getworkflowdetailsforassessmentusingget) API response can be used to reassign approvers to different stages of an assessment.

## Path parameters

- `assessmentId` string, uuid, required

## Request body

- PrivacyAutomationAssessmentAutomationReassignAssessmentRequest
  - `orgGroupId` string, uuid: The ID of the organization that the assessment should be reassigned to
  - `approvers` PrivacyAutomationAssessmentAutomationAssessmentApproverRequest[]: The user(s) that will override the current approvers if any are added
    - `approverId` string, uuid, required: Unique identifier for the approver
    - `approverName` string: Display name of the approver
    - `comment` string: Optional comment for the approver assignment
    - `workflowStageIds` string[]
  - `respondents` PrivacyAutomationAssessmentAutomationAssessmentRespondentRequest[]: The user(s) that will override the current respondents if any are added
    - `respondentId` string, uuid: Unique identifier for the respondent user
    - `respondentName` string, required: Display name of the respondent
    - `comment` string: Optional comment for the respondent assignment
    - `sectionIds` string[]
    - `isRespondentOfApproverSection` boolean: Flag indicating whether this respondent is assigned to approver sections
  - `respondentCreationType` 'INVITED' | 'PROJECT_RESPONDENT': If adding new users that don't already exist, this is the type of user they will be created as

## Response `204`

No Content

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests. For more information, see [API Rate Limits](https://developer.onetrust.com/onetrust/reference/rate-limits-overview).
- `500`: Internal Server Error

---

[API](https://skmtc.dev/onetrust/apis/privacy-automation-assessment-automation.md) - [All operations](https://skmtc.dev/onetrust/apis/privacy-automation-assessment-automation/llms.txt) - [OpenAPI document](https://skmtc.dev/onetrust/apis/privacy-automation-assessment-automation/revisions/fbdf0c71bfe5?raw)