Security

Security & Access

Tenant isolation enforced by the database, a finite permission catalog per carrier, rates visible only to those who need them, and money records that are reversed rather than edited.

Database-enforced isolation

Every organization, carrier and driver boundary is enforced by Postgres row-level security and checked functions, not by hiding screens.

Role-based permissions

Owners, dispatchers, accounting and safety staff get per-carrier roles from a fixed permission catalog, with individual overrides.

Rate isolation

Seeing a load does not mean seeing what it pays. Rates and rate confirmations stay with people who hold the rates permission.

History and reversals

Changes keep a history with who and when. Financial records are never edited in place; they are reversed with a linked record and a reason.

Security is a database property

GlowTMS runs on Postgres with row-level security. An organization’s data is isolated from every other organization, each carrier’s operational and financial records are isolated from the organization’s other carriers, and drivers see only the loads assigned to them. Navigation in the app is a convenience, not the security boundary.

Access

  • Organization administrators manage people, carriers and role defaults. The last active administrator cannot be removed or demoted.
  • Carrier staff receive per-carrier roles (owner, dispatcher, accounting, safety) with independent overrides.
  • Drivers belong to exactly one carrier and use the driver app with assigned-row access only. They never receive staff permissions. A carrier may choose to share rate confirmations with a driver, and that setting is off by default.
  • Invited accounts and accounts that must change their password can do nothing until the new password is set.

Documents

Document metadata and stored files are authorized separately, under a carrier-scoped layout. Files are downloaded through the signed-in session, and GlowTMS does not hand out long-lived public links.

Records you can trust

  • Browsers cannot delete rows directly. Removals run through checked functions that refuse when a record is in use and offer to deactivate it instead.
  • Money is stored as whole cents, and settlement postings must balance.
  • Secrets such as service keys and AI provider keys stay on the server.

Your data

An organization administrator can download every record and document the organization holds as one archive.

Questions about security? Email support@glowtms.com.

Get your carrier off the spreadsheet

Import the sheet you already run on, then let GlowTMS carry loads through invoicing, factoring and truck settlements. Every step that moves money waits for a person to approve it.