Settings > API Keys is an in-memory mock shown to customers; empty state claims it authenticates integrations #287

New Issue

2026-10-25T21:32:13-04:00

logan commented

2026-10-25 21:32:13 -04:00

Found in a UX pass 2026-10-25. Related: #3 (billing mock), #44. Searched open+closed: no API-keys issue.

Settings -> API Keys is a visible tab for every org owner (app/settings/layout.tsx:14) but runs on an in-memory demo module (lib/apiKeys.ts); keys vanish on reload and authenticate nothing. The page carries a "Preview feature" banner (app/settings/api-keys/page.tsx:81), but the empty state still says "Create one to authenticate external integrations against the DRB API" (:99), the modal tells the user to "Copy this key now -- it won't be shown again", and Revoke (:73) has no confirm. The banner references a source file customers cannot read.

Fix: hide the tab until a backend exists (or mark it "Coming soon" and remove Create), and drop the empty-state claim.

Found in a UX pass 2026-10-25. Related: #3 (billing mock), #44. Searched open+closed: no API-keys issue. `Settings -> API Keys` is a visible tab for every org owner (`app/settings/layout.tsx:14`) but runs on an in-memory demo module (`lib/apiKeys.ts`); keys vanish on reload and authenticate nothing. The page carries a "Preview feature" banner (`app/settings/api-keys/page.tsx:81`), but the empty state still says "Create one to authenticate external integrations against the DRB API" (`:99`), the modal tells the user to "Copy this key now -- it won't be shown again", and Revoke (`:73`) has no confirm. The banner references a source file customers cannot read. Fix: hide the tab until a backend exists (or mark it "Coming soon" and remove Create), and drop the empty-state claim.

logan added the

labels 2026-10-25 21:32:13 -04:00

Sign in to join this conversation.