Settings

Backend

Supabase project (connected)

Session

—

Owner check

Checking access…

Saving enabled

No

Not supported yet

Delete, rename stacks, reorder, remove from stack, delivery receipts

Data access is limited to the enrolled owner by the database. People with workspace or Supabase management access can still administer the project.

• Owner authenticationPassed

  Verified with the real signed-in owner in the browser on Oct 18, 2026: project create/edit/reload, quarterly snapshot, pin/unpin, Binder card/stack create, and a two-tab revision conflict that kept the draft without overwriting.

• Row-level security policiesTested in isolation

  44 database checks passed on temporary test records (Oct 18, 2026). Not yet re-tested with the real owner.

• Private storageTested in isolation

  Private bucket; owner-folder read/add only. Oct 18, 2026 real owner check: synthetic image upload persisted after reload (card r2, Version 1 renders 96×32); the object's public route, a signed route without a token, and an unauthenticated request were all denied — the public route returned not found, and the other two were refused. Checksum download is not yet verified.

• Import reconciliationNot passed

  No import has been run.

• Tested chat writesNot passed

  Not tested.

• Backup / restoreNot passed

  Not tested.

• CutoverNot passed

  Not started.