How ONE works
One workspace. One set of records.
ONE is a business operating system, not a bundle of tools that happen to be sold together. The difference shows up at the handovers.
The spine
Identity, company, membership, capability.
Everything in ONE hangs off four ideas, in that order. A person has an identity. A company is a workspace. A membership is that person's place in that company. A capability is what the membership may actually do.
Identity
Who someone is, independent of any company. One person can belong to more than one.
Company
The workspace. Every record carries the company it belongs to, so two companies cannot see each other's work.
Membership
The link between the two, and where access lives. Ending a membership ends the access.
Capability
What may be done. Explicit, and not implied by a job title.
The rule underneath
Two things that must agree are written together.
When a sale is recorded, the sale and its accounting entry are one write. Either both land or neither does. The same holds for a stock movement and the order that caused it, and for a payment and the cash it moved.
That is a small-sounding rule with a large consequence: there is no window in which the books and the operation disagree, so reconciling them is not a monthly job.
What happens when something goes wrong
ONE says so.
An unread value is not shown as a known one
If ONE cannot load something, the screen says it could not — rather than showing an empty list that reads as "nothing here".
A partial result says partial
When a job finishes with a piece missing, the piece is named. Silence is reserved for success.