Configure Fitch access and approval controls
Decide who can use Fitch, which business context it may inspect and which proposed changes must wait for human review.
Step by step
- Open Settings → Fitch and confirm current availability, organisation controls and authorised roles.
- Review the data and action boundaries with the owner responsible for the workflow.
- Sign in as an intended user and ask a controlled question about a known test record.
- Compare the response with the source record and distinguish confirmed facts from inference.
- Request a controlled draft action, such as a schedule proposal, and confirm it waits for review rather than changing work immediately.
- Record who may approve material proposals and how unexpected output is reported.
Good practice
Fitch should help investigate and prepare. Keep source records, permissions and explicit approvals authoritative for business-changing actions.
Before you begin
- Fitch is available for the organisation's current plan and release.
- Owners have agreed access, data and approval boundaries.
Setup dependency
Settings that change this workflow
The same task can behave differently between organisations. Check these settings before treating a different result as an error.
/settings/openaiControls organisation access and available AI-assisted operating behavior.
Open in SignBas3 →/settings/usersLimits business records and actions to the same boundaries held by the signed-in person.
Open in SignBas3 →If your workspace behaves differently, record the relevant job, client or record number and raise a support ticket so the team can investigate the exact context.
