Active session progress
No active session.
Status breakdown
Found items broken down by condition, and Not Found items broken down by confirmation state.
Visual overview
Overall status distribution and per-department comparison for the active session.
Breakdown by department
| Dept | Total | Found | Not Found | Not Checked |
|---|---|---|---|---|
| No active session. | ||||
Session history
All sessions ever created. Open the History tab for full detail per year.
Master Database
0 assets stored. This is the master data used to build every yearly checking session.
| ID Number | Description | Dept | Section | Group | Location | Qty | User | Actions | |
|---|---|---|---|---|---|---|---|---|---|
| No data yet. Connect the database, then add or import assets. | |||||||||
Create a new checking session
A new session is automatically built from the entire Master Database — no need to re-import every year.
Sessions
Historical data import
Import a previous-year workbook as a closed snapshot session. It never replaces the current master asset list.
Checking data
Default Submit records Found with Good. Choose Not Found to request confirmation, or choose Broken when required.
| Action | ID Number | Description | Dept | Section | Group | Location | Qty | User | Status | Condition | Remark | Checked By | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Select or create a session first. | |||||||||||||
Select a session to view
Result detail
| ID Number | Description | Dept | Location | Status | Condition | Remark | Checked By | Time |
|---|---|---|---|---|---|---|---|---|
| Select a session above. | ||||||||
Database Connection (Supabase)
This tool needs a shared cloud database so 5 people can access & update the same data (not stored in each person's browser). It uses Supabase (Postgres) via direct REST API — no extra SDK, for a more reliable connection.
- Go to supabase.com → Sign up (free) → New Project.
- Open the SQL Editor → paste the SQL script below → click Run (this creates the 4 required tables).
- In the sidebar, click the gear icon Project Settings → API Keys.
- At the top of that page there's a Project URL (format
https://xxxxx.supabase.co) — copy it. - Below it there's a Publishable key (starts with
sb_publishable_) — copy that too. This replaces the old "anon key". - Paste both into the two boxes below, then click "Save & Test Connection".
Found at the top of Project Settings → API Keys, or via the Connect button on the project dashboard.
New projects: use the Publishable key (starts with sb_publishable_) from the API Keys tab. Older projects: use anon public from the "Legacy API Keys" tab.
Database setup
The SQL scripts (setup & migration) are intentionally not bundled in this file, so the database structure and default credentials are not exposed to whoever receives it. Use the setup-lengkap.sql / migration.sql files kept separately by the administrator.
Active device sessions
First login remains active. A new device is rejected until an administrator revokes the active session.
| Username | Full Name | Role | Session | Action |
|---|---|---|---|---|
| Loading... | ||||
User Management
Create local accounts, assign roles, reset passwords, deactivate accounts. Password values are never displayed.
| Username | Full Name | Role | Status | Last Signed In | Actions |
|---|---|---|---|---|---|
| Loading user data... | |||||