bgevconsultancy puts an approval desk in front of every new organisation user

This fork replaces instant access with a clear admin decision before a new signup can enter an organisation.

securitymulti-tenant

New users now wait in a holding area until an administrator approves or denies their request. Approval creates their organisation membership; denial keeps them out.

The work also gives administrators two ways to manage that queue:

  • Organisation administrators can approve or deny requests for their own organisation.
  • Super-administrators can manage pending requests across organisations.

It removes the old assumption that every signup should be dropped into a default organisation. That matters because multi-tenant security is not only about separating client data after access is granted. It is also about deciding who gets access in the first place.

So what Firms and legal-product teams running separate client or business workspaces should care: this is the missing front door for controlled onboarding.

View this fork on GitHub →

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

Commits in this thread

3 commits from bgevconsultancy/Helm-v2, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
defd28cb T10.1 invitation gating schema Clava Stripdown 2026-07-23 ↗ GitHub
Add pending|approved|denied profile gating with approve/deny RPCs that insert org_members, update handle_new_user (no auto-approve), and enforce requireApproved without Default Org bootstrap.
d59d2c43 T10.2 org admin approve UI Clava Stripdown 2026-07-23 ↗ GitHub
Add proxy access gates, pending/out pages, org-admin approve/deny UI, and super-admin org management while keeping MFA.
2d386a77 T10.2 include /out route Clava Stripdown 2026-07-23 ↗ GitHub
Track the no-membership /out page; gitignore Next export out/ still applies elsewhere.

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-960.md from inside the repo you want the changes in.

⬇ Download capture-thread-960.md