Overview
Accounts, entitlement and what clients have actually been doing. Usage figures come from the tools' own telemetry, so they begin at the moment it was deployed — not before.
| Tool | Where | Granted | Active | Projects | Minutes | Solves | Last activity |
|---|
| Account | Why | Since |
|---|
Users
Every account in Supabase. Click a row for the full picture and the account actions.
| Account | Status | Tools | Sign-ins | Minutes | Projects | Last seen |
|---|
Access
Tick a cell to grant or revoke one tool for one person. Select rows to act on several at once — one call, one audit entry, rather than a click per pair.
Tools
The catalogue every backend checks. A tool's slug must match MINALAV_TOOL_SLUG on its Railway service exactly — a mismatch refuses every client silently.
| Slug | Name | Category | URL | Users | Projects | Active |
|---|
Deleting a tool is deliberately not offered: the tools row cascades to projects, so removing one would destroy every client project built with it. Deactivate instead — it drops out of users' tool lists and keeps the work.
Activity
Active minutes count distinct minutes in which a tab was open and visible, not wall-clock time between opening and closing. A tool left open over lunch does not read as an hour of work.
| Account | Sessions | Minutes | Sign-ins | Solves | Downloads | Tools | Last seen |
|---|
| Account | Tool | Started | Active min | Open for | Events |
|---|
Audit
Every administrative write, with who did it. Written only by the database itself, so nothing in this console can forge or remove an entry.
| When | Who | Action | Target | Detail |
|---|