> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set a team member Away

> Set a team member Away so stages that only assign to Active members stop giving them new leads. Away only, never Active.

Sets one member Away, for example someone who left without turning off their switch. Stages that only assign to Active members stop giving them new leads until they turn Active again themselves.

## Before you start

* MCP keys need `workflows:write`. Full-access REST keys need nothing else.
* A key that belongs to a person (for example an MCP key) works only for owners and admins. Otherwise it returns 403 `OWNER_OR_ADMIN_REQUIRED`.
* If team availability is not turned on for the account, it returns 403 `TEAM_AVAILABILITY_UNAVAILABLE`.

## Request

| Field | Detail |
| - | - |
| `user_id` (path) | The member's user ID, from `members[].user_id` in [Get team availability](/docs/en/api/team/get-team-availability.md) or from `GET /team`. A value that is not a UUID returns 400 `INVALID_USER_ID`. |
| `availability` | Required. Only `away`. Anything else returns 400 `ADMIN_CAN_ONLY_SET_AWAY`. |

## What happens

* The member is Away, with `changed_by: admin`.
* Leads they already own keep their owner.
* A member who is already Away stays as they were: `changed_at` and `changed_by` keep the earlier values.
* No member of this account with that ID returns 404 `MEMBER_NOT_FOUND`.
* There is no way to set someone else Active. Active is always the member's own choice.

## Related

* With the Nexor MCP, use `set_member_away`.


## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.getnexor.ai/llms.txt).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.