Dashboard

Your Matrixx VMS landing page — this is where everyone arrives after signing in. Widgets land here as the build progresses (open jobs, submissions in flight, assignments ending soon, the candidate pipeline). For now, pick a section on the left.

Suppliers

Every supplier in the HG tables. Contacts and Assignments count the rows tied to each supplier by its Supplier ID; Users counts active portal users; a STUB was auto-created from an assignment upload and fills in when the profile report lands. Click a supplier to open its full page — profile details you can edit, the clients it's allowed to work, and its contacts. Changes only reach Supabase when you hit Save there.

Candidates

The candidates' main source data. Every candidate is tied to a supplier — the same person can exist under several suppliers, but only one record per supplier, each with its own Candidate ID. Click a candidate to open their full page — editable, written only when you hit Save.

Clients (MSPs)

The client/MSP list from msp.xlsx. Facilities and Assignments count the rows tied to each client by its Client ID. A STUB tag next to the status means the client was auto-created from an assignment upload — it clears when the client list lands or when you open the record and Save it once. Click a client (or Open →) for its full record — profile, its suppliers, facilities, jobs and assignments.

Jobs

Every job in the HG tables — assignments link to these by Job ID. A STUB job was auto-created from an assignment upload and fills in when the jobs export lands. Click a job to open its full page — every detail, editable, written only when you hit Save.

Facilities

Every facility from the client profile report, each linked to its client by Client ID (matched on the Parent Facility Name). Click a facility to open its full page — every field editable, written only when you hit Save.

Assignments

Every assignment in the HG tables, linked to its supplier, facility, client and job by ID. Click an assignment to open its full page — read-only VMS data except the status, with one-click links to the related records.

Submissions

Every submittal across all jobs — the job columns are read through the Job ID tie and the candidate columns through the Candidate ID tie, so they always show what those records hold right now. Click a row to open the submission's record; the Job ID and candidate name open their own pages.

Offers

Offers made to candidates will live here — we'll build this out when we get back into the data-heavy work.

HG Uploads (Suppliers · Contacts · Assignments · Jobs · Clients · Facilities · Candidates)

The HG group — its tables are named hg_… and are tied together by real ID relationships (assignments and contacts both link to their supplier by Supplier ID; assignments link to their job by Job ID). Drop any of the four files on any box — each is recognized by its columns. 1 · Supplier profile report (vms_agency_profile_report…csv): one row per supplier, saved by Nexus Supplier ID — re-uploads refresh in place, a supplier is never dropped. 2 · Supplier contacts (avcontacts.csv): replaced as a full snapshot each upload; every contact links to its supplier by name match. 3 · Assignment export (all fields.csv): saved by Assignment ID, each linked to its supplier and its job — a supplier or job missing its own file is auto-created as a stub until that file is uploaded. Candidate SSN, date of birth and home addresses in that file are never stored. 4 · Jobs export (jobs.csv): one row per Job ID — assignments point at these, and re-uploads refresh in place. 5 · Client/MSP list (msp.xlsx — Excel works as-is): one row per client, saved by Client ID. 6 · Facility report (vms_client_profile_report…csv): one row per Facility ID, each linked to its client by the Parent Facility Name. 7 · Candidates exports (candidates.csv / candidates2.csv): every candidate is tied to its supplier — by Supplier ID when the file has one, else by Supplier Name — one record per candidate per supplier (the exports repeat a person once per submission; those rows are merged, latest first). An existing candidate is matched by its VMS Candidate ID first, then by supplier + name. A candidate whose supplier isn't saved yet is rejected until the supplier profile report lands. Candidate SSN, date of birth and home addresses in that file are never stored.

Upload history