video1.0<iframe src="https://www.loom.com/embed/50096e96c1934b519509a0fa183c9f1f" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/50096e96c1934b519509a0fa183c9f1f-8b9a650e9ade68ed.gif572.8853340000001This Loom explains the main fixes to correct incorrect monthly revenue and tenant scoping on the dashboard for clients A and B. For client A, the speaker traced wrong dashboard values to a Supabase DB user mismatch in Docker configuration, then adjusted rounding by moving numeric calculations to the database and formatting only in the frontend, and updated reservation date filtering and timezone handling. They also removed hardcoded property fields by adding an endpoint to filter properties by tenant ID and added month and year selection for the revenue view. For client B, they fixed cache key generation to include tenant ID, property ID, year and month, and frontend filters, and tightened authorization by returning 403 when no tenant is authenticated, using only server-signed app metadata instead of user metadata.