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 an organization member.
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:AddUser | create | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
AdminUserdeprecated | boolean | No | Whether to assign the organization administrator role. Value range:
Notice This parameter is deprecated and not recommended for use. It is invalid when RoleIds is provided. | true |
AuthAdminUserdeprecated | boolean | No | Whether to assign the organization permission administrator role. Value range:
Notice This parameter is deprecated and not recommended for use. It is invalid when RoleIds is provided. | true |
| UserType | integer | Yes | The user type of the organization member. Value range:
| 1 |
AccountNamedeprecated | string | Yes | Aliyun account name.
| xxxxxx@163.com |
| NickName | string | Yes | Aliyun account nickname.
| ddd |
| RoleIds | string | No | Preset or custom organization role IDs bound to the user, separated by commas, with a maximum of 3. Value range:
| 111111111,456 |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "D787E1A3-A93C-424A-B626-C2B05DF8D885",
"Result": {
"AccountName": "xxxxxx@163.com",
"AdminUser": true,
"AuthAdminUser": true,
"NickName": "ddd",
"RoleIdList": [
111111111
],
"UserId": "b5d8fd9348cc4327****afb604",
"UserType": 1
},
"Success": true
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | Organization.Developers.ReachedTheUpperLimit | The developers of the organization have reached the upper limit:%s | The developers of the organization have reached the upper limit:%s |
| 400 | Organization.Viewers.ReachedTheUpperLimit | The visitors of the organization have reached the upper limit:%s. | The visitors of the organization have reached the upper limit:%s. |
| 400 | Organization.Analysts.ReachedTheUpperLimit | The analysts of the organization have reached the upper limit:%s. | The analysts of the organization have reached the upper limit:%s. |
| 400 | NickName.AlreadyIn.Organization | The alias already exists. | The alias already exists. |
| 400 | User.AlreadyIn.Organization | This user is already a member of the current organization. | This user is already a member of the current organization. |
| 400 | User.AlreadyIn.Organization | The user already exists. | The user already exists. |
| 400 | Instance.Over.MaxLicense | You have reached the maximum number of users that can be added. Please upgrade the configurations or remove some users first. | You have reached the maximum number of users that can be added. Please upgrade the configurations or remove some users first. |
| 400 | AnalystUser.NotSupport.AdminOrDevRole | Analyst users do not support granting workspace administrator or developer roles. | - |
| 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 | User.OrganizationRole.NotExist | User %s must have role in organization. | User %s must have role in organization. |
| 400 | Viewer.CannotHave.CustomRole | Organization viewer cannot have custom roles. | Organization viewer cannot have custom roles. |
| 400 | UserAnalyst.NotSupport.ThisRole | This role has permissions that analysts cannot grant. | This role has permissions that analysts cannot grant. |
| 400 | RoleCount.ExceedsLimit.Error | The user role cannot exceed three. | The user role cannot exceed three. |
| 400 | BindRole.NotExist.Error | Bind role not exist, %s. | Bind role not exist, %s. |
| 400 | DirtyData.Duplicate.User | Dirty data,duplicate user: %s. | - |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2024-02-26 | The Error code has changed. The request parameters of the API has changed. The response structure of the API has changed | View Change Details |
| 2023-08-07 | The Error code has changed | View Change Details |