Skip to content
MSO CloudDocumentation

Why it can be trusted

On this page

Each boundary around an organization's data, the mechanism that holds it and the check that proves it, plus what lets a number on screen be signed off.

Boundaries, mechanisms and proofs#

Boundary Mechanism Proof
One organization's data Row-level security forced on every organization table; no context, zero rows Tenancy gate run as the real runtime identity (tenant isolation)
Brands inside an organization A brand policy leg; the brand in every rollup key Brand-isolation gate (Multi-brand workspaces)
Which organization a request is in The host decides on a tenant domain; a switch is refused Audits refuse session-based organization reads (Tenancy and security)
Secrets Envelope-encrypted under versioned keys; never returned, logged or archived Security scan on every push (credentials)
Real names One masking decision per request; by default editors, viewers and share links see aliases Unmasked-field audit (Identity masking)
Messages leaving the platform Platform channel, organization setting and recipient link must all allow it In-app only until all three pass (Notifications)
Sign-in Password, magic link, passkeys, two-factor codes; LDAP/AD and Google sign-in where an admin turns them on Directory bind fails closed (sign-in, LDAP/AD login)
Connected apps One sign-in issued by MSO Cloud; an app receives only the scopes it was registered for, and a signed event reports a member or access change Redirect URIs are registered literals, checked by audit (App family and sign-in)
Third-party estimates Own plane and label; never a KPI or a measured outcome Plane-isolation audit (market estimates)
Recorded decisions Append-only ledger; a correction is a new row Replay from frozen inputs as a build gate (replay)
No special-case code One build for every organization; differences are configuration Ratchet audit refuses customer names and ids (System context)

Why a number can be signed off#

Hiệu quả bán hàngTháng nàyMọi sànThương hiệu ADoanh thu thuần1.284.500.000 ₫tổng của bảng bên dưới=SànDoanh thu thuầnTikTok Shop612.300.000Shopee418.700.000Lazada253.500.000Tổng1.284.500.000Xuất ExcelBảng và tệp xuất đọc cùng một định nghĩa chỉ sốTiền là số nguyên VND; ngày theo giờ Việt Nam=hieu-qua-ban-hang-2026-10-03.xlsxTikTok Shop612.300.000Shopee418.700.000Lazada253.500.000Tổng1.284.500.000same cells, same definition
One number on three surfaces. The headline tile equals the exact sum of the rows the table draws, and the export reads the same cells. A gate fails when they differ.

Each metric has one definition that dashboards, the data assistant, alerts and exports read; a second derivation that shares a wrong assumption is not a cross-check (Measurement and honest numbers). Metric surfaces carry reconciliation assertions that run as a gate: a headline equals the exact sum of its rows, a rolling window equals the period value, two sources for one day are combined once. Expected values are anchored outside the code, in the organization's own export, and a disagreement is checked against that source before anything is corrected (metric reconciliation). Money is an integer number of dong and every date path uses Vietnam time, so the screen equals the download (Exports: CSV, Excel, PDF). Operators can run the same check on their own uploads, per order and per day (Data validation).

When the data cannot support an answer#

Situation What happens
A rule condition has missing data It evaluates to "unknown" and the rule does not match (The decision engine)
A card lacks data for the period It shows the reason, not a zero (Organization datasets and measures)
A generated sentence has an untraceable number It is dropped before publication (Measurement and honest numbers)
The organization has no rows for a data area The assistant does not mention it, even to a platform administrator (Data assistant)

What the platform does not do#

It does not Because
Act in the organization's channels It recommends and records; a person acts (autonomy ladder)
Anonymize data Masking is a display layer, not deletion (Identity masking)
Let one organization read another's Platform staff hold a separate role with no organization membership (System context)