QueryWorkspaceRoleConfig - Query workspace role configuration - Quick BI

Queries the configuration of a specified workspace role.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

quickbi-public:QueryWorkspaceRoleConfig

get

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
RoleId	integer	Yes	Workspace role ID. Predefined and custom roles: 25: Workspace Administrator (predefined role) 26: Developer (predefined role) 27: Analyst (predefined role) 30: Viewer (predefined role) Custom role: The custom role ID	25

Response elements

Element	Type	Description	Example
	object
RequestId	string	Request ID.	D8749D65-E80A-433C-AF1B-CE9C180FF3B4
Result	object	Query result.
AuthConfigList	array<object>	Role permission configurations.
	object	Permission configuration.
ActionAuthKeys	array	Permission scope.
	string	Permissions: edit: Create use: Use list: Display list	edit
AuthKey	string	Permission type: portal_create: Data Portal dashboard_create: Dashboard report_create: Spreadsheet screen_create: Data Screen analysis: Ad-hoc Analysis offline_download: Self-service Data Retrieval data_form: Data Entry quick_etl: Data Preparation cube: Dataset datasource: Data Source	portal_create
IsSystemRole	boolean	Whether the role is predefined. true: Yes false: No	true
RoleId	integer	Workspace role ID. Predefined and custom roles: 25: Workspace Administrator (predefined role) 26: Developer (predefined role) 27: Analyst (predefined role) 30: Viewer (predefined role) Custom role: The custom role ID	25
RoleName	string	Role name.	空间管理员
Success	boolean	Whether the request succeeded. true: The request was successful. false: The request failed.	true

Examples

Success response

JSON format

{
  "RequestId": "D8749D65-E80A-433C-AF1B-CE9C180FF3B4",
  "Result": {
    "AuthConfigList": [
      {
        "ActionAuthKeys": [
          "edit"
        ],
        "AuthKey": "portal_create"
      }
    ],
    "IsSystemRole": true,
    "RoleId": 25,
    "RoleName": "空间管理员"
  },
  "Success": true
}

Error codes

HTTP status code	Error code	Error message	Description
400	User.Role.NotExist	User role not exist: %s.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.