These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Change made directly
- Approval sought by email
- Evidence across inboxes
- Timing depends on people
With SynaptaGrid
- Change submitted as a request
- Approver required to publish
- Timed for a quiet hour
- History keeps the prior value
The situation
The control is real and the evidence is not. Reconstructing who asked, who approved, and what the value was before means searching email and a shared drive — and the change itself went in whenever the person making it happened to be at their desk.
How it is approached
A record change can wait for an approver before it takes effect, or wait for a chosen time, or both. Requests move through pending and then published, rejected or canceled, and draft and published states are kept separately per record, so work in progress is never what the API serves. The record’s own history keeps what the value was before.
What changes
The second pair of eyes becomes part of making the change rather than a message about it. A change timed for a quiet hour no longer needs somebody awake to apply it.