Auwion Admin

Monthly Profit

Client NOT Paid — Action Needed

Support

Projects

⚡ Every client's data is fully isolated at the database level — a client can never see or modify another client's tickets, projects, or invoices. Select a client below to view their dashboard; Super Admin is the only role that can switch between clients.

All Clients

Loading…

Add New Company

Company Name

Once added, this client appears immediately in every Client dropdown across the app (new tickets, client logins, etc). Create their portal login from the Client Portal tab.

Create Super Admin Creates a new, pre-approved login with full read/write access to this dashboard

Full Name

Password

This requires your Supabase service role key (pasted once in the Client Portal tab) since it creates a real login via Supabase's Auth Admin API. The account is created already approved and active — no separate approval step needed.

Super Admins Full read/write access to everything, across every client

Loading…

Client Admin Users Approve new sign-ups and manage Client Admin access to this dashboard

⚡ Client Admin can only view Support and Projects — the database itself blocks any write attempt, so this is enforced even if someone bypasses this page entirely. Super Admin accounts are listed above instead.

Current Rates Applied to all new tickets, projects and set offs

Invoice Rate Per Hour

LKR

Used to calculate Invoice Functional Amount

Developer Per Hour

LKR

Used to calculate Dev Payment & Invoice Dev Amount

✓ Changes apply to new records only — existing data keeps its original calculated values.

Statuses Editable option lists used across Dev, Func and Project tickets — use ▲ ▼ to reorder

⚡ Click any row to edit · Set status to Invoiced to move to Completed Support

Description

Requester

Est Func Hrs

Act Func Hrs

Est Dev Hrs

Act Dev Hrs

Completed Date

Project Status

Dev Pay Status

Client Payment

Developer Payment

Invoice Number

Edit row

⚡ Click any row to edit · Set status to Invoiced to move to Completed Projects

Description

Requester

Est Func Hrs

Act Func Hrs

Est Dev Hrs

Act Dev Hrs

Completed Date

Project Status

Dev Pay Status

Client Payment

Developer Payment

Invoice Number

Edit row

Description

Requester

Act Func Hrs

Act Dev Hrs

Project Status

Dev Pay Status

Client Pay Status

Developer Payment

Invoiced Full Amount

Profit

Invoice Number

Actions

Edit row

Description

Requester

Act Func Hrs

Act Dev Hrs

Project Status

Dev Pay Status

Client Pay Status

Developer Payment

Invoiced Full Amount

Profit

Invoice Number

Actions

Edit row

Profit Analysis

Filter by year:

Monthly Total Profit

Support Profit

Projects Profit

Year

Month

Support Profit
Invoiced Full Amt

Projects Profit
Inv Full − Dev Pay

Set Off Loss
Dev Pay + Inv Func

Total Profit

NCF — Net Cash Flow

Cash basis: revenue counted only when Client Payment = Customer Paid · dev cost counted only when Dev Pay Status = Developer Paid

Filter by year:

Monthly Net Cash Flow

Support Cash Profit

Projects Cash Profit

Year

Month

Support Cash Profit
Only if Client Paid

Projects Cash Profit
Cash In − Cash Out

Set Off Loss
Developer Payment

Total Net Cash Flow

All active set off records

Code

From Project

Remaining Amount

Code

Functional Rate

Developer Rate

From Setoff

Project

Func Hours

Dev Hours

Total

To Setoff

Project

Func Hours

Dev Hours

Total

Project Notes

Special notifications or notes tied to a project or topic

New Note

Project / Topic

Pick an existing project from suggestions, or type any custom topic

Note

Client Portal

⚡ This gives clients a separate, read-only page (portal.html) where they can log in and see only their own requests, status, hours and payment info. It never lets them edit anything. Host portal.html anywhere (a separate URL from this file) and share the login you create below with your client.

Connection Required once, stored only in this browser — never sent anywhere except your own Supabase project

⚠️ Supabase now has two kinds of full-access key: the old legacy service_role key (a long JWT starting with eyJ...) and the new secret key (starts with sb_secret_...). Supabase itself blocks the new sb_secret_ key from ever being used in a browser — you'll get a "Forbidden use of secret API key in browser" error. You must use the legacy one here: Supabase Dashboard → Project Settings → API Keys → look for a "Legacy API Keys" section (you may need to click "reveal") → copy service_role.

Supabase Service Role Key

Needed to create client logins and manage portal access. Keep this file private — never send index.html itself to a client, since it can fully manage your database.

Database Setup Creates/updates every table, view and policy the portal needs — no manual SQL Editor step required

⚡ One-time only: Postgres needs a tiny helper function before this page can run SQL for you. Paste the snippet below into Supabase Studio → SQL Editor → New query → Run, once, ever. After that, every future setup or re-run happens from this button — no more copy-pasting SQL.

Step 1 — one-time bootstrap (run in Supabase SQL Editor)

Not checked yet

Step 2 — run the actual portal setup

Runs the full client-portal-setup.sql script (tables, views, RLS policies) against your database. Safe to run again any time — it never overwrites a mapping you've since customized.

Pending Signups Clients who created their own login from the "New client? Request access" link on the portal

⚡ Signing up creates a login only — it grants zero portal access on its own. A request only becomes real access once you approve it below and confirm the company (what they typed is just a hint, not verified).

Enter your service role key above, then Refresh to load pending requests.

⚡ To add a new client company or switch which client's dashboard you're viewing, use the Super Admin tab. Client logins are still created here, below.

Add Client Login Or create one directly yourself, without waiting for a signup

Client Name

Client / Company

Client Email

Password

Portal Role

This creates a login tied directly to the selected client's client_id — the database enforces that this login can only ever read that one client's tickets, projects, and invoices, no matter what.

Requester Assignment Controls which tickets a client sees — your `req`/Requester field holds individual staff names, not company names

⚡ A client's portal visibility is now enforced by each ticket's own Client field (set when creating/editing a ticket) — this mapping is just a convenience for keeping requester names organized, it no longer controls what a client can see.

Enter your service role key above, then Refresh to load assignments.

Requester Name

Belongs To Client

Existing Client Logins

Enter your service role key above, then Refresh to load client accounts.

Help Desk Status Mapping Controls which Kanban column each internal Project Status appears in on the client portal board

⚡ Clients never see your internal status text (e.g. "Prepare Quote/Scope") — only the Kanban column name you choose here. Unmapped statuses default to Prepare Quote/Scope.

Enter your service role key above, then Refresh to load the mapping.

Internal Status

Kanban Column