Risk & controls

Pick whichever connector your team already uses.

Brings audit findings, risk register entries, KRI readings, SoD conflicts, and vendor assessments into dashboards and chat. Built for GRC teams who need committee-ready views without a separate analytics project.

1. 1

   Connect Supabase

   Add a hosted PostgreSQL connector pointed at your GRC schema on Supabase.

2. 2

   Index GRC tables

   Mark audit findings, controls, risk register, KRIs, vendors, and SoD conflicts during indexing.

3. 3

   Ask audit and risk questions

   Try "How many open audit findings do we have by severity?" or vendor tier breakdowns.

4. 4

   Build committee dashboards

   Create audit findings overview and operational risk exposure views for leadership reviews.

• “How many open audit findings do we have by severity?”
• “What is the breakdown of vendors by risk tier?”
• “Show control test pass and fail counts by month for the last year.”

• Connect Supabase (or PostgreSQL) with your GRC and audit schema.
• Mark the 13 core tables during indexing per the cookbook.
• Define risk score and KRI breach rules in connector memory.