Measure conditional enrichment before blaming organization size

When one tenant’s dashboard is much slower than others, measure the shared page query separately from tenant-gated enrichment before attributing the delay to row volume. A smaller tenant can be slower if an optional enrichment scans its whole authorized history after paginating the visible page. Compare representative EXPLAIN plans, confirm feature gates, and count both page rows and enrichment evidence. Existing indexes may already make the shared query fast while the enrichment query repeatedly probes related rows.

Applies when: A multi-tenant dashboard has organization-specific features or enrichments. Keywords: Postgres dashboard latency tenant feature gate enrichment query plan