AlsoNotifyTrust is a product feature.
Authentication, safer email rendering, and reports that agree on what the numbers mean.
- 01Sign in
- 02Protected workspace
- 03Shared KPI rules
- 04Consistent export
Trust is a product feature.
AlsoNotify brings task tracking, calendars, leave management, finance, reporting, and notifications into a shared work platform. Its frontend uses Next.js, React, and feature-based components.
The problem to work through
The same KPI could receive a different rating in the interface and the exported PDF. Protected page shells were guarded only in the client, while email styles were being dropped before their scoping code could run.
One meaning for a number
I unified KPI thresholds so the employee drawer and PDF report use the same banding function. Previously, 72% occupancy could read Low on screen and appear green in the export.
A safer entry into the workspace
I constrained post-login redirects to local paths, added a server-side cookie-presence route guard, and tightened replay masking. Backend verification remains the authentication boundary.
Email styling with boundaries
I fixed the sanitizer path that discarded leading style blocks and corrected the scoping expression that broke media rules. Existing CSS sanitization then applies to those blocks as intended.
One shared KPI definition
The documented reconciliation included 813 passing tests across 73 files. That is the verification reported for that change, not a current coverage claim for the entire product.
What I take from it
Consistency matters at the seams: an export should mean the same thing as the screen, and rendering a document should preserve its layout without allowing it to restyle the surrounding app.