Using AI Tools Inside GreatHosts CP

1. What the AI Tools area is

The live GreatHosts CP exposes AI Tools as a dedicated account area rather than hiding AI functionality inside a generic support page. It includes project management and AI-account controls.

• AI projects are listed inside the hosting account.
• A Create New Project action is exposed.
• AI Accounts is managed separately from ordinary hosting credentials.

2. Customer-owned ChatGPT connection

The current AI Accounts dialog offers a ChatGPT subscription connection for customers who want to connect their own eligible ChatGPT account. The panel presents an authorization/sign-in flow and also exposes a token-import fallback.

• The interface describes the connection as using your own subscription.
• Do not share ordinary account passwords in project files or support messages.
• Provider authentication flows can change; follow the current panel instructions rather than an old screenshot.

3. Customer-owned Claude connection

The same dialog exposes a Claude subscription connection with an authorization flow. As with ChatGPT, the subscription belongs to the customer; the hosting plan should not be described as including a third-party AI subscription unless a current plan explicitly says so.

• Treat provider authorization codes/tokens as sensitive.
• Use the current provider/panel flow.
• Disconnect an account when it should no longer be available to the hosting project.

4. AI credits are a separate path

The panel text distinguishes connecting your own subscription from using AI through monthly credits. Those are different commercial/authentication models, and current credit terms should be checked in the live interface.

• Do not equate a hosting plan with unlimited AI use.
• Check current credit availability and price before relying on it.
• Choose the model that matches the project and account policy.

5. AI projects are not hosting requirements

The presence of AI Tools does not mean a website must use them. A normal PHP, WordPress, static or Python site can be hosted without connecting an AI account.

• Use AI Tools only when they add value to the workflow.
• Keep production secrets separate from prompts and generated files.
• Review generated changes before publishing them.

6. Keep authorization separate from application secrets

AI-account authorization and website application credentials solve different problems. Do not place AI tokens, hosting passwords, payment credentials or private keys in public web files.

• Use provider authorization mechanisms rather than copying passwords.
• Revoke tokens that are no longer required.
• Keep application environment secrets outside public document paths where the application supports it.

7. Verify capabilities before promising them to clients

AI integrations evolve quickly. GreatHosts should describe only the controls currently exposed in the live CP and should re-verify the panel before publishing instructions about new models, credits or project features.

• Use the live CP as the current interface reference.
• Avoid promising a particular third-party model or quota unless the current account shows it.
• Update guides when authorization or project behavior changes.

Services related to this guide