# Provision a New Organization Member

##

POST /api/0/organizations/{organization\_id\_or\_slug}/scim/v2/Users

Create a new Organization Member via a SCIM Users POST Request.

Note that this API does not support setting secondary emails.

### Path Parameters

* `organization_id_or_slug`*&#x20;<!-- -->(<!-- -->string<!-- -->)*

  REQUIRED

  The ID or slug of the organization the resource belongs to.

### Body Parameters

* `userName`*&#x20;<!-- -->(<!-- -->string<!-- -->)*

  REQUIRED

  The SAML field used for email.

* `sentryOrgRole`*&#x20;<!-- -->(<!-- -->string<!-- -->)*

  The organization role of the member. If unspecified, this will be set to the organization's default role. The options are:

  * `billing` - Can manage payment and compliance details.
  * `member` - Can view and act on events, as well as view most other data within the organization.
  * `manager` - Has full management access to all teams and projects. Can also manage the organization's membership.
  * `admin` - Can edit global integrations, manage projects, and add/remove teams. They automatically assume the Team Admin role for teams they join. Note: This role can no longer be assigned in Business and Enterprise plans. Use `TeamRoles` instead.

### Scopes

You need to [authenticate via bearer auth token.](/api/auth/)

`<auth_token>` requires one of the following scopes:

* `member:admin`
* `member:write`

```
curl https://sentry.io/api/0/organizations/{organization_id_or_slug}/scim/v2/Users \
 -H 'Authorization: Bearer <auth_token>' \
 -H 'Content-Type: application/json' \
 -d '{}'
```

RESPONSESCHEMA

```
Copied
{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:User"
  ],
  "id": "242",
  "userName": "test.user@okta.local",
  "emails": [
    {
      "primary": true,
      "value": "test.user@okta.local",
      "type": "work"
    }
  ],
  "active": true,
  "name": {
    "familyName": "N/A",
    "givenName": "N/A"
  },
  "meta": {
    "resourceType": "User"
  },
  "sentryOrgRole": "member"
}
```
