Skip to content

Platform module

Role-Based Access Control

People see and do only what their job requires. Eight system roles grant module permissions, scoped to a factory and, for supervisors, to their assigned lines. The API checks a permission on every request.

Eight roles, factory and line scope, checked on every request.

The problem it solves

Why this module exists

In a multi-factory group, a supervisor should not see another factory's data, and a worker should not see colleagues' records. Hiding buttons is not enough.

How it works

Role-Based Access Control, step by step

  1. 01

    Assign roles

    Administrators give each person one or more roles: Super Admin, Factory Admin, Factory Manager, Production Supervisor, Monitoring Operator, HR / Attendance Officer, IT / Device Administrator or Worker.

  2. 02

    Scope

    Accounts are tied to factories, and supervisors to production lines.

  3. 03

    Enforce

    Every API endpoint declares the permission it needs; requests without it are refused.

Key capabilities

What it does

Eight system roles

From platform administration to individual workers.

Factory and line scope

Data is partitioned by factory and line assignment.

Session security

Short-lived access tokens kept in memory and an HttpOnly refresh cookie; deactivating a user ends their sessions immediately.

Audit of access changes

Role and account changes are written to the audit log.

Who benefits

Group management

Separate factories in one system.

IT & administrators

Clear, auditable access rules.

Workers

Access to their own information only.

Next step

See BunonBrain on a running garment plant

We walk you through the product on a simulated factory and answer questions about your own lines.