Provision a company
Creates a tenant and its first SysAdmin via POST /api/v1/admin/companies. The admin email and password you enter become your login.
Now sign in → with that admin email and password.
Dashboards
Loading…Executive GET /dashboard/executive
My dashboard GET /dashboard/me
First-pass yield GET /quality/reports/first-pass-yield
OEE by production order GET /oee/production-orders/{id}
Note: the task mentioned /api/v1/reports, which does not exist; the real report endpoints above are used instead.
Approvals
Your pending queueRequests awaiting your action — you hold the current level's approver role and didn't raise it. GET /api/v1/approvals
Act on a request
The engine re-checks eligibility and raiser≠approver — a forged id is refused (422).
Users
Members of your companyCreate user POST /api/v1/users
Password ≥ 8 chars. Role IDs optional (comma-separated) — create a role in Admin to get its id, or assign roles below after.
Members
User actions
Paste a user id from the table above.
Admin
Roles & permissionsThere is no create-user or list endpoint. Users are created only by provisioning (as SysAdmins). This screen manages what the API does expose: create a role, set its permissions, and assign/remove a role on a user by id. Your login is a SysAdmin, which by design (segregation of duties) can't hold business roles or view business reports — so assigning a business role to your own id will likely be refused (422).
1 · Create a role POST /api/v1/roles
2 · Set role permissions PUT /api/v1/roles/{id}/permissions
A custom role may hold any permission except users.manage / roles.manage (reserved for System Administrator) and portal.access.
3 · Assign a role to a user POST /api/v1/users/{id}/roles
Remove a role · Deactivate a user
API documentation
Open full page ↗Every endpoint grouped by module, with parameters, request/response schemas and a how-to-use guide — generated from /swagger/v1/swagger.json.