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

# List permission categories

> GET /multi-users/permission/

Lists every active permission category and the shared permissions available within it, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
GET https://api.scanova.io/multi-users/permission/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/multi-users/permission/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

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

Not paginated. This is the bulk, category-grouped alternative to reading permission IDs off an existing role's `permissions` array — use it to build a full role-editor UI (grouped checkboxes by category) without first fetching a role.

## Related

* [Create a custom role](/api-reference/management-api/shared-users/roles-create) — use permission IDs from here to build `permissions`.
* [List roles](/api-reference/management-api/shared-users/roles-list) — see which permissions an existing role already grants.
* [Roles & permissions](/team/roles-and-permissions) — the human-facing explanation of what each permission grants.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /multi-users/permission/
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/permission/:
    get:
      summary: List permission categories
      description: >-
        Lists every active permission category and the shared permissions
        available within it, for building a role-editor UI. Not paginated.
      operationId: listManagedPermissionCategories
      responses:
        '200':
          description: Permission categories with their permissions.
          content:
            application/json:
              example:
                - name: QR Codes
                  permissions:
                    - id: 23
                      code: QR_CODE_CAN_VIEW
                      name: Can view QR Code
                      description: Allows viewing QR code details.
                      is_boolean: true
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.

````