How to change or replace an AI provider key in PD AI Assistant for Blesta
Use Provider & connection when changing the active AI service or replacing a saved OpenAI or Gemini key. Plan the change around the assistant features your team actually uses, rather than treating it as a change to one staff conversation.
Review the effect first
Open the PD Modules plugin in your staff area, choose PD AI Assistant, then open Settings → Provider & connection. Note the active provider and model. Staff chat, enabled customer chat and automated work use the configured engine. Arrange a controlled check before relying on those features after the switch.
Keep your original knowledge documents available. Changing the provider does not automatically rebuild previously indexed custom references. Check Settings → Knowledge and note each source’s audience and Embedded with value before proceeding.
Replace a saved OpenAI or Gemini key
- Select the intended provider in Choose a provider. Viewing a different form does not make it active.
- Paste the replacement into API key. Leaving this field blank keeps the key that is already saved for that provider.
- Review Model and, for OpenAI, the optional proxy address. Retain an existing gateway only if that is your intended destination.
- Click the provider’s Connect button. Saving its form also makes that provider active, even if you were only planning to replace an inactive provider’s key.
- Confirm the active summary, then check a simple reply. Check indexing separately if you use custom Knowledge.
After a planned rotation, retire the old credential through its provider only once the replacement has been checked. If the old key is exposed, prioritise revoking it with the provider and restoring service with a replacement.
Switch back to Amazon Bedrock
Select Your own Amazon Bedrock (your AWS account), review its Model, and use Save & use Amazon Bedrock or Save Bedrock settings, as shown. If AWS credentials are missing, the form directs you to Connect AWS; selecting Bedrock alone cannot supply them.
Understand Remove key
Remove key clears the saved key for the provider whose form you are viewing. If it is the active provider, the module falls back to Bedrock, which still needs a working AWS connection. Removing an inactive provider’s key leaves the currently selected provider unchanged.
Removing a key here does not revoke it at its provider. A provider switch also does not erase conversation history, Memory, custom Knowledge or existing proposals. Use the knowledge replacement procedure when references need rebuilding. If a change fails, check the active summary before trying again and retain the original redacted error while your hosting team checks the actual selected engine.
See the PD AI Assistant Blesta guide for related tasks, or explore PD AI Assistant.