About this prototype

What is real today

Tenant isolation, enforced in the database

Deny-by-default row-level security, not an application filter someone could forget. The most sensitive fields live in a separate schema the ordinary application account cannot read at all.

Every change is audited

Who, which fields, when. Balances and batch states are built from dated entries that are added to, never overwritten.

The Sage import engine

Four validation layers before a file exists, an explicit batch lifecycle, and duplicate protection that makes it impossible for the same approved hour to reach two files.

Two deployment stacks, both green on every commit

Your Azure tenant is the primary target; a portable stack is tested alongside it so nothing quietly assumes Azure. More than 450 automated tests run on each change.

What this site is

A clickable prototype on synthetic data. There is no login yet, nothing on these pages is connected to Sage or to any live system, and the screens are illustrative — a picture of the product on top of the engine that already exists, not the finished product.

Every name, job number, hour and balance you see was invented for this demonstration. No employee data of any kind is present.

And one thing this site is not: WE Hub. WorkWright is not building or replacing the Hub. We are building two applications — WE People and WE Time — that plug into the Hub you already run, at hub.wilkinsonelectric.com/people and /time, by path routing. Everything in this demo lives inside one of those two apps; the demo's front page stands in for the Hub tile a user would tap, nothing more.

A guided tour — about 25 minutes, following one person's whole employment from a no-account job application through to being let go, then up to the seats that run the system — starts from the bar at the top of any page.

Sign-in is decided and being built: Microsoft for wilkinsonelectric addresses, and a regular email with a password for everyone else — each person deliberately admitted, their address verified once with an emailed code. This prototype stays sign-in-free on purpose.

Still being confirmed with you

What still shapes the build, and we would rather ask than assume: your Customize Time Entry view (the real Import Time file arrived and the format is now verified against it); which way quarter-hour rounding breaks ties; the PTO ceiling and carryover cap, where your handbook reads more than one way; and two sign-in details — who may add or remove someone from the admitted list, and whether people who can see sensitive HR data must use Microsoft sign-in.