Who: Organisation access administrator with organisation-wide iam.manage authority, or the approved recovery administrator. Entry: Access & identity > Business configuration. Availability: Deployed to JPWTech on 26 October 2026. Runtime settings reads and append-only database grants were verified; publication/reset workflows passed local tests. Other installations must confirm their release.
- In Forms, select a record type and find its field. Set a clear display label and additional guidance. Blank overrides retain the standard wording; internal field names and API keys stay unchanged.
- Choose Required when saving for information needed on every explicit save. Alternatively, expand Required in selected statuses and choose the relevant stages. For example, require a contract's responsible owner in In review and Active while allowing an incomplete Draft. Choose every later status where the requirement must continue. Built-in required fields cannot be relaxed.
- In Review windows, set the supported advance-warning periods in whole days from 1 to 365. Most feed the daily compliance sweep and related summaries; the policy-review window controls the report's due-soon list. Saving does not run a job or send a notification. A narrower window does not rewind an already advanced lifecycle state.
- Select Review changes, inspect the before/after values, enter a meaningful reason and confirm. Reopen an affected record editor to verify the label, guidance and validation. Test both a permitted draft and an incomplete submission that should be rejected.
- Use History to see the administrator, date, revision and reason. Restore defaults requires a reason and creates another revision; it does not erase records or prior history. If another administrator saved first, reload and reapply the intended change rather than overwriting their work.
These settings cover the listed fields in 18 record types and 12 review windows. Existing records are not rewritten. Stronger requirements apply on their next explicit save or applicable workflow transition; unattended expiry checks continue. Editing a field label affects record editors, not every report heading or existing document. The API enforces the rules even when a client bypasses the form.
Additional guidance is appended to the standard field guidance. Unsaved configuration edits remain in the open page only: save or deliberately discard them before using browser Back, reloading or closing the page. This form does not provide draft recovery.
Setup directory links the existing register-type custom fields, units, roles/scopes, framework requirements, maturity definitions, risk appetite and training requirements. Each area retains its own permissions and procedures. This page does not provide arbitrary new fields on every entity, a workflow/approval-chain designer, editable security controls or a scheduled-report builder. See the configuration scenario review (administrator reference) for current coverage and proposed extensions.
Complete when: A saved revision produces the intended form and review behaviour for this organisation, with a useful reason, verified permissions and no unintended submission block. Configuration is not authority to alter regulatory wording, financial calculations or immutable evidence.