# Add or change a team member

> Add a member of the workspace to a team, or change their role in it: member (the default) or maintainer, who manages the team's people and settings.

<div class="g1t-endpoint"><span class="g1t-method" data-method="put">PUT</span><code>/workspaces/{workspace}/teams/{team}/members/{username}</code></div>

Someone who is not a member of the workspace must join it first. Owners of the workspace and the team's maintainers. People only. Returns the person as [`list_team_members`](/reference/api/teams/list-team-members/) lists them.

`role` is `member` (the default) or `maintainer`. `422` when they are not a member of the workspace: add them to it first. Owners of the workspace and the team's maintainers (`403` otherwise).

- **Authentication:** Required. Send an [access token](/reference/api/#authentication) as `Authorization: Bearer`.
- **MCP tool:** [`team`](/reference/mcp/#team) with `action` `set_member`, and the same inputs
- **Scope:** An access token needs [`workspace:admin`](/guides/authentication/#scopes).

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `workspace` | string | Yes | The workspace's slug, e.g. "flagon-io". |
| `team` | string | Yes | The team's slug, as in its mention @workspace/slug, e.g. "backend". |
| `username` | string | Yes | The person's username. |

## Body parameters

Send a JSON object. Names are `snake_case`, as in responses; the `camelCase` spelling is accepted too.

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `role` | string | No | member, or maintainer: also manages the team's people and settings. Defaults to member. One of `member`, `maintainer`. |

## Example request

```sh
curl -X PUT https://api.g1t.sh/workspaces/flagon-io/teams/backend/members/ana \
  -H "Authorization: Bearer $G1T_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "role": "maintainer"
  }'
```

## Example response

A successful request answers `200` with:

```json
{
  "username": "ana",
  "display_username": "Ana",
  "name": "Ana Lima",
  "avatar": null,
  "role": "maintainer",
  "via": null
}
```

## Errors

A failed request answers with one of these statuses and a body like `{"error": {"code": "not_found", "message": "Repository not found."}}`. See [errors](/reference/api/#errors).

| Status | Code | When |
| --- | --- | --- |
| 401 | `unauthenticated` | A token is required, or the one sent is not valid. |
| 403 | `forbidden` | The token is valid but not allowed to do this, such as a member-only change or an agent token outside its repository. |
| 404 | `not_found` | It does not exist, or you cannot see it. |
| 409 | `conflict` | The request conflicts with the current state. |
| 422 | `invalid` | The input is not valid. `message` says which field and why. |