BaseOps is the shared foundation underneath our workforce platforms — identity, organizations, permissions and configuration, built once and trusted by every product on top of it. Products focus on the work. The base handles who you are, what you may do, and how everything is set up.
Every product in the family is built on the same base, so a worker, a crew lead and an administrator sign in once and are recognized everywhere — with the same identity, the same permissions model and the same design standard.
The foundation layer. It owns everything products should never rebuild:
The workforce operations system: getting the right people to the right site, and paying them correctly.
The site project system for structured cabling, managing the full lifecycle of data center build-outs.
Hard problems — identity, access control, sign-in policy — are solved a single time in BaseOps, not patched separately into every product.
Every person gets one permanent employee identity that never changes across products, projects or employers on the platform.
SMS code, password, Google, Passkey and email code for sign-in — plus TOTP for administrators. Binding a new credential always verifies the person first.
Default-deny permission points, role inheritance with high-risk exceptions, expiring temporary grants, and no self-escalation — enforced server-side.
Site phones often have Wi-Fi but no cell signal, so each product and organization chooses its preferred sign-in order — password-first or code-first.
Platform-level settings live in the base and apply everywhere; product back offices keep only their own business settings.
Sign-ins, grants, claims and administrative actions are written to an append-only audit trail as they happen.
Products integrate through one small client package and never touch identity data directly. Business data — projects, sites, work orders — always stays in the product, never in the base.
BaseOps is designed so partner organizations can eventually build on the same foundation — shared identity, the same two field systems, and one permission model — without giving up their own business data or their own brand on site. If you run field crews and want that conversation, we should talk.
info@kol.xyz