cpatpa hardwires Piper Alderman into the account page

The fork is shedding the parts of Mike that only make sense if you're serving many firms at once.

multi-tenantpersonas

cpatpa's account screen no longer asks who you work for. The editable organisation field - and the save logic behind it - is gone, replaced by the firm's name baked straight into the page. The usage-plan and tier display, the kind of thing that matters when you're billing multiple tenants, has been cut too. In its place sits a single new line: whether you're signed in as an Administrator or an ordinary User.

The shape of the change tells the story - far more was deleted than added. This is Mike being narrowed from a product that could host many organisations down to one tailored for a single firm's internal deployment. One caveat for anyone copying the approach: the firm name is written directly into the code, so changing it later means a developer, not a settings page.

So what Worth a look if you're deploying a legal-AI tool inside one firm and want to strip out the multi-tenant scaffolding you'll never use.

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
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