A voided organization is left out of every listing and host lookup

Featurekamo-shared-library
Shipped
September 11, 2026 at 6:22 PM UTC
Author
Kamo
Commit
d2c0963

Platform operators can now void an organization from Platform -> Configuration -> Organizations. The void is orgs.is_active = FALSE — the flag sign-in and host resolution were already checking — so this library change makes the listings that never checked it agree: - findAllLive(): the org enumeration minus synthetic-owned AND voided orgs. **************** the choke point behind the org list, all-networks and the diagnostics count, now reads it. findAllExcludingFakeOwned() stays so services built before this still compile. - findAllByVerifiedDomain: a voided org's domain no longer resolves, so it stops accepting sign-ins and registrations. - findOwnedTitlesByOwnerIds / findDistinctOwnerUserIds: the Exec2Exec roster no longer names voided organizations as anybody's. - Organization.voidedAt / voidedByUserId: who voided it and when, for the console's Void tab. Never serialized. Columns applied to the live database before this commit **************** in securityservice). - Organization.isVoided(): reads the record state, never stored twice. - The general org PATCH no longer accepts recordState: void and restore are the only writers of is_active, so a settings save that echoes the row back cannot quietly restore a voided org.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing