Use this checklist to verify the analytics events currently wired in invoice-app.
| Event | Trigger to test |
|---|---|
$pageview |
Navigate between pages/routes |
posthog identify |
Log in as a user and confirm user properties update |
Last Updated: February 11, 2026
This document provides step-by-step instructions for setting up AWS infrastructure to run preview environments for all 4 TabCommerce applications (invoice-app, sqm-chat-backend, tab-finance, transaction-export-service) with Neon databases.
| # RBAC Migration Scope & Effort Estimate | |
| ## Current State Summary | |
| | Layer | Auth Pattern | Count | | |
| |-------|--------------|-------| | |
| | **sqm-chat-backend** | `auth('permissionString')` on routes | ~90 route protections | | |
| | **sqm-chat-backend** | Unique permission strings | ~50 | | |
| | **invoice-app** | Route configs (`authorizedUsers` / `authorizedSeatRoles`) | ~28 routes | | |
| | **invoice-app** | Inline role checks (`user?.is_admin`, etc.) | ~50+ components | |
Last Updated: February 11, 2026
This document provides step-by-step instructions for setting up AWS infrastructure to run preview environments for all 4 TabCommerce applications (invoice-app, sqm-chat-backend, tab-finance, transaction-export-service) with Neon databases.
PR Preview Environments with Neon Databases - Implementation Plan
name: PR Preview Environments with Neon Databases overview: Set up automated preview environments that deploy all 4 repos (invoice-app, sqm-chat-backend, tab-finance, transaction-export-service) using feature branches or dev branch. One preview per Jira ticket—multiple PRs for the same ticket share the same preview URL. Each preview gets its own Neon database. Preview URLs are path-based (preview.tabcommerce.com/TAB-1234). todos:
A bug in the payment allocation logic caused autopay payments to be incorrectly allocated to already-paid billing cycles instead of cycles with outstanding balances. This resulted in a $10 shortfall where the payment was allocated to the wrong billing cycle.