Run the OpenAI Integration production verification checklist
Verify settings, controlled output, fine-tuning access and privacy controls before release.
Where to goAdmin Area → Setup → Settings → AI → OpenAI
Before you start
- Use an account with Administrator 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 helps you do
Verify settings, controlled output, fine-tuning access and privacy controls before release. 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.
- Select the relevant record, filter, report, model or configuration described below.
- Use the displayed action or read the current values without altering unrelated data.
- Compare the output with the code-backed rules and expected result in this guide.
- Record or correct any mismatch before relying on the output in production.
Fields and options
ActionRun the OpenAI Integration production verification checklist
Exact navigationAdmin Area → Setup → Settings → AI → OpenAI
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 and limits
- Verify module v1.0.0, CRM 3.2.*+, PHP 8.1+, a valid key, selected model and max tokens.
- Run a non-sensitive test request and inspect output.
- If fine tuning is used, verify source eligibility, job state, selected model and enable toggle.
Check it worked
- The supported run the openai integration production verification checklist 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.
Related guides
Was this guide useful?Your response is stored only in this browser.
