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

# Create a custom role

> POST /multi-users/access-levels/

Every shared user is assigned a role — Scanova's dashboard calls these "access levels" internally, and the same term appears throughout this endpoint. Use this endpoint to look up available roles before inviting a teammate via [`POST /multi-users/`](/api-reference/management-api/shared-users/invite), or to create a custom role from your own systems.

<Note>
  This endpoint was not previously documented. It requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota — see the [Management API overview](/api-reference/management-api/overview). For what each role actually grants a teammate, see the human-facing [Roles & permissions](/team/roles-and-permissions) guide — this page only documents the wire format.
</Note>

<Warning>
  Creating custom roles requires a dedicated quota on the account's plan (the same gate that hides the dashboard's **Roles** tab on unsupported plans — see [Custom roles are plan-gated](/team/roles-and-permissions#custom-roles-are-plan-gated)). A 403 here means the plan doesn't include it.
</Warning>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://management.scanova.io/multi-users/access-levels/' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{
      "name": "Regional Support",
      "permissions": [23, 24, 31]
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json 201 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 },
      { "id": 24, "code": "ANALYTICS_CAN_VIEW", "name": "Can view Analytics", "description": "Allows viewing analytics.", "is_boolean": true },
      { "id": 31, "code": "LEAD_GENERATION_CAN_VIEW", "name": "Can view Lead Lists", "description": "Allows viewing lead lists.", "is_boolean": true }
    ],
    "is_custom": true
  }
  ```
</ResponseExample>

<ParamField body="name" type="string" required>
  Role name. Must be unique among this account's roles — a duplicate returns a 400 with `{"name": ["Can not create another user role with the same name."]}`.
</ParamField>

<ParamField body="permissions" type="array" required>
  Permission IDs to grant, from the `permissions[].id` values in the list response above.
</ParamField>

<Note>
  There's no bulk "list all available permissions independent of a role" endpoint on the Management API — to discover permission IDs, read them off an existing role's `permissions` array (every account has at least the 6 system roles to inspect).
</Note>

## Related

* [List roles](/api-reference/management-api/shared-users/roles-list) — the other operation on this same endpoint.
* [Invite a shared user](/api-reference/management-api/shared-users/invite) — assign a role ID from this list when inviting or updating a teammate.
* [Update a shared user](/api-reference/management-api/shared-users/update) — assign a role ID from this list when inviting or updating a teammate.
* [Roles & permissions](/team/roles-and-permissions) — the human-facing explanation of what each role grants, including the custom-roles plan gate.
* [Shared users](/team/shared-users) — the dashboard's Users table where these roles are assigned via the UI.


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /multi-users/access-levels/
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/access-levels/:
    post:
      summary: Create a custom role
      operationId: createManagedAccessLevel
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
                permissions:
                  type: array
                  items:
                    type: integer
                  description: >-
                    Permission IDs from an existing role's permissions[].id
                    values.
              required:
                - name
                - permissions
            example:
              name: Regional Support
              permissions:
                - 23
                - 24
                - 31
      responses:
        '201':
          description: Custom role created. Requires the account's custom-roles plan quota.
          content:
            application/json:
              example:
                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
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.

````