Set a fine-tuned model as active
Follow this guide to choose the exact model ID used when fine-tuning is enabled. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Settings → AI → OpenAI → Advanced Features → OpenAI Fine Tuning → Fine Tuned Models → Set as Active
Before you start
- Use an account with Settings: Edit 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 you’ll accomplish
Choose the exact model ID used when fine-tuning is enabled. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Follow these steps
- Go to Admin Area → Setup → Settings → AI → OpenAI → Advanced Features → OpenAI Fine Tuning → Fine Tuned Models → Set as Active.
- Go to the exact setting, option or record named in this guide.
- Enter or select the required value; leave unrelated options unchanged.
- Save the form and wait for the success response.
- Reload the page or open a controlled record to confirm the stored value is being used.
Fields and options to review
ActionSet a fine-tuned model as active
Exact navigationAdmin Area → Setup → Settings → AI → OpenAI → Advanced Features → OpenAI Fine Tuning → Fine Tuned Models → Set as Active
Module version1.0.0
VerificationVerify the saved record, status, output or setting in the same workspace and review any linked activity, file or notification.
Rules the system enforces
- The selected ID is stored in openai_fine_tuned_model.
- The active label appears beside the current selection.
How to confirm it worked
- The supported set a fine-tuned model as active 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.
- Check 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.
