<span id="查询工作区成员详情"></span>

# Get workspace member details

```{raw} html
<div class="mo-api-page-show-toc" aria-hidden="true"></div>
```

`POST /user/detail_info` reads profile, role/tag, and operation projections for a joined workspace member. This independent detail operation is not replaced by member or current-role lists.

<span id="调用前准备"></span>

## Before you call this API

Set `MOI_ENDPOINT` to the product API prefix `https://api.moi.matrixorigin.cn/v5`. For private deployments, use the corresponding product API URL.

Use a product identity with workspace access and X-Workspace-ID. Obtain member id or iam_user_id from the joined-member list, not invitation IDs or UC subjects. The specification requires workspace_member.read; the composition layer explicitly authorizes workspace_member.get and separately projects allowed_actions.

<span id="请求"></span>

## Request

:::::::{div} mo-api-tabs
::::::{tab-set}
:::::{tab-item} Request example

```bash
curl -X POST "$MOI_ENDPOINT/user/detail_info" \
  -H "X-API-Key: $AI_STUDIO_API_KEY" \
  -H "X-Workspace-ID: $WORKSPACE_ID" \
  -H 'Content-Type: application/json' \
  -d "{\"id\":\"$MEMBER_ID\"}"
```

:::::
:::::{tab-item} Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| X-Workspace-ID | header string | Yes | Target workspace |
| id | body string or number | Yes | Member reference. Prefer strings to preserve identifiers. Supports IAM user references or mappable product principal references |

The handler consumes id only, without strict rejection of unknown fields or a second JSON object. Do not import other APIs' strict JSON guarantees. Empty IDs and unbindable types are rejected. Numeric binding does not mean arbitrary numbers resolve to valid members.

:::::
::::::
:::::::

<span id="成功响应"></span>

## Successful response

:::::::{div} mo-api-tabs mo-api-response-tabs
::::::{tab-set}
:::::{tab-item} Response example

```json
{
  "code": "OK",
  "msg": "OK",
  "data": {
    "allowed_actions": [
      "workspace_member.update"
    ],
    "id": "principal-example",
    "iam_user_id": "456",
    "name": "Example",
    "status": "enabled",
    "created_at": "2026-11-12T00:00:00Z",
    "updated_at": "2026-11-12T00:00:00Z",
    "reserved": false,
    "role_list": [
      {
        "id": 123,
        "name": "Data analyst",
        "status": "enabled"
      }
    ],
    "tag_list": []
  }
}
```

:::::
:::::{tab-item} Fields

| Field | Type | Description |
| --- | --- | --- |
| data.id | string | Product principal identifier from profile mapping, separate from iam_user_id |
| data.iam_user_id | string | IAM user identifier of the current member |
| data.name | string | Display name derived from alias, product display name, email, or IAM reference |
| data.description | string | Description when present. Reserved-member descriptions may be localized |
| data.status | string | Current active/disabled member facts projected to enabled/disabled |
| data.created_at / updated_at | string | UTC RFC3339 timestamps |
| data.reserved | boolean | Reserved/protected-member flag, not permission for arbitrary operations |
| data.role_list | array (array of objects) | Member roles. Each item has integer id and string name/status |
| data.tag_list | array (array of objects) | Member tags. Each item has integer id and string value |
| data.allowed_actions | string[] (array of strings) | Core projection calculated separately for the current workspace/effective role. Still an array when empty |

Empty roles/tags are[]. allowed_actions projects current workspace operations and does not replace target protection, lifecycle/CAS, or write-time checks. Do not grant access from role names/reserved alone. SDK github_login/deletion fields do not prove these details return them. Regular details do not populate deletion; incomplete-deletion information belongs to member-list projections.

:::::
::::::
:::::::

<span id="错误与读取范围"></span>

## Errors and read scope

| HTTP | code | Current branch |
| --- | --- | --- |
| 400 | INVALID_ARGUMENT | Workspace header or id binding failed |
| 404 | USER_NOT_FOUND | Reference unmapped, no membership fact, or lifecycle outside current detail-read scope |
| 403 | IAM_ERROR_CODE_PERMISSION_DENIED | Core authorization denied |
| 503 | IAM_ERROR_CODE_CORE_AUTHORIZE_UNAVAILABLE | Authorization dependency unavailable |
| 500 | INTERNAL | Other profile/storage/projection failure |

Member errors use code/msg/data:null; msg is HTTP status text. Invited or incomplete-deletion member-list entries need not be readable through details. DAO details select active/disabled only. Mapping fallback occurs only after original NotFound; storage errors do not fall back to another identity.
