> ## 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.

# تحديث دور مخصص

> PATCH /multi-users/access-levels/{pk}/

يحدّث دورًا مخصصًا مملوكًا لهذا الحساب، على مضيف **Management API** (‏`api.scanova.io`)، مع المصادقة باستخدام مفتاح Management API الخام الخاص بك.

```
PUT   https://api.scanova.io/multi-users/access-levels/{pk}/
PATCH https://api.scanova.io/multi-users/access-levels/{pk}/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  معرّف `id` الخاص بالدور.
</ParamField>

يدعم كلًا من `PUT` (استبدال كامل) و`PATCH` (تحديث جزئي)، ويقبل كلاهما نفس حقلي `name`/`permissions` الموثّقين في [إنشاء دور مخصص](/ar/api-reference/management-api/shared-users/roles-create).

<RequestExample>
  ```bash cURL theme={null}
  curl -X PATCH "https://api.scanova.io/multi-users/access-levels/42/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a" \
    -H "Content-Type: application/json" \
    -d '{ "permissions": [23, 24, 31, 40] }'
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": 42,
    "name": "Regional Support",
    "slug": null,
    "permissions": [
      { "id": 23, "code": "QR_CODE_CAN_VIEW", "name": "Can view QR Code", "description": "Allows viewing QR code details.", "is_boolean": true }
    ],
    "is_custom": true
  }
  ```
</ResponseExample>

## لا يمكن تعديل الأدوار النظامية هنا

يمكن الكتابة عبر نقطة النهاية هذه فقط للأدوار المخصصة الخاصة بالحساب (‏`is_custom: true`‏) — أي `pk` يخص دورًا نظاميًا (أو دورًا مخصصًا خاصًا بحساب آخر) يُعيد `404`، تمامًا كما لو لم يكن الدور موجودًا على الإطلاق.

## ذات صلة

* [الحصول على دور](/ar/api-reference/management-api/shared-users/roles-retrieve) — الاطلاع على الدور قبل تحديثه.
* [إنشاء دور مخصص](/ar/api-reference/management-api/shared-users/roles-create) — مرجع الحقول التي يعيد هذا التحديث استخدامها.
* [حذف دور مخصص](/ar/api-reference/management-api/shared-users/roles-delete) — حذف هذا الدور نهائيًا.
* [نظرة عامة على Management API](/ar/api-reference/management-api/overview) — مخطط المصادقة وقواعد الحصة المطبّقة على نقطة النهاية هذه.


## OpenAPI

````yaml api-reference/openapi/management-api.json PATCH /multi-users/access-levels/{pk}/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.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://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /multi-users/access-levels/{pk}/:
    patch:
      summary: Update a custom role
      description: >-
        Only the account's own custom roles can be updated — system roles
        (`is_custom: false`) 404 here even though they 200 on GET. Both PUT and
        PATCH are supported; PATCH shown here for a partial update.
      operationId: updateManagedAccessLevel
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
                permissions:
                  type: array
                  items:
                    type: integer
            example:
              permissions:
                - 23
                - 24
                - 31
                - 40
      responses:
        '200':
          description: Role updated.
        '404':
          description: No custom role with this id owned by this account.
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. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````