Control state
Defaults connected, stored read pending. Sensitive changes stay non-retroactive and require reason, version, and audit capture before writes unlock.
Employee workspace
Settings
Owner/Admin
Review operational defaults by control surface instead of scanning one long wall of disabled fields. Pricing, tax, templates, access, delivery, and material taxonomy all stay versioned and audit-ready.
Control state
Defaults connected, stored read pending. Sensitive changes stay non-retroactive and require reason, version, and audit capture before writes unlock.
API defaults
26
Defaults endpoint connected
Groups
12
Operational sections
High risk
32
Require reason when writable
Stored overrides
0
13 fields connected to live defaults/read path
Selected control surface
Margin, quote value, discount, PO thresholds, validity, and rounding.
Review posture
This section is intentionally presented as a read-only control surface until the FastAPI reason, version, effective-date, and audit save workflow is wired. Secret values remain key references only.
Owner decision queue
0
Pending configuration items still need an explicit owner decision.
Stored overrides
0
Active settings already diverging from defaults in this surface.
Secret-backed setup
0
Fields that should resolve by secret-key reference only.
Read-only actions
See prior versions and effective dates once the audit endpoint is wired.
Review before/after payloads for high-risk changes before activation.
Bundle reason, version, and rollout timing before writes unlock.
Confirm owner-review and non-retroactive rules for this surface.
Related control surfaces
Thresholds that trigger owner review before quotes or POs move.
20%
12%
OMR 5,000
3%
OMR 5,000
Base commercial defaults used when calculating and presenting quotes.
14 days
Round to 3 decimal places
Manual rate with source required
Quick help
1. Start with pricing, tax, and payments because they change approvals and issued-document snapshots.
2. Check communications and templates next so sender readiness, secret references, and live-send gates are obvious.
3. Finish with permissions, legal, and material taxonomy because they shape safe access and public-facing content.