OpenAI Integration — Security, privacy, limitations and troubleshooting
Protect API credentials and submitted content and diagnose provider, model, training and output errors without inventing unsupported controls.
01Protect the OpenAI API keyApply least privilege and secret-handling controls to the stored credential.Admin Area → Setup → Settings → AI → OpenAI02Assess personal-data transfer to OpenAIReview lawful basis, minimisation and provider terms before using CRM data in prompts.Data protection review → CRM AI features03Review AI-generated content before usePrevent unverified output from becoming an official CRM communication or decision.Any CRM feature using OpenAI → review generated result04Monitor OpenAI cost and usage externallyUse provider-side controls because this module has no usage dashboard.OpenAI provider account → Usage/Billing05Understand the absence of OpenAI module cron and webhooksDo not expect background polling or inbound provider events from this module.Code-backed reference → supplied OpenAI module hooks/controllers06Understand the absence of API-key rotation controlsPlan credential lifecycle outside the module.OpenAI provider account and Admin Area → Setup → Settings → AI → OpenAI07Review OpenAI activity and PHP logsUse the available evidence when provider calls fail.Admin Area → Utilities/Activity Log and server PHP logs08Troubleshoot OpenAI authentication or model-access errorsVerify key validity, account access and the selected model.Admin Area → Setup → Settings → AI → OpenAI09Troubleshoot OpenAI rate-limit, quota or token errorsReduce request frequency/size or correct provider account limits.Admin Area → Setup → Settings → AI → OpenAI10Run the OpenAI Integration production verification checklistVerify settings, controlled output, fine-tuning access and privacy controls before release.Admin Area → Setup → Settings → AI → OpenAI