Overview
Test access by application (subscription staff only)
Production URLs on sbsdispatch.com. Per-company delivery-module passwords appear in the Trial Credentials column when viewing Delivery module companies (not shown outside this portal).
Dispatcher (logistics courier)
One tenant per logistics company — orders, dispatch board, zones.
| Role | URL | Credentials |
|---|---|---|
| Admin | /admin/ · /app/ | Signup email + password chosen at registration |
| Dispatcher | /app/ | dispatch+{company-slug}@{domain} · password DispatchDemo2026! |
| Driver | /driver/ | driver+{company-slug}@{domain} · password DriverDemo2026! |
Freight TMS (brokerage)
Independent freight-broker tenants — loads, carriers, shipper/carrier portals.
| Role | URL | Credentials |
|---|---|---|
| Broker staff | /freight/ | Signup email + password chosen at registration |
| Shipper portal | /freight/shipper/ | Enabled per shipper in TMS · default module seed freight.customer@sbsdispatch.com / ModulePortal!2026 |
| Carrier portal | /freight/carrier/ | Enabled per carrier · default module seed freight.carrier@sbsdispatch.com / ModulePortal!2026 |
Delivery modules (standalone modes)
Parts, food, mobility, medical, etc. — hub plus per-mode ops and customer/agent portals.
| Surface | URL | Credentials |
|---|---|---|
| Modes hub | /modes/ | Staff: /modes/login.html |
| Operations | /modes/{module}/ | Staff email from company profile · password ModulePortal!2026 (provisioned on first view) |
| Customer / Agent / Partner | /modes/{module}/customer/ etc. | See Trial Credentials column per company (default seed ModulePortal!2026) |
Subscription portal (this app)
| Role | URL | Credentials |
|---|---|---|
| Subscription user | /subscription/ | Accounts under Manage Users on Overview |
Subscription Records
| Company | Phone | Start | End | Reminder | Paid | Amount | License | Features | Verify | Last import | Trial Credentials | Last In Online |
|---|
DATA IMPORT
Select an operation below.
Golden template sync
Schema promotion (tenant → master)
Best: migration file on the master
sqlcmd example (manual)
Migrations in api/scripts
Server sync
App + schema update (recommended): copies application source to the target, then applies any pending api/scripts/migration-*.sql files that are not yet recorded in schema_migration_history.
Tenant data, passwords, and login_directory on the target are preserved. A files backup is taken on the target first.
FULL OVERWRITE: replaces every ZoneCalc database and all file content on the target with a complete copy of the source server. Use only when you intend to destroy target data and make it an exact clone.
Backup
Nightly backups to C:\backup\ on this server only (each host runs its own profile after sync deploy).
sbsdispatch.com: SCP, AK (tenant data), Code + SB schema (application code and subscription backend — credentials only in SQL).
fusciadesigns.com: SCP, AK, YLC (code + data), Code + SB schema.
Bundle file names include the server id (e.g. SCP-sbsdispatch.com.bak).
Loading…