Setup, access and model configuration

Set the OpenAI maximum token value

Control the max_tokens value sent with each chat request. 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.

Audience: CRM administrators and authorised staffPermission: Settings: EditModule v1.0.0
Jump to steps
Where to goAdmin Area → Setup → Settings → AI → OpenAI
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

Control the max_tokens value sent with each chat request. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Follow these steps

  1. Go to Admin Area → Setup → Settings → AI → OpenAI.
  2. Go to the exact setting, option or record named in this guide.
  3. Enter or select the required value; leave unrelated options unchanged.
  4. Save the form and wait for the success response.
  5. Reload the page or open a controlled record to confirm the stored value is being used.

Fields and options to review

Maximum tokensNumeric setting openai_max_token; it is cast to an integer before the API call.
EffectPassed as max_tokens in chat()->create().

Rules the system enforces

  • The module does not calculate cost or validate the value against a selected model’s current provider limit.

How to confirm it worked

  • The supported set the openai maximum token value 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.