AVKUL ERPDocs
MODULE GUIDE · 11 OCT 2026

Roles & permissions

Control which school users can view, create, edit, export and manage records.

Try guided demo →Download guide ↓
Roles & permissions — illustrated workflow banner

What you can do

01

Role catalogue

02

Permission catalogue

03

Role grants

04

User assignment

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
role:viewrole:createrole:updaterole:deleterole:manage

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

    Open a role and inspect its existing permissions

    An assigned school account with the required permissions.

  2. 02

    Choose only the required permission keys

    Permission catalogue is part of the documented workflow.

  3. 03

    Save the role and assign eligible users

    Role grants is part of the documented workflow.

  4. 04

    Sign in as the affected role to review access

    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
namestringOptional
keystringRequired by declaration
descriptionstringOptional
permissionKeysstring[]Required by declaration
userIdstringRequired by declaration

Rules & current limits

  • A role name alone does not grant platform administration. School scope and explicit guards still apply.

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

Try roles & permissions

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

Launch guided demo →

API & permissions reference

This is the module’s source-declared endpoint catalogue. Reading this reference does not execute any request.

10 source-declared operations
GET/api/v1/access-control/roles

List

role:view
GET/api/v1/access-control/permissions

Permission Catalog

role:view
GET/api/v1/access-control/roles/:id

Get

role:view
POST/api/v1/access-control/roles

Create

role:create

Declared request fields: name (required), key (required), description (optional).

PATCH/api/v1/access-control/roles/:id

Update

role:update

Declared request fields: name (optional), description (optional).

DELETE/api/v1/access-control/roles/:id

Remove

role:delete
PUT/api/v1/access-control/roles/:id/permissions

Set Permissions

role:manage

Declared request fields: permissionKeys (required).

GET/api/v1/access-control/roles/:id/assignable-users

Assignable Users

role:manage
POST/api/v1/access-control/roles/:id/users

Assign User

role:manage

Declared request fields: userId (required).

DELETE/api/v1/access-control/roles/:id/users/:userId

Unassign User

role:manage

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