aabddb592f
* feat(billing): multi-user seat gate: multi_user capability, 20-day grace, owner-only dormancy Multiple people in one company becomes a paid capability (multi_user, the eighth PAID key). Derived at access time from capability_grants, no status column, no enforcement cron: - entitled: active grant (trial/stripe/team/manual/comp), everyone works - grace: newest grant expired < 20 days ago; countdown banner for everyone in companies with > 1 user; invites still allowed - frozen: only role=owner resolves; other memberships go dormant (rows untouched, paying reactivates instantly); invites 403 with paid-plan upsell Enforcement: new resolve_active_company_gated RPC (zero-arg RPC and RLS twin untouched: they also run on self-hosts, where the gate never bites), gated query fallback for service-role/API-key paths, setActiveCompany guard, MCP company-access check, invite route. Middleware routes all-frozen users to a new /paused page; the switcher greys locked companies. Migration 20260901081417 (applied to staging): trial trigger seeds multi_user, backfills for mid-trial companies, active Stripe subs, team agreements, and a grandfather grant (expires now, i.e. grace = deploy + 20 days) for existing unpaid multi-member companies. Daily cron mails owners at grace start and last day. Strings in sv+en; pg-real + unit tests included. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4tNt8wRG3a5iuU1JE2pnP * fix(billing): multi-user seat gate hardening from skeptic review - Stripe cancel now EXPIRES the multi_user stripe grant instead of deleting it: the 20-day grace window hangs on an expired row, so a deleted one froze churned payers' staff instantly with no banner and no mail. Other stripe grants keep the freeze-and-retain delete. - New SECURITY DEFINER company_multi_user_state() RPC (migration 20260901083726, applied to staging) and RPC-first getMultiUserState: capability_grants RLS hides team-scoped rows from non-team users, so user-client reads misread byra-covered companies as frozen (switch refusal, wrong switcher locks). - Byra-kind teams get a standing team-scoped multi_user grant (backfill + teams trigger): byra client companies have no company-scoped trial by design, so a grantless byra team would freeze every consultant and client user. - Comped/manual companies with active PAID-key grants extend to multi_user (a comped company must not read as paying while locking out user two). - /api/v1 gets the same dormancy gate as MCP (frozen non-owner -> 403). - PGRST202 on resolution fails OPEN (pre-migration DB has zero multi_user rows; the gated fallback would have frozen every non-owner mid-deploy). - Grace cron: covers team-scoped lapses (byra agreement ending) and skips the start mail for the hand-mailed grandfather cohort. - Tests updated/added across all touched surfaces; pg tests for the new RPC and byra trigger; trial-suppression pg test extended to 8 keys. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4tNt8wRG3a5iuU1JE2pnP * fix(billing): decouple seat-gate env check and fail open on gate read throws CI round 1 on #2099: - isMultiUserEnforced no longer imports has-capability: several route test suites partially mock that module and the vitest mock guard threw from inside the v1 seat gate, turning expected 4xx responses into 500s. multi_user is never a connector capability, so the bypass reduces to the same env reads, now inlined. - getMultiUserState wraps its resolution in a fail-open try/catch: a client without .rpc or a thrown network error must never lock users out. - no-phantom-columns ceiling 391 -> 393 with reasons: the seat gate's .or() scope filter (server-resolved UUIDs) and the Stripe cancel expiry update's timestamp .or(); all columns in both strings are literals. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4tNt8wRG3a5iuU1JE2pnP * fix(billing): membership-guard the multi-user entitlement RPCs (Superagent P3) company_multi_user_ok and company_multi_user_state are SECURITY DEFINER and were granted to authenticated with a caller-supplied company UUID: any logged-in user could probe an arbitrary company's billing state and grace deadline across tenants. Migration 20260901091752 (applied to staging) requires an auth.uid() membership in the target company when a JWT is present, keeps service-role/definer contexts unrestricted, and clamps the grace window to [0, 20] days. pg tests: stranger gets false/NULL, member reads normally, oversized p_grace_days cannot widen the probe. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4tNt8wRG3a5iuU1JE2pnP --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
76 lines
3.3 KiB
TypeScript
76 lines
3.3 KiB
TypeScript
/**
|
|
* Pure multi-user access model: no I/O, no env reads, imported by both
|
|
* has-capability.ts (which derives the state from grant rows it already
|
|
* fetched) and multi-user.ts (the async lookup helpers). Keep it that way:
|
|
* this module must never import from either of them.
|
|
*
|
|
* The `multi_user` capability gates PEOPLE, not a feature surface, so its
|
|
* lapse is softened by a grace window (founder decision 2026-09-01):
|
|
*
|
|
* entitled : an active multi_user grant (trial/stripe/team/manual/comp).
|
|
* Everyone in the company works normally.
|
|
* grace : the newest grant expired less than MULTI_USER_GRACE_DAYS ago.
|
|
* Everyone still works; the countdown banner shows.
|
|
* frozen : expired at least MULTI_USER_GRACE_DAYS ago, or never granted.
|
|
* Only role = 'owner' memberships resolve; every other
|
|
* membership is dormant (rows untouched: paying reactivates
|
|
* them instantly), and new invites are blocked.
|
|
*
|
|
* The 20-day grace is the PERMANENT rule for every lapse (trial end,
|
|
* subscription cancel, comp expiry), not a one-off migration affordance:
|
|
* the grandfather backfill simply inserts a grant expiring at deploy time
|
|
* so existing multi-member free companies enter the same window.
|
|
*
|
|
* company_capability_config is deliberately ignored for this key: a config
|
|
* disable has no expiry to hang the grace window on, and freezing people
|
|
* out of their bookkeeping must never happen through a side channel. The
|
|
* DB twin (public.company_multi_user_ok) implements the same rule.
|
|
*/
|
|
|
|
export const MULTI_USER_GRACE_DAYS = 20
|
|
|
|
const GRACE_MS = MULTI_USER_GRACE_DAYS * 86_400_000
|
|
|
|
export type MultiUserState = 'entitled' | 'grace' | 'frozen'
|
|
|
|
export interface MultiUserAccess {
|
|
state: MultiUserState
|
|
/** End of the post-lapse grace window (ISO); set only while state === 'grace'. */
|
|
graceEndsAt: string | null
|
|
}
|
|
|
|
export interface MultiUserGrantRow {
|
|
expires_at: string | null
|
|
}
|
|
|
|
/** Derive the access state from the company's multi_user grant rows. */
|
|
export function computeMultiUserState(
|
|
rows: readonly MultiUserGrantRow[],
|
|
now: number,
|
|
): MultiUserAccess {
|
|
let newestExpiryMs: number | null = null
|
|
for (const row of rows) {
|
|
if (row.expires_at === null) return { state: 'entitled', graceEndsAt: null }
|
|
const expiryMs = new Date(row.expires_at).getTime()
|
|
if (Number.isNaN(expiryMs)) continue
|
|
if (expiryMs > now) return { state: 'entitled', graceEndsAt: null }
|
|
if (newestExpiryMs === null || expiryMs > newestExpiryMs) newestExpiryMs = expiryMs
|
|
}
|
|
if (newestExpiryMs !== null && newestExpiryMs + GRACE_MS > now) {
|
|
return { state: 'grace', graceEndsAt: new Date(newestExpiryMs + GRACE_MS).toISOString() }
|
|
}
|
|
return { state: 'frozen', graceEndsAt: null }
|
|
}
|
|
|
|
/**
|
|
* The dormancy rule, in one place. Owners always keep access (a company must
|
|
* never lock out the person who can pay); everyone else needs the company to
|
|
* be entitled or in grace. Membership `source` is deliberately NOT consulted
|
|
* (founder decision 2026-09-01, superseding the earlier byrå exemption):
|
|
* byrå consultants stay in through the company's or their team's grant, not
|
|
* through a role carve-out.
|
|
*/
|
|
export function isMembershipDormant(role: string, state: MultiUserState): boolean {
|
|
return state === 'frozen' && role !== 'owner'
|
|
}
|