Fine-tuned model management

Understand fine-tuned model list ordering

Know why some models appear before others.

Audience: CRM administrators and authorised staffPermission: Settings: ViewModule v1.0.0
Exact navigationAdmin Area → Setup → Settings → AI → OpenAI → Advanced Features → OpenAI Fine Tuning
Before you begin
  • Use an account with Settings: View and confirm the intended record or setting before making a change.
  • Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
  • Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Know why some models appear before others. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

  1. Open Admin Area → Setup → Settings → AI → OpenAI → Advanced Features → OpenAI Fine Tuning.
  2. Select the relevant record, filter, report, model or configuration described below.
  3. Use the displayed action or read the current values without altering unrelated data.
  4. Compare the output with the code-backed rules and expected result in this guide.
  5. Record or correct any mismatch before relying on the output in production.

Fields, choices and supported possibilities

ActionUnderstand fine-tuned model list ordering
Exact navigationAdmin Area → Setup → Settings → AI → OpenAI → Advanced Features → OpenAI Fine Tuning
Module version1.0.0
VerificationConfirm the saved record, status, output or setting in the same workspace and review any linked activity, file or notification.

Code-backed validations and workflow rules

  • pcrm-owned models are prioritised.
  • Within ordering, newer creation timestamps are shown first.

Expected result and verification

  • The supported understand fine-tuned model list ordering flow completes without bypassing permission or validation checks.
  • The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
  • Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

  • Restrict the API key and AI settings to authorised administrators.
  • Do not submit confidential, special-category or unnecessary personal data to the external AI provider.
  • Review generated text before using it in customer, staff, legal, financial or compliance communication.
  • Monitor provider billing and retention independently because this module has no built-in cost dashboard.