/ SONDA · ENTERPRISE

A change waits for the people who have to see it first.

An approval flow drawn on a canvas — who approves, how many of them, in what order, under what conditions — and enforced where it counts: a submitted change is held from the team until it is approved, and the item is frozen for everyone, the author included. Locks for the hours someone needs a component to themselves. A merge that only argues about the fields both sides touched.

APPROVALS ON A CANVAS LOCKS 1 – 168 H THREE-WAY MERGE 2 – 100 REVISIONS KEPT

The nodes

ApproverApproved, changes requested, or rejected. An author never approves her own change.
TogetherAll of them, any one, or N of M.
If the change…Creates, modifies, deletes, touches scripts, touches auth, comes from a member — a branch per answer.
Tell peopleMembers and extra addresses mailed, with templates for the change and its originator.
EndApproved or Rejected. On reject: discard, keep, or send back for another round.
/ WHAT HAPPENS TO THE ITEM

Submitted, frozen, approved, merged. Nothing slips past.

A flow sits on a project, a folder or a request, and the nearest one wins. A change under it goes up as a submission — the exact proposed content and the revision it is based on — and the item is frozen for everyone until the flow has spoken, the originator too. The backend refuses a save, a publish or a conflict resolution on it, whoever asks.

Approved, it is merged against its base field by field and publishes through the approval path alone. If the store moved on and the merge is not clean, it goes back as stale. Below it, an edit lock: one member's edits only, for the hours the work needs.

Signed and sealed in the team store
/ APPROVALS

Scoped, frozen, enforced.

A flow on a project, a folder or a request; the nearest one wins.

The submission carries the change and what it was based on.

The exact proposed content and the revision it is based on. The approver sees a field-level diff. The item is frozen for everyone while it is open — the originator too — and the lock is visible in the tree and the editor.

No way around it.

A manual save, a manual publish and a conflict resolution cannot bypass approval. An approved change publishes through the approval path alone. Resubmission restarts the full review. The originator can withdraw; an administrator can void.

When the store moved on, never half-right.

An approved change is merged against its base. An unclean merge goes back to the originator as stale, never published half-right. A guest division's changes to a shared workspace wait for the home administrators.

/ LOCKS, MERGE, HISTORY

The rest of working together without stepping on each other.

Each one signed and sealed like everything else in the store. A merge argues only about the fields both sides touched: everything else settles itself, and a difference in how a file was written is not a difference at all.

Beside it, an approved change meeting a store that moved on. Everything merges but one field — so it goes back to the originator as stale, and nothing is published half-right.

# PUT /orders/{id} · approved · merged against its base # base rev 14 · the store moved on to rev 15 · the change, approved headers, by key X-Idempotency-Key added in the change kept X-Trace added in the store kept checks, by stable id status is 200 added in the change kept timeout 30 s → 60 s, both sides resolves itself body key order only not a conflict body.currency both, differently conflict not clean → back to Ana M. as stale · nothing published # resubmitted, it starts the full review again
Edit locksTake a component for one member's edits, from one hour to a week, with a reason. Everyone else is read-only, the administrator included — though the administrator can lift it. A folder lock covers everything under it.
ToldThe administrator, the project, or picked people — told when a lock is taken, and again on release. A Locks page lists all of them.
MergeAgainst the common base, field by field. Query parameters, headers and path variables merged by key; checks, examples and saved messages by stable id. A one-sided change wins on its own; the same change from both sides resolves itself.
ConflictsOnly fields both sides changed become conflicts — resolved one by one, or all at once: Keep this computer's, or Take the store's. Serialization-only differences are not conflicts.
HistoryEvery kept revision with who published it, from where and when; two to a hundred per item, twenty by default. Side-by-side or inline diff against your copy.
RestoreOpen an old revision without restoring it, or restore it — and the replaced one lands in history too. The previous publisher is told when a revision is merged or replaced.
/ LOCKFLARE SONDA

Approvals, locks and merge, in the free edition.

Change governance, listed →