Account page: hardcoded org name, role label replaces usage tier

Single commit reshaping the Account page for a single-tenant deployment. The per-user organisation field and the Usage Plan section are gone; in their place, a hardcoded "Piper Alderman" line and an "Account type" field showing "Administrator" or "User" derived from the JWT role.

multi-tenantbranding

Commit 684223b9 (+16/-88 across 3 files) strips the UI paths that only made sense for a multi-tenant SaaS product.

The organisation field on the Account page - previously an editable input that wrote to user_profiles.organisation - becomes a read-only paragraph with the constant ORGANISATION_NAME = "Piper Alderman". The updateOrganisation function and all state managing it (organisation, isSavingOrg, orgSaved) are deleted from the component. The UserProfileContext loses updateOrganisation as well.

The Usage Plan section, which displayed profile?.tier || "Free", is removed entirely. Nothing replaces it in the user-facing account view. Instead, a new "Account type" field shows user?.role === "admin" ? "Administrator" : "User". The sidebar footer, which previously called getUserTier() to show "Free", now calls getAccountTypeLabel() returning the same role-derived string.

The database columns user_profiles.organisation and users.tier are deliberately left in place. The commit comment notes them as cleanup debt for the next schema sweep. The wire shape doesn't change; the columns just aren't read or written by UI code any more.

So what Skip unless your fork is also single-tenant and you want to remove the org/tier UI paths. The "delete UI now, drop column later" shape is fine as a deployment pattern. The backend columns survive, so this doesn't create a migration dependency. If you're running multi-tenant or still want per-user org labels, there's nothing here for you.

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.

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.