Function · security
Staff sign-in & role gates
Let strangers read the door. Let only approved people open the tools.
Problem
A public marketing site and a staff app on the same domain create a blunt question: who gets past the welcome page?
What you get
Google OAuth for company email, JWT sessions, and per-area permission checks. The public can browse guides and the product door; API routes and app modules stay gated.
Where it shows up
Live on the DGS Operations door — Staff sign-in only works for authorized accounts.
Deep application screens require authorization. This page and the public guides do not bypass staff login.