# Creates a New Role

**`POST /api/v1/permissions/roles`**

Creates a new custom role within the authenticated Standard Registry's organization.

**Authentication:** Bearer token required (`Authorization: Bearer <token>`)

**Permission:** `Permissions.PERMISSIONS_ROLE_CREATE`

***

## Request

### Request Body

```json
{
  "name": "MRV Submitter",
  "description": "Can submit MRV data and view approved policies",
  "permissions": ["POLICIES_POLICY_READ", "POLICIES_POLICY_EXECUTE"]
}
```

| Field         | Type      | Required | Description                                      |
| ------------- | --------- | -------- | ------------------------------------------------ |
| `name`        | string    | Yes      | Unique role name within the organization         |
| `description` | string    | No       | Human-readable description of the role           |
| `permissions` | string\[] | Yes      | Array of permission names to assign to this role |

***

## Response

### Success Response

**Status:** `201 Created`

```json
{
  "id": "63e3e5e8a01b3c001234abcd",
  "name": "MRV Submitter",
  "description": "Can submit MRV data and view approved policies",
  "permissions": ["POLICIES_POLICY_READ", "POLICIES_POLICY_EXECUTE"],
  "owner": "did:hedera:testnet:zHcDLGFNymFAJiMBKnpbHDgjvTn6yZnwkPPeFhtJBECH_0.0.4532001",
  "default": false
}
```

| Field         | Type      | Description                                      |
| ------------- | --------- | ------------------------------------------------ |
| `id`          | string    | Newly created role identifier                    |
| `name`        | string    | Role name                                        |
| `description` | string    | Role description                                 |
| `permissions` | string\[] | Assigned permission names                        |
| `owner`       | string    | DID of the Standard Registry that owns this role |
| `default`     | boolean   | Whether this is the default role for new users   |

### Error Responses

| Status                      | Description                                |
| --------------------------- | ------------------------------------------ |
| `401 Unauthorized`          | Missing or invalid token                   |
| `403 Forbidden`             | Insufficient permissions                   |
| `422 Unprocessable Entity`  | Validation error — missing required fields |
| `500 Internal Server Error` | Unexpected server failure                  |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guardian.hedera.com/docs/develop/guardian/standard-registry/roles-and-permissions/apis-related-to-roles-and-permissions/creates-a-new-role.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.