---
title: "Update a member"
method: PATCH
path: "/accounts/{account_id}/members/{id}"
tags: ["Members"]
---

# Update a member

`PATCH /accounts/{account_id}/members/{id}`

Update user permissions in the account. Developers and translators need `project_ids` and `locale_ids` assigned to access them. Access token scope must include `team.manage`.

## Path parameters

- `account_id` string, required
- `id` string, required

## Headers

- `X-PhraseApp-OTP` string

## Request body

- object
  - `strategy` string — Update strategy, can be any of set, add, remove. If provided, it will set, add or remove given spaces, projects and locale ids from users access list.
  - `role` string — Member role, can be any of of Admin, ProjectManager, Developer, Designer, Translator
  - `project_ids` string — List of project ids the user has access to.
  - `locale_ids` string — List of locale ids the user has access to.
  - `default_locale_codes` string[] — List of default locales for the user.
  - `space_ids` string[] — List of spaces the user is assigned to.
  - `permissions` object — Additional permissions depending on member role. Available permissions are `create_upload` and `review_translations`

## Response `200`

OK

- Member
  - `id` string
  - `email` string
  - `username` string
  - `created_at` string, date-time
  - `last_activity_at` string, date-time
  - `role` string
  - `projects` ProjectLocales[]
    - `id` string
    - `name` string
    - `project_role` string
    - `main_format` string
    - `created_at` string, date-time
    - `updated_at` string, date-time
    - `locales` LocalePreview[]
      - `id` string
      - `name` string
      - `code` string
  - `permissions` object
  - `default_locale_codes` string[]
  - `teams` TeamShort[]
    - `id` string
    - `name` string
    - `created_at` string, date-time
    - `updated_at` string, date-time
  - `spaces` object[]
    - `id` string
    - `name` string
    - `created_at` string, date-time
    - `updated_at` string, date-time
    - `projects_count` integer

## Other responses

- `400` — Bad request. The request could not be parsed or a parameter failed validation. Verify the request body, the content type, and the parameter types, then retry.
- `401` — Unauthorized. Authentication failed because the access token is missing, expired, or invalid. Supply a valid access token and retry.
- `403` — Forbidden. The credentials are valid but not permitted for this request: the access token may lack the required scope, the user may lack permission on the resource, or the account plan may not include the feature. Use a token with the required scope on an account and user that hold the necessary permissions.
- `404` — Not found. The requested resource does not exist or is not visible to the authenticated user. Verify the identifiers in the request path and that the token has access to them, then retry.
- `422` — Unprocessable entity. The request was well-formed but failed validation. The response body lists each offending field in the `errors` array, with its resource, field, and a human-readable message. Correct the listed fields and retry.
- `429` — Too many requests. The rate limit has been exceeded. Wait until the time indicated by the `X-Rate-Limit-Reset` response header before retrying.

---

[API](https://skmtc.net/phrase/apis/control-hub-service.md) · [All operations](https://skmtc.net/phrase/apis/control-hub-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/phrase/control-hub-service/versions/98ecac7ba2bf/schema)