8 min guideUpdated August 2026App review required

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.

Best forOwner / Admin
Before you beginUse a representative record and confirm you have the permissions required for this area.

Step by step

  1. Open Settings → Fitch and confirm current availability, organisation controls and authorised roles.
  2. Review the data and action boundaries with the owner responsible for the workflow.
  3. Sign in as an intended user and ask a controlled question about a known test record.
  4. Compare the response with the source record and distinguish confirmed facts from inference.
  5. Request a controlled draft action, such as a schedule proposal, and confirm it waits for review rather than changing work immediately.
  6. 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.

When you are finishedAn authorised user can ask a controlled question and any material proposed change remains reviewable before it is applied.

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.

Fitch settings/settings/openai

Controls organisation access and available AI-assisted operating behavior.

Open in SignBas3 →
Roles and permissions/settings/users

Limits business records and actions to the same boundaries held by the signed-in person.

Open in SignBas3 →

Screen reference

What you will see

Fitch workspace using synthetic SignBas3 business information
Use Fitch inside normal access boundaries and review material proposals before applying them.

Screens show the synthetic BrightLine demonstration workspace. Your records, permissions and configuration will change the details you see.

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.