CRM Testing Call — Sign-up Fix & Initial Bug Review

wiki/clients/current/hazardos/2026-04-05-crm-testing-signup-fix.md · 625 words · 2026-04-05

Overview

Short working session to unblock Karly and Sebastian from the HazardOS sign-up flow and take a first look at the CRM module. Sign-up was resolved live during the call via a manual Supabase database fix. Initial CRM review immediately surfaced UI and data integrity bugs; testing was paused to give Mark time to clean things up before a more structured session Monday morning.

Date: 2026-04-05
Attendees: Mark Hope, Karly Oykhman, Sebastian Gant

Key Decisions

Testing paused until Monday AM — Rather than continue testing against a known-buggy state, Karly will block Monday morning for a proper CRM review after Mark has applied fixes. Avoids duplicate effort and conflicting observations.
CRM menu should replace main nav when active — When a user enters the CRM module, the main navigation menu should be swapped out for the CRM submenu rather than stacking both, reducing visual clutter.

Action Items

[ ] Mark — Fix CRM UI: replace main nav with CRM submenu when inside the CRM module
[ ] Mark — Clean CRM data: move companies out of the Contacts table; correct Denver School District mapping (currently treated as a contact rather than a company)
[ ] Mark — Investigate and fix error thrown when clicking the Opportunities tab
[ ] Karly — Block Monday AM for HazardOS CRM testing; log findings in shared tracker

Problem: Both Karly and Sebastian were blocked from completing sign-up. Mark identified the root cause as a conflict in Supabase's built-in authorization component — Karly's account existed in the database in a broken state from a prior attempt.

Fix: Mark manually deleted Karly's record from the Supabase users table during the call, then re-sent an invitation. The invitation flow bypassed the company-setup prompt (as expected for org-invited users) and both Karly and Sebastian were able to sign in successfully.

Context from Mark:

"I can work for three days on an app and then spend two days on nothing but the auth. It's unbelievable."

Mark noted that Supabase auth is a recurring pain point and that ^[1] used Clerk instead, which he considers significantly better. Worth flagging as a potential future migration consideration.

CRM Module — Initial Findings

What's Working

CRM module is visible in the navigation menu
Clicking a contact's name opens their detail view

Bugs Identified

#	Area	Description	Severity
1	UI/Navigation	Main nav and CRM submenu stack on top of each other when CRM is active	High
2	Data Integrity	Companies (e.g., Denver School District) are listed in the Contacts table instead of Companies	High
3	Opportunities Tab	Clicking the Opportunities tab throws an error	High

Notes on Data Issue

The Denver School District data appears to be a legacy mapping artifact — it was treated as the "customer" in the old data model and has carried over incorrectly. Mark is aware and working on the separation.

Transcript Excerpts

On the auth frustration:

"I mean, you could write a case study on how much of a pain in the [ass] these authorization parts of these pages is." — Mark Hope

On the CRM menu conflict:

"The main menu should be replaced by the CRM menu when you're in it or something. I have to think about that." — Mark Hope

On pausing testing:

"I'll block some time out like Monday morning to then go and do a bunch of [testing]... that way it gives you [time], instead of double tag team." — Karly Oykhman

^[2]