Setup, access and model configuration

Troubleshoot a missing OpenAI settings section

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Check module activation, CRM version and parent AI settings registration when the child section is absent.

Audience: CRM administrators and authorised staffPermission: AdministratorModule v1.0.0

Jump to steps

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

Check module activation, CRM version and parent AI settings registration when the child section is absent. 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

ActionTroubleshoot a missing OpenAI settings section

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 the module is active and vendor autoload succeeds.
Verify the CRM contains AiProviderRegistry and the AI settings group expected by CRM 3.2.*.
Check PHP logs for dependency or class-loading errors.

Check it worked

The supported troubleshoot a missing openai settings section 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.

Was this guide useful?Your response is stored only in this browser.