cpatpa strips multi-tenant scaffolding off the account page

Piper Alderman's fork drops the org picker and free-tier label - what's left is just "who are you, and what can you do here?"

multi-tenantbranding

The Account page used to assume Mike was a multi-firm product: pick your organisation, see your usage plan, maybe upgrade. cpatpa's deployment is one firm, so that whole frame is gone. The organisation field is now a fixed line reading "Piper Alderman", and the old "Usage Plan / Free" section has been removed. In its place is a simple "Account type" showing whether you're an Administrator or a regular User - the same label now appears in the sidebar where the tier used to sit.

The team deliberately left the underlying database columns in place. The screens stop reading them today; a future schema cleanup can drop them once nothing depends on them. It's a tidy way to ship a single-tenant experience without a risky data migration on day one.

So what Worth a look for anyone deploying Mike inside a single firm and wondering how much of the SaaS scaffolding can be quietly hidden rather than ripped out.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from cpatpa/PIP, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

684223b9 Account: show role, drop per-user organisation field, drop tier Claude 2026-05-16 ↗ GitHub

SHA	Subject	Author	Date
`684223b9`	Account: show role, drop per-user organisation field, drop tier	Claude	2026-05-16	↗ GitHub
commit body PIP is single-tenant for Piper Alderman; there is no per-user organisation and no usage plan. The Account page now shows the organisation as a read-only "Piper Alderman" line, displays the user's role ("Administrator" or "User") in a new Account type field, and the legacy "Usage Plan" / "Free" section is removed. The sidebar tier line now shows "Administrator" or "User" instead of "Free". Dead `updateOrganisation` removed from UserProfileContext. The backend `organisation` column on user_profiles is untouched for now; the UI just no longer reads or writes it. Tier likewise remains in the API response but unused by the UI.

commit body

PIP is single-tenant for Piper Alderman; there is no per-user
organisation and no usage plan. The Account page now shows the
organisation as a read-only "Piper Alderman" line, displays the
user's role ("Administrator" or "User") in a new Account type field,
and the legacy "Usage Plan" / "Free" section is removed.

The sidebar tier line now shows "Administrator" or "User" instead
of "Free". Dead `updateOrganisation` removed from
UserProfileContext.

The backend `organisation` column on user_profiles is untouched for
now; the UI just no longer reads or writes it. Tier likewise remains
in the API response but unused by the UI.

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-372.md from inside the repo you want the changes in.

⬇ Download capture-thread-372.md