---
title: "Deactivate a user"
method: POST
path: "/v3/users/{id}/deactivate"
tags: ["Users"]
---

# Deactivate a user

`POST /v3/users/{id}/deactivate`

## Request

- Base URL: `https://harvest.greenhouse.io`
- URL: `https://harvest.greenhouse.io/v3/users/{id}/deactivate`
- Auth: one of:
  - OAuth 2
    - Authorization code: `https://auth.greenhouse.io/authorize`
    - Client credentials
    - Token URL: `https://auth.greenhouse.io/token` scopes: `harvest:users:deactivate`
  - HTTP bearer

Deactivate a Greenhouse user. The user can no longer sign in or be assigned to new jobs, but all of their historical activity (notes, scorecards, emails, applications they own) is preserved. Existing job permissions remain on the user record so they can be restored cleanly via `POST /v3/users/{id}/activate` if the user is later reinstated. Safe to call on a user that is already deactivated — the response is `204 No Content` either way.

## Path parameters

- `id` integer, required

## Request body

- object

## Response `204`

Successful (No Content)

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `422`: Unprocessable Content

---

[API](https://skmtc.dev/greenhouse/apis/harvest-api.md) - [All operations](https://skmtc.dev/greenhouse/apis/harvest-api/llms.txt) - [OpenAPI document](https://skmtc.dev/greenhouse/apis/harvest-api/revisions/822822e3f771?raw)