AVKUL ERPDocs
SCREEN GUIDE · 11 OCT 2026

Multilingual explanations

Use the multilingual explanations workspace to review its saved runs, context and available actions.

Try guided demo →Download guide ↓
Multilingual explanations — illustrated workflow banner

What you can do

01

Input and context selection

02

Saved result review

03

Available history and comparisons

04

Human review

Access & setup

Intended access: Assigned account with the required permissions.

  • A school account with the permissions shown below.
  • Choose the relevant school, academic session or child before working.
Required permission keys
lms:view

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Review the input context and provider/data state

    A school account with the permissions shown below.

  2. 02

    Run or open the relevant saved result

    Saved result review is part of the documented workflow.

  3. 03

    Inspect the available evidence and comparison

    Available history and comparisons is part of the documented workflow.

  4. 04

    Review the outcome before acting on it

    Review the result in the connected record or workspace before moving on.

Request fields to understand

Source-declared fields used by related operations; each operation has its own validation and scope.

FieldDeclared typeInput
conceptstringOptional
levelstringOptional
languagesstring[]Optional
subjectIdstring | nullOptional
classIdstring | nullOptional
audience'STUDENT' | 'PARENT' | 'BOTH'Optional
publishbooleanOptional
titlestringOptional
bodystringOptional
parentTipstringOptional
status'DRAFT' | 'PUBLISHED' | 'PRIVATE' | 'ARCHIVED'Required by declaration

Rules & current limits

  • The current provider can return sample output. Configured credentials do not prove a verified provider, live GPS feed or reliable prediction.

Source inventory checked on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Try multilingual explanations

Open a guided sample workspace, try the available actions, then reset whenever you like. No login required.

Launch guided demo →

API & permissions reference

These are the source-matched API operations connected to this guide. Reading this reference does not execute any request.

6 source-declared operations
GET/api/v1/ai-features/multilingual-explain

List Multilingual Explain

lms:view
POST/api/v1/ai-features/multilingual-explain

Generate Multilingual Explain

lms:view

Declared request fields: concept (required), level (optional), languages (optional), subjectId (optional), classId (optional), audience (optional), publish (optional).

PATCH/api/v1/ai-features/multilingual-explain/langs/:langId

Update Multilingual Explain Lang

lms:view

Declared request fields: title (optional), body (optional), parentTip (optional).

GET/api/v1/ai-features/multilingual-explain/:id

Get Multilingual Explain

lms:view
PATCH/api/v1/ai-features/multilingual-explain/:id

Update Multilingual Explain Meta

lms:view

Declared request fields: concept (optional), level (optional), subjectId (optional), classId (optional), audience (optional).

PATCH/api/v1/ai-features/multilingual-explain/:id/status

Set Multilingual Explain Status

lms:view

Declared request fields: status (required).

Open the actual application

ERP links use your assigned account. Record-specific pages start from the list so you can choose a real record.

Keep exploring