Foundations

AI features & settings

Where QFormance uses AI, how to turn it on, and how to route every AI request through your own provider account so the data stays under your data-handling agreement.

For
Org admins
Find it at
Admin → Organization → AI Settings
Reading time
5 min

In one sentence

AI is built into several workflows — drafting NCRs, summarizing audit evidence, generating meeting minutes, suggesting compliance mappings — and a single AI Settings page controls whether it's on, who pays for it, and which specific features are enabled.

Three things to remember
  • Master toggle is per-org. Off means every AI feature is off, everywhere — useful while you're still deciding policy.
  • Bring your own key routes every AI request through your own provider account, not ours. The data flows under your contract with the provider — your data-handling agreement, your retention rules, your audit trail on the provider side.
  • AI is assistive, never required. Every AI-driven UI works fine when AI is off — the button just goes away.

Where AI is used

FeatureModuleWhat it does
Clause SuggestionsDocumentsProposes compliance mappings for uncovered headings
Document CleanupDocuments (Import)Restructures pasted / imported markup while preserving the text
NCR Draft AssistNon-conformancesDrafts title / description / source / severity from a one-line prompt
NCR Residual RiskNCR (Root Cause tab)Drafts a risk register entry, calibrated to your org's thresholds
Audit Evidence SummaryAudits (Perform)Summarises attached evidence on audit questions
Gap Analysis AIGap AnalysisAssesses a clause against linked context documents
Meeting MinutesMeetingsGenerates structured minutes and action items from notes or transcripts

See the individual module articles for how each feature surfaces in the UI.

Master toggle & provider

Admin → Organization → AI Settings has the top-level controls:

SettingWhat it means
OffEvery AI feature disabled org-wide.
Use platform keyQFormance's provider key (covered by your platform contract; usage may be billed).
Bring your own keyPaste your own provider API key. AI requests go through your account — your data handling agreement, your retention controls, your audit trail with the provider. (Billing also lands on your account.)
Provider keys are write-only after save

The key is encrypted at rest. The UI only shows the last four characters as a hint — the raw key isn't readable again after you save it. Store it in a password manager before you close the dialog.

Per-feature toggles

With the master toggle on, admins can enable / disable each feature independently:

  • Document cleanup
  • Clause suggestions
  • NCR drafting
  • NCR residual risk
  • Audit evidence summary
  • Gap analysis AI
  • Meeting minutes

A disabled feature renders a clear "This feature has been turned off by your administrator" in its UI rather than a broken-looking button — so users know AI isn't being silently flaky.

Usage tracking

The AI Settings usage panel with per-feature call counts and token consumption

The AI Settings page shows usage metrics per feature:

  • Total calls — how often the feature has been used.
  • Token consumption — input and output, separately.

Useful for spotting which features are getting traction, which ones aren't being used, and where token usage is concentrated. For per-call billing detail, check your provider's own dashboard — that's the authoritative source.

Data handling

  • AI calls include only the specific content needed — the question being answered, the document being analyzed, the notes being summarized.
  • No cross-org data mixing. Each call is bounded to the calling org's content.
  • Files (Word, Excel, audit-evidence images) are read server-side; any file that exceeds the provider's per-file limit is flagged in the UI as "attached but not analyzed", not silently truncated.

When AI is off

Every AI-dependent UI has a graceful degradation path:

  • Buttons either hide or show a disabled state with explanatory text.
  • The rest of the workflow works normally — AI is assistive, never required.
Was this helpful?
Suggest an edit →