Control state
API defaults Write workflow locked
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
Settings control panel
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.
Showing API defaults while stored setting overrides are unavailable.
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
Bank transfer
Bank account, payment reference, payment proof, and client access policy.
7 default / 6 pending 13 fields Section-level audit required 1 high risk
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
6
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
Bank details
Named bank account identifiers used on instructions and proofs.
5 fields 5 pending
Bank name
Not configured
Not configured
payments:bank_name
Account name
Not configured
Not configured
payments:account_name
Account number
Not configured
Not configured
payments:account_number
IBAN
Not configured
Not configured
payments:iban
SWIFT/BIC
Not configured
Not configured
payments:swift_bic
Payment rules
Client-facing payment rules and reference format defaults.
1 high-risk field 1 pending Reason and versioning apply
Currency
Default
OMR
payments:currency
Payment reference format
Default
DS-{quote_number}-{client_code}
payments:payment_reference_format
Payment instructions
Not configured
Bank transfer instructions are not configured.
payments:payment_instructions
Advance payment rule
Default
Advance payment required before production release.
payments:advance_payment_rule
Balance payment rule
Default
Balance payment required before dispatch release.
payments:balance_payment_rule
Payment proof file types
Default
pdf, jpg, jpeg, png
payments:payment_proof_allowed_file_types
Payment proof max size (MB)
Default
10
payments:payment_proof_max_file_size_mb
Require verified payment before full client access
Default High risk
Enabled
payments:client_full_access_requires_payment_verified Reason required when writable
Quick help
What to review first
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.