---
title: "Reactivate user"
method: POST
path: "/v1/users/{id}/reactivate"
tags: ["users"]
---

# Reactivate user

`POST /v1/users/{id}/reactivate`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/users/{id}/reactivate`
- Auth: HTTP bearer

Restores a deactivated person's account to active status. A person who never accepted their invite goes back to invited status. Their previous role assignments are restored along with the access they grant. Any approver-list entries removed at deactivation are not automatically restored. Only an account owner can do this to an owner, and you cannot do it to a person who holds a permission you do not hold. An API key is never an owner.

## Path parameters

- `id` string, required

## Response `200`

Success.

- object
  - `data` object, required
    - `id` string, required
    - `status` 'active' | 'invited', required: `invited` when the person never accepted their invite (never signed in, set a password or confirmed their email).

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: The person belongs to a location where you do not hold `user.edit`; `owner_required`: the person is an owner and you are not an owner there (an API key is never an owner); or `outranked`: the person holds a permission you do not hold where they hold it.
- `404`: No such person in this workspace.
- `409`: `not_deactivated`: the person is not deactivated.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/7c2741bcdb16?raw)