# Update a Role

Updates a Role from Project scope.

Endpoint: PUT /v1/orgs/{org}/projects/{project}/roles/{role}
Version: 1.0
Security: x-api-key

## Path parameters:

  - `org` (string, required)
    Organization identifier

  - `project` (string, required)
    Project identifier

  - `role` (string, required)
    Role identifier

## Header parameters:

  - `Harness-Account` (string)
    Identifier field of the account the resource is scoped to. This is required for Authorization methods other than the x-api-key header. If you are using the x-api-key header, this can be skipped.

## Request fields (application/json):

  - `identifier` (string, required)
    Role identifier

  - `name` (string, required)
    Role name

  - `permissions` (array)
    List of the permission identifiers.

  - `description` (string)
    Role description

  - `tags` (object)
    Role tags

## Response 200 fields (application/json):

  - `identifier` (string, required)
    Role Identifier

  - `name` (string, required)
    Role Name

  - `permissions` (array)
    Permissions for this Role.

  - `allowed_scope_levels` (array)
    The Scope levels at which this Role can be used.
    Enum: "account", "organization", "project"

  - `description` (string)
    Role description

  - `tags` (object)
    Role tags

  - `scope` (object)
    Scope of the Role

  - `scope.account` (string)
    Account identifier

  - `scope.org` (string)
    Organization identifier

  - `scope.project` (string)
    Project identifier

  - `created` (integer)
    Creation timestamp for Role.

  - `updated` (integer)
    Last modification timestamp for Role.

  - `harness_managed` (boolean)
    This indicates if this Role is managed by Harness or not. If true, Harness can manage and modify this Role.