---
title: "Create an organization role"
method: POST
path: "/organization_roles"
tags: ["Organization Roles"]
---

# Create an organization role

`POST /organization_roles`

Creates a new organization role with the given name and permissions for an instance.
The key must be unique for the instance and start with the 'org:' prefix, followed by lowercase alphanumeric characters and underscores only.
You can optionally provide a description for the role and specify whether it should be included in the initial role set.
Organization roles support permissions that can be assigned to control access within the organization.

## Request body

- object
  - `name` string, required — The name of the new organization role
  - `key` string, required — A unique key for the organization role. Must start with 'org:' and contain only lowercase alphanumeric characters and underscores.
  - `description` string, nullable — Optional description for the role
  - `permissions` string[], nullable — Array of permission IDs to assign to the role
  - `include_in_initial_role_set` boolean, nullable — Whether this role should be included in the initial role set

## Response `200`

Success

- Role
  - `object` 'role', required
  - `id` string, required
  - `name` string, required
  - `key` string, required
  - `description` string, nullable, required
  - `is_creator_eligible` boolean, required — Whether this role is eligible to be an organization creator role
  - `permissions` Permission[], required
    - `object` 'permission', required
    - `id` string, required
    - `name` string, required
    - `key` string, required
    - `description` string, required
    - `type` string, required
    - `created_at` integer, required — Unix timestamp of creation.
    - `updated_at` integer, required — Unix timestamp of last update.
  - `created_at` integer, required — Unix timestamp of creation.
  - `updated_at` integer, required — Unix timestamp of last update.

## Other responses

- `400` — Request was not successful
- `401` — Authentication invalid
- `402` — Payment required
- `403` — Authorization invalid
- `404` — Resource not found
- `422` — Invalid request parameters

---

[API](https://skmtc.net/clerk/apis/clerk-backend-api.md) · [All operations](https://skmtc.net/clerk/apis/clerk-backend-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/clerk/clerk-backend-api/revisions/75df3a43fcb2/schema)