---
title: "POST /v1/matters/{matterId}:addPermissions"
method: POST
path: "/v1/matters/{matterId}:addPermissions"
tags: ["matters"]
---

# POST /v1/matters/{matterId}:addPermissions

`POST /v1/matters/{matterId}:addPermissions`

Adds an account as a matter collaborator.

## Path parameters

- `matterId` string, required

## Request body

- AddMatterPermissionsRequest — Add an account with the permission specified. The role cannot be owner. If an account already has a role in the matter, the existing role is overwritten.
  - `ccMe` boolean — Only relevant if **sendEmails** is **true**. To CC the requestor in the email message, set to **true**. To not CC requestor, set to **false**.
  - `sendEmails` boolean — To send a notification email to the added account, set to **true**. To not send a notification email, set to **false**.
  - `matterPermission` MatterPermission — Users can be matter owners or collaborators. Each matter has only one owner. All others users who can access the matter are collaborators. When an account is purged, its corresponding MatterPermission resources cease to exist.
    - `role` 'ROLE_UNSPECIFIED' | 'COLLABORATOR' | 'OWNER' — The user's role for the matter.
    - `accountId` string — The account ID, as provided by the [Admin SDK](https://developers.google.com/admin-sdk/).

## Response `200`

Successful response

---

[API](https://skmtc.dev/google/apis/vault.md) · [All operations](https://skmtc.dev/google/apis/vault/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/google/vault/revisions/db6937065136/schema)
