> For the complete documentation index, see [llms.txt](https://docs.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redivis.com/api/rest-api/members/patch.md).

# patch

## HTTP Request

```http
PATCH /api/v1/organizations/:organizationName/members/:userName
```

## Path parameters

| Parameter        |                                       |
| ---------------- | ------------------------------------- |
| organizationName | The name of the organization          |
| userName         | The username of the particular member |

{% hint style="info" %}
This endpoint extends the [general API structure](/api/rest-api/general-structure.md).
{% endhint %}

## Authorization

You must have edit access to the underlying workflow, and hour access token must have one of the following scopes:

* organization.edit

[Learn more about authorization.](/api/rest-api/authorization.md)

## Request body

Provide a JSON object with information about the parameter.

| Property name | Type          | Description                                                                                                                                                     |
| ------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **status**    | **string**    | Optional. Used to update the member's status. Must be one of `approved` , `rejected`                                                                            |
| **labels**    | **string\[]** | A list of labels to assign to the member. Labels cannot contain spaces, and may have a single colon to delineate a categorical label (e.g., `school:medicine`). |

## Response body

The response body will contain a JSON representation of a [member.get resource](/api/resource-definitions/member.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.redivis.com/api/rest-api/members/patch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.