Files
accounted/app/paused/page.tsx
T
MattssonandClaude Fable 5 aabddb592f feat(billing): multi-user paywall: multi_user capability, 20-day grace, owner-only dormancy (#2099)
* 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>
2026-09-01 11:29:12 +02:00

78 lines
3.3 KiB
TypeScript

import { redirect } from 'next/navigation'
import { getTranslations } from 'next-intl/server'
import { Lock } from 'lucide-react'
import { createClient } from '@/lib/supabase/server'
import { getActiveCompanyId } from '@/lib/company/context'
import { PausedSignOutButton } from './sign-out-button'
/**
* Multi-user seat gate: the landing for a user whose EVERY membership is
* frozen (non-owner in companies whose multi_user entitlement lapsed past
* its 20-day grace). Middleware routes here instead of onboarding, so a
* locked-out colleague is told what happened and who can fix it rather than
* being walked into creating a pointless company.
*
* Self-healing on purpose: the page re-runs the gated resolution first, so
* the moment an owner pays, a reload lands the user straight back in the
* company. Nothing here is stateful.
*/
export default async function PausedPage() {
const supabase = await createClient()
const {
data: { user },
} = await supabase.auth.getUser()
if (!user) redirect('/login')
// Anything accessible after all (an owner upgraded, or the user was made
// owner somewhere) leaves this page immediately.
const companyId = await getActiveCompanyId(supabase, user.id).catch(() => null)
if (companyId) redirect('/')
const { data: memberships } = await supabase
.from('company_members')
.select('company_id, companies:company_id(name, archived_at)')
.eq('user_id', user.id)
type Row = { company_id: string; companies: { name: string; archived_at: string | null } | null }
const rows = ((memberships ?? []) as unknown as Row[]).filter(
(m) => m.companies && m.companies.archived_at === null,
)
// Current display names (company_settings.company_name; companies.name is
// frozen at creation). RLS scopes the read to the user's own companies.
const { data: settingsNames } = await supabase
.from('company_settings')
.select('company_id, company_name')
.in('company_id', rows.map((m) => m.company_id))
const nameByCompany = new Map(
(settingsNames ?? []).map((s) => [s.company_id, s.company_name as string | null]),
)
const companyNames = rows.map(
(m) => nameByCompany.get(m.company_id) || m.companies?.name || '',
)
// No memberships at all means this page is the wrong destination.
if (companyNames.length === 0) redirect('/')
const t = await getTranslations('paused')
return (
<div className="flex min-h-dvh items-center justify-center bg-frame px-4">
<div className="w-full max-w-md rounded-xl border border-border bg-background p-8 text-center">
<div className="mx-auto mb-4 flex h-10 w-10 items-center justify-center rounded-full bg-secondary">
<Lock className="h-4 w-4 text-muted-foreground" aria-hidden="true" />
</div>
<h1 className="font-display text-2xl leading-8 tracking-tight">{t('title')}</h1>
<p className="mt-3 text-sm text-muted-foreground">
{companyNames.length === 1
? t('body_single', { companyName: companyNames[0] })
: t('body_multiple', { companyNames: companyNames.join(', ') })}
</p>
<p className="mt-2 text-sm text-muted-foreground">{t('body_action')}</p>
<div className="mt-6">
<PausedSignOutButton label={t('sign_out')} />
</div>
</div>
</div>
)
}