Question
On a production-like install (multi-org enabled: enterprise package + license), platform/system tables never carry organization_id — including rows created today. Business-object tables do carry it (we backfilled our own legacy rows project-side). Please confirm: is the absence of org scoping on these system tables by design, or should they be org-scoped (and if so, is a migration planned)?
We are not reporting a malfunction — everything works. We only need the design intent confirmed, and to know whether org markers will be added later, so we can decide whether to account for it in operations.
Inventory (read-only scan, 2026-08-23, 112 org-column-bearing tables scanned)
Platform tables where 100% of rows (old and new) lack organization_id — 9,577 rows total:
| Category | Rows |
|---|
| Logs (job logs 5,613 / audit logs 1,510 / feed 916 / automation runs 5) | 8,044 |
| Messaging (inbox messages & receipts 766 / notifications & deliveries 410 / email 96 / templates 28) | 1,300 |
| Config & metadata misc (capabilities / metadata / files / permission sets / positions etc.) | 233 |
Environment
@objectstack/*@17.2.0, PostgreSQL 16- Multi-org enabled and in active use; 47 business tables are fully org-scoped and clean
Question
On a production-like install (multi-org enabled: enterprise package + license), platform/system tables never carry
organization_id— including rows created today. Business-object tables do carry it (we backfilled our own legacy rows project-side). Please confirm: is the absence of org scoping on these system tables by design, or should they be org-scoped (and if so, is a migration planned)?We are not reporting a malfunction — everything works. We only need the design intent confirmed, and to know whether org markers will be added later, so we can decide whether to account for it in operations.
Inventory (read-only scan, 2026-08-23, 112 org-column-bearing tables scanned)
Platform tables where 100% of rows (old and new) lack
organization_id— 9,577 rows total:Environment
@objectstack/*@17.2.0, PostgreSQL 16