Granting Permissions to a User Group for a Region-specific Project

Function

This API is provided for the administrator to grant permissions to a user group for a region-specific project. For details about the authorization scope, see System Permissions.

The API can be called using both the global endpoint and region-specific endpoints. For IAM endpoints, see Regions and Endpoints.

Debugging

You can debug this API in API Explorer.

URI

PUT /v3/projects/{project_id}/groups/{group_id}/roles/{role_id}

**Table 1** URI parameters
Parameter	Mandatory	Type	Description
group_id	Yes	String	User group ID. For details about how to obtain a user group ID, see Obtaining Account, IAM User, Group, Project, Region, and Agency Information.
project_id	Yes	String	ID of the project for which the user group will be assigned permissions. For details about how to obtain the project ID, see Obtaining Account, IAM User, Group, Project, Region, and Agency Information. Ensure that the project is the IAM project that IAM users in the group will be authorized to access and use. NOTE: To assign a custom policy that contains OBS operations to a user group, use the API described in Querying Project Information to obtain the ID of the MOS project, and attach the custom policy to the user group in this project.
role_id	Yes	String	Permission ID. For details about how to obtain a permission ID, see Listing Permissions.

Request Parameters

**Table 2** Parameters in the request header
Parameter	Mandatory	Type	Description
Content-Type	Yes	String	Fill application/json;charset=utf8 in this field.
X-Auth-Token	Yes	String	Access token issued to a user to bear its identity and permissions. For details about the permissions required by the token, see Actions.

Response Parameters

None

Example Request

Request for granting permissions to a user group for a region-specific project

PUT https://iam.myhuaweicloud.com/v3/projects/{project_id}/groups/{group_id}/roles/{role_id}

Example Response

None

Status Codes

Status Code	Description
204	The authorization is successful.
400	Invalid parameters.
401	Authentication failed.
403	Access denied.
404	The requested resource cannot be found.
409	A resource conflict occurs.