Cashbook AI Concept comparison

PRD-123 LedgerVault feature flags and Nova admin — design concepts

LedgerVault staff sign in to a new Nova admin and turn the Cashbook features on for one user at a time. These screens are LedgerVault’s and Nova’s, not Cashbook’s, so they use those apps’ own look. Pick one Feature Flags tool concept and one admin account option. The shared screens are the same in every concept.

1. The Feature Flags tool — pick one

Concept A — Straight port

Open full ↗

The idea: copy Cashbook’s tool as it is (a list page, then a detail page) and only remove Beta.

  • 👍 Least to build; the team already knows it; the specs copy over.
  • 👎 The state saves on change, with no confirm: one slip on “All users” shows Cashbook to Xero’s reviewers. People can be added only after the switch to Specific users.

Critic (1–5): Xero n/a · Hierarchy 3 · Clarity 3 · States 2 · Flow 2 (save-on-change kept on purpose)

Concept B — One page, with a confirm step ✓ Chosen

States ↗Open full ↗

The idea: each flag is one card with its state and its people list; every state change asks first and says who is affected, in numbers.

  • 👍 No accidental “All users”; the people list is there in every state, so it can be filled before the switch; it says why a person cannot be found.
  • 👎 Changes Cashbook’s tool, so the two copies drift unless Cashbook takes the same change.

Critic (1–5): Xero n/a · Hierarchy 4 · Clarity 4 · States 4 · Flow 4

Concept C — Find the person first

Open full ↗

The idea: search a LedgerVault user, then see and switch that user’s flags; the flag-wide state is on a second tab.

  • 👍 Matches the request staff get (“turn it on for Aroha”); shows one person’s access at a glance.
  • 👎 A different tool from Cashbook’s; the flag-wide state hides on a second tab; closer to a Users page, which is out of scope.

Critic (1–5): Xero n/a · Hierarchy 3 · Clarity 4 · States 2 · Flow 4

2. Admin accounts: create, forgot password, lost phone (option 1 approved by Aidan, CAS-2614)

Option 1 — Commands a developer runs ✓ Chosen

Open full ↗

The idea: admin:create, admin:reset, admin:remove on Laravel Cloud print a one-time link that a developer sends privately.

  • 👍 Smallest build; no email; nothing for Octane to keep (CAS-2493). Follows decision 2026-10-16 (no admin screen) and the existing user:make-admin.
  • 👎 A locked-out admin waits for a developer with Laravel Cloud access.

Option 2 — An Admins page in Nova

Open full ↗

The idea: any admin adds an admin or resets one’s sign-in, and gets the same one-time link to send. The first admin still comes from a command.

  • 👍 Admins help each other; no developer needed after day one.
  • 👎 Goes against decision 2026-10-16 (no admin screen); a new Nova resource, beyond “only what the flag tool needs”.

3. Shared screens — the same in every concept

Nova admin sign-in, every state

Open full ↗

Password, code, wrong password, wrong code, too many tries, recovery code, first-time QR setup, and a LedgerVault user who is not an admin.

LedgerVault with the flag Off (default)

Open full ↗

1 stat card, no tabs, no tick boxes, no Cashbook column, no Import button, no CashBookAI in the app menu.

LedgerVault with the flag On

Open full ↗

The same user after a grant: what users with the env switch on see today.

Flag revoked while the page is open

Open full ↗

Today the Import dialog shows “Not Found”. Proposed: a plain message with no Cashbook name, and a Reload button.

Flag revoked while an import runs

Open full ↗

The status poll now gets a 404 and today the page silently forgets the import. Proposed: say that updates stopped and the import may still finish. The gate stays, as Aidan asked on CAS-2462.

How to use this board

Walk each concept through the same lenses: what staff see first, how many decisions a grant takes, the first-run and empty states, and what one wrong click can do. The chosen direction gets written up in DESIGN.md, then built high-fidelity by /cb-prototype.