Skip to content

TransitPin - Glossary

Terms a reader without TransitPin context needs. Verified against the live system 2026-08-15.

  • tenant - A customer of the platform: a transportation provider (for example Village Express) that runs branded signup, billing, and operations on TransitPin. One row in the tenants table. All provider-facing data is scoped by tenant_id.

  • slug - The short, URL-safe identifier for a tenant (for example villageexpress). It is the tenant's primary key and is used in subdomains (villageexpress.transitpin.com), path URLs (app.transitpin.com/villageexpress/...), and the tenants.id column.

  • white-label - The ability for a tenant to present the product under its own brand (name, colors, fonts) rather than TransitPin's. Implemented by storing a theme JSON on the tenant and applying it client-side via CSS variables.

  • theme resolver - The mechanism that returns a tenant's theme. Server side it is GET /api/theme/{slug}; client side it is loadTenantTheme(), which fetches that endpoint and applies the returned tokens as CSS variables.

  • CSS variables - The design tokens a theme sets on the :root element (--primary, --accent, --bg, --font, and so on). A theme JSON value like {"primary":"#2ac0a6"} becomes --primary: #2ac0a6.

  • reserved slug - A subdomain label that is a brand surface or infrastructure and is never a tenant slug: www, my, app, ops, webmail. Tenant resolution skips these.

  • household - The billing unit: one contact (typically a parent) plus the children they register. A household has one primary payer, optionally a second parent/guardian, and a weekly total equal to the sum of its children's rates.

  • payer - An adult who receives an invoice. The primary payer is usually the registering parent; additional payers (for example a co-parent outside the household) can be added and assigned a share of the bill.

  • registration - Two related meanings: (1) the act of a parent signing up their children, which writes household + payer + children + a $50 registration-fee invoice; (2) the legacy registrations table, a simpler inbound interest/approval list separate from the household flow.

  • manifest - The driver-facing list of riders and stops for a route or run. (Referenced in the frontend assets and driver tooling; the core stop data lives in route_stops with a riders JSON array.)

  • route_stops - The normalized table holding a route's ordered stops (one row per stop, seq 1..N), with name, address, coordinates, time, and a riders JSON array. The route row keeps a denormalized stops count in sync.

  • ops console - The internal super-admin surface at ops.transitpin.com/ops/, used by IT Pro Partner staff (auth2 users in the transitpin-it-staff group). It is separate from the operator (fleet) and parent surfaces.

  • first pickup date - The date a household's child first rides. Stored as households.first_pickup_date; it drives the timing of the first weekly transportation invoice (generated 5 days before, or once past).

  • one-way / two-way - The two weekly trip types. One-way ($120/wk) means the child rides morning OR afternoon only; two-way ($175/wk) means both. Derived from the form's transport-need value (both -> two-way, morning or afternoon only -> one-way) and stored as children.trip_type.

  • transport-need - The registration form field capturing morning, afternoon, or both. The single source of truth for a child's trip type.

  • registration fee - The one-time $50.00 charge taken at signup, before the first pickup. Written as a kind='registration' invoice and emailed to the parent.

  • weekly cycle - The Monday-Sunday billing window used for weekly transportation invoices (current_weekly_cycle).

  • manifest / driver - The driver-facing surface (driver.html, driver-manifest.json) that surfaces a route's stops and riders for the day's run.

  • auth2 / Hexclave - The identity provider TransitPin delegates authentication to. The ops console logs in against https://auth2-api.itpropartner.com; the backend validates JWTs against http://127.0.0.1:8102/api/latest.

  • impersonation - A platform admin acting as a customer tenant. Uses a DB-backed 15-minute token and writes every action to audit_log.

  • audit_log - The append-only trail of ops actions (assume/exit identity, impersonated actions), with both the real actor and the impersonated subject.

  • platform_admin - The role (or its legacy alias admin) required for tenant-listing and ops assume-identity/audit endpoints.