> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 移除共享用户

> DELETE /multi-users/{pk}/

共享用户是您邀请加入 Scanova 账户的团队成员——与仪表盘 **Users** 表格中展示的列表相同。此端点让您可以以编程方式列出、邀请、更新或移除他们。

<Note>
  此端点此前未被记录过文档。它需要一个拥有 `MANAGEMENT_API`（或 `MANAGEMENT_API_SANDBOX`）配额的 Management API 密钥，以原始 `Authorization` 请求头的值发送——参见 [Management API 概览](/zh/api-reference/management-api/overview)——外加账户自身用于共享用户的 Team 配额。关于每个角色实际授予的权限，请参见[角色与权限](/zh/team/roles-and-permissions)；关于角色本身的数据格式，请参见[角色（访问级别）](/zh/api-reference/management-api/shared-users/roles-list)。
</Note>

<ParamField path="pk" type="integer" required>
  上方列表响应中的共享用户记录 ID。
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request DELETE \
    --url 'https://management.scanova.io/multi-users/118/' \
    --header 'Authorization: YOUR_API_KEY'
  ```
</RequestExample>

`DELETE` 返回 `204 No Content`。

## 相关内容

* [列出共享用户](/zh/api-reference/management-api/shared-users/list) — 查找要在此处操作的 `pk`。
* [获取共享用户](/zh/api-reference/management-api/shared-users/retrieve) — 同一 `{pk}` 端点的另一个操作。
* [更新共享用户](/zh/api-reference/management-api/shared-users/update) — 同一 `{pk}` 端点的另一个操作。
* [列出角色](/zh/api-reference/management-api/shared-users/roles-list) —— 查找或创建本端点的邀请/更新调用所需的 `access_level` ID。
* [创建自定义角色](/zh/api-reference/management-api/shared-users/roles-create) —— 查找或创建本端点的邀请/更新调用所需的 `access_level` ID。
* [共享用户](/zh/team/shared-users) —— 仪表盘自身的 Users 表格，展示相同的邀请/停用/移除操作。
* [角色与权限](/zh/team/roles-and-permissions) —— 每个角色实际授予团队成员的权限。


## OpenAPI

````yaml api-reference/openapi/management-api.json DELETE /multi-users/{pk}/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    management.scanova.io (QR codes, folders, tags, leads, forms, analytics,
    plans, shared users & roles), plus the token-creation and usage-stats
    endpoints used to authenticate against it. Every path and request/response
    shape below was verified live against a real API key and the actual running
    backend (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://management.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /multi-users/{pk}/:
    delete:
      summary: Remove a shared user
      operationId: deleteManagedSharedUser
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '204':
          description: Shared user removed.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. management.scanova.io) — the same key sent to
        the regular API host will not authenticate.

````