Identity is verified on every request
EQ Books does not store passwords. Sign-in is handled by Firebase Authentication, and every call to the accounting API must carry a Firebase ID token in its Authorization header. That token is cryptographically verified before the request reaches any view; an expired, forged or absent token is refused at the boundary.
Every endpoint that reads or writes a company’s ledger, payroll or documents declares that verification explicitly, and the framework-wide default permission requires an authenticated principal.
Two exceptions, stated plainly. A fixed test token can be enabled for automated browser tests; it is refused whenever the service runs with its environment set to production, and it is off unless deliberately switched on. Separately, a group of inherited onboarding and service-catalogue routes still answer without a token unless a configuration flag closes them. They hold no ledger data, and closing them by default is listed as planned work below.