This topic is generated by a machine translation engine without any human intervention. ALIBABA CLOUD DOES NOT GUARANTEE THE ACCURACY OF MACHINE TRANSLATED CONTENT. To request a human-translated version of this topic or provide feedback on this translation, please include it in the feedback form.
Add a member to the specified workspace.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| quickbi-public:AddUserToWorkspace | create | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| WorkspaceId | string | Yes | The ID of the workspace. | 95296e95-ca89-4c7d-8af9-dedf0ad0**** |
| UserId | string | Yes | The ID of the Quick BI user to be added. | de4bc5f9429141cc8091cdd1c15b**** |
| RoleId | long | Yes | The preset space role ID. Value range:
| 25 |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "D787E1A3-A93C-424A-B626-C2B05DF8D885",
"Result": true,
"Success": true
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | Workspace.NotIn.Organization | The workspace is not owned by the organization. | The workspace is not owned by the organization. |
| 400 | User.RoleType.Valid | The role ID is invalid. | The role ID is invalid. |
| 400 | Workspace.Not.Exist | The group workspace does not exist. | The group workspace does not exist. |
| 400 | Workspace.Type.Error | The type of group workspace is invalid. | The type of group workspace is invalid. |
| 400 | Viewer.AddInTo.Workspace | Organization members with viewer type are not allowed to add to workspace: %s. | Organization members with viewer type are not allowed to add to workspace: %s. |
| 400 | User.AlreadyIn.Workspace | This user already exists. | This user already exists. |
| 400 | User.AlreadyIn.Role | The user is already assigned this role. | The user is already assigned this role. |
| 400 | AnalystUser.NotSupport.AdminOrDevRole | Analyst users do not support granting workspace administrator or developer roles. | - |
| 400 | UserAnalyst.NotSupport.ThisRole | This role has permissions that analysts cannot grant. | This role has permissions that analysts cannot grant. |
| 400 | Viewer.CannotHave.CustomRole | Organization viewer cannot have custom roles. | Organization viewer cannot have custom roles. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2023-08-07 | The Error code has changed | View Change Details |