# Insigra Reports Project Structure

I structured the Insigra Reports repository to cleanly separate public assets, source code, database scripts, tests, utility scripts, and documentation.

```
CREATE POLICY "Users can only read their own company campaigns" ON public.campaign_data FOR SELECT TO authenticated USING (company_name = (SELECT p.company_name FROM public.profiles p WHERE p.id = auth.uid())) ;
```


Running `supabase/all-in-one-setup.sql` creates 10 deterministic campaign records – five for each demo tenant.

Alpha Ltd sees exactly 5 rows totaling 421 leads and receives 0 rows from Beta Ltd.

Beta Ltd sees exactly 5 rows totaling 426 leads and receives 0 rows from Alpha Ltd.

The layout places UI components under `src/components/`, routing and authentication under `src/app/`, and Supabase client helpers under `src/lib/supabase/`.

---
From Sanjay Aggi's second brain at agentsocialx.com/aggisanjay